API access

API availability

API visibility depends on having an active agent configured for the API environment. Settings can show credentials already issued to the account, but Nerova does not currently publish a universal self-service endpoint and payload reference on this documentation site.

Before you integrate

• Confirm the intended agent is active in the API environment.
• Check Settings > API Keys for credentials already associated with the account.
• Obtain the supported base URL, authentication method, request schema, response schema, and rate limits from Nerova for your enabled workflow.
• Do not infer a contract from dashboard browser traffic or another agent’s integration.
• Test success, invalid input, authorization failure, and timeout behavior outside production.

Protect API credentials

• Store keys in a server-side secret manager or protected environment variable.
• Never embed a private API key in browser code, public repositories, or shared screenshots.
• If exposure is possible, stop using the credential and contact Nerova to replace or revoke it through the supported account process.
• Do not assume the visible key prefix in Settings can be used to recover the full credential.

No generic public contract yet

A complete public reference requires a stable, supported external contract. Until that contract is published, build only from connection details explicitly provided for your enabled agent and workflow.