Publishing

Submit to Orchet Store.

Submission turns a public agent endpoint, remote MCP server, or A2A Agent Card into a reviewable contract snapshot.

Submission paths.

The developer portal and CLI call the same Orchet Store submission APIs.

Path	Use for
POST /marketplace/submissions/sdk	Developer-hosted SDK/API agents with manifest and OpenAPI.
POST /marketplace/submissions/mcp	Remote MCP servers over SSE or streamable HTTP.
POST /marketplace/submissions/a2a	A2A peers with Agent Cards.

SDK/API CLI submission.

The default SDK/API path is hosted-first. Create a developer key, deploy your agent, and submit the manifest, OpenAPI, and health URLs. Signed bundles are optional advanced metadata for verified releases; they are not required for a simple HTTPS agent.

SHELL

# Create this token at https://www.orchet.ai/developer/keys
export ORCHET_DEVELOPER_TOKEN=orchet_dev_...

orchet-agent submit \
  --manifest-url https://weather-demo.example.com/.well-known/agent.json \
  --openapi-url https://weather-demo.example.com/openapi.json \
  --health-url https://weather-demo.example.com/health \
  --contact-email developer@example.com

Advanced signed bundles are optional.

Use --bundle and --signature-file only when a reviewer asks for a signed release artifact or when your trust tier requires provenance evidence. Hosted manifest submission remains the public developer default.

Response shape.

Successful submissions return a pending submission id and synchronous trust results. Blocking trust failures return 422 and are not persisted.

JSON

{
  "submission_id": "8e3a...uuid",
  "state": "pending",
  "agent_type": "mcp_remote",
  "submitted_at": "2026-05-16T10:30:00.000Z",
  "trust_results": [
    { "name": "server_id_shape", "severity": "info", "ok": true }
  ]
}