Protocol

A2A peer agents.

A2A peers expose an Agent Card that Orchet can normalize into the Agent Contract Registry. Reviewers verify schema depth and runtime semantics before an A2A agent becomes available in Orchet Store.

Submission.

Submit the Agent Card URL and contact email. Orchet fetches the card, validates the basic shape, and creates draft tools from skills.

SHELL

ORCHET_DEVELOPER_TOKEN=... orchet-agent submit-a2a \
  --agent-card-url https://agent.example.com/.well-known/agent.json \
  --contact-email developer@example.com \
  --requested-tier community

Schema quality.

A2A skills do not always include strict per-skill JSON Schema. When schemas are missing, Orchet uses a conservative generic argument object until the developer supplies richer schema metadata. Use SDK/API when you need strict schemas, structured confirmations, or rollback guarantees on day one.

When to choose A2A.

Choose A2A for long-running delegated work, agent-to-agent ecosystems, or specialist services that already publish a peer protocol. Choose SDK/API when you need the tightest schema and confirmation control.