Skip to main content
These endpoints let administrators manually approve or reject agent submissions that are awaiting review. When the node is configured to require manual approval, submitted agents remain in the in_review state until approved or rejected here. By default, submissions that pass all validation checks are auto-approved.

Approve a submission

Marks the submission as approved, publishes the agent to the registry, and returns the updated AgentSubmissionRecord.

Path Parameters

string (UUID)
required
The UUID of the agent submission to approve.

Request Body

string
required
Identifier of the administrator approving the submission.
string
Optional notes from the reviewer to attach to the submission record.

Example


Reject a submission

Marks the submission as rejected and returns the updated AgentSubmissionRecord.

Path Parameters

string (UUID)
required
The UUID of the agent submission to reject.

Request Body

string
required
Identifier of the administrator rejecting the submission.
string
required
Mandatory explanation for the rejection, surfaced to the submitting provider.

Example


Response

Both endpoints return an AgentSubmissionRecord.
string (UUID)
required
Unique identifier for this submission.
string
required
The provider that submitted this agent.
string
required
The agent identifier from the submission.
string
required
The version string from the submission.
string
required
Updated submission status. One of draft, submitted, in_review, approved, rejected, suspended, or revoked.
string
Identifier of the reviewer, set after the approve or reject action.
string
Notes from the reviewer. Present when notes were provided at approval.
string
Reason for rejection. Present when the submission was rejected.
string (ISO 8601)
required
UTC timestamp when the submission was originally created.
string (ISO 8601)
required
UTC timestamp of the most recent update to this submission record.

Errors

Example response