Turns structured agent metadata into a finished catalog entry - as a
governance record and as a portal-style web view - and publishes it to
the internal Agent Catalog.
A catalog entry always references exactly one agent from Agent
Deployments. Standalone catalog entries without a deployment record are
intentionally not supported, so compliance disclosures and rollout
history stay maintained in a single place.
Workflow
POST /catalog-entriesstarts the generation. The response carriesstatus: "in_progress".- Once the entry is ready, the status changes to
completed. We recommend
subscribing to thecatalog_entry.completedevent instead of polling. GET /catalog-entries/{entryId}/recordreturns the document.POST /catalog-entries/{entryId}/publishputs it live in the internal catalog.
Compliance disclosures
Before publication the API checks the disclosures required by governance
policy - most importantly the compliance-certification figures and the
chargeback rate. If something is missing, the API responds with 422 and
code: "compliance_disclosure_missing".
- Server 1:https://api.nexora.example/v1
Production
- Server 2:https://sandbox.api.nexora.example/v1
Sandbox
apiKey (apiKey)
Every call carries an API key in the apikey header. You generate the
key in the Nexora AI portal under “My Apps”; it’s shown exactly once.
Each key has the scopes it’s allowed to use attached to it. If one is
missing, the API responds with 403 and code: "scope_missing"; the
missing scope is in details[].field.
For demonstration purposes only License