Setup
One endpoint, one card, one keyring. The door is a stateless streamable-HTTP Model Context Protocol (MCP) server; the Agent-to-Agent (A2A) party is described by the signed Agent Card. Reads need no credential. An agent that transacts presents a credential; settlement is x402.
The endpoint
- MCP door —
https://mcp.a2a-peptides.ai/mcp, transport streamable-http, protocol version 2025-06-18, server namea2a-peptides. Open schemas; every tool answers JSON. - Agent Card —
https://a2a-peptides.ai/.well-known/agent-card.json, signed ES256 under kida2ap-2026-09; verify againsthttps://a2a-peptides.ai/.well-known/jwks.json. - Registry listing — namespace
io.github.A2A-Peptides(the registry grants the login's own case), servera2a-peptides. Contact for every listing this hub files: the mcp mailbox on this domain, on the card. - Headers — every response carries the GSC wire envelope (the x-gsc-* header set) naming the node, the card, the keyring, the door and the graph.
Connect
Add the door as a remote MCP server in any client that speaks streamable-HTTP. The stock client of each major cloud connects with no adapter: give it the URL, the transport and the server name.
- Any MCP client —
{ "url": "https://mcp.a2a-peptides.ai/mcp", "transport": "streamable-http" } - First three calls —
resolve_jurisdiction·resolve_actor·gate_transaction. The gate returns allow, deny or require_rx with a reason code and a rule-set version; no price, availability, order or handoff tool answers before an allow or require_rx exists. - A2A — read the Agent Card; skills are the twenty tools under the
peptides.*prefix; the handoff skill ispeptides.a2a_handoff.
Credentials by actor class
- Reads (substance record, pathway status, cleared catalogue, enforcement watch, safety label) — no authentication. Registry-truth reads are metered by x402 on the registry zone.
- Patient — no credential; the door answers cosmetic and supplement pathways and refers to a licensed channel. No vial checkout.
- Prescriber, pharmacy or 503B, wholesaler, cosmetic brand, retailer — a licence on record with the hub; the licence number, issuer and expiry are read from the register and carried on the supplier record.
- Agent — must present a credential issued to a licensed party. No credential returns DENY_UNLICENSED_AGENT. Credential issuance opens with door version 1.0 on this page.
- Settlement — x402, USDC on Base, after the gate. Receipts are signed and carry the reason code and the rule-set version. Human page: /x402.
Tenants
A tenant is a supplier record, catalogue rows and a signed Agent Card on its own hostname. Onboarding is ordered per signed tenant: the licences are read from the register, the catalogue rows are cut on real Global Trade Item Numbers (GTINs) or GTIN-less, and the card is signed under the hub keyring. Tenants never get repositories.
The form is the only human door on this surface. Machine contact is on the Agent Card and in the headers.