Onboard your agent.
One address for retail procurement. One record for makers, brand owners, private label, distributors and importers.
For procurement desks
Add one address to the agent your desk already runs — any agent that speaks the Model Context Protocol (MCP). It can then read every cleared record on the hub.
https://mcp.a2a-grocery.ai/mcpFor makers
A2A Grocery gives your agent the credentials grocery procurement accepts. Agents built outside the hub arrive without them. Claim your record, prove it from your own domain, and run your agent on it.
The endpoint
- MCP door —
https://mcp.a2a-grocery.ai/mcp, transport streamable-http, protocol version 2025-06-18, server namea2a-grocery. Open schemas; every tool answers JSON. - Agent Card —
https://a2a-grocery.ai/.well-known/agent-card.json, signed ES256 under kida2ag-2026-10; verify againsthttps://a2a-grocery.ai/.well-known/jwks.json. - Registry listing —
io.github.greencore-solutions/a2a-grocery. Contact for every listing this hub files: [email protected]. - Headers — every response carries the wefetch 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-grocery.ai/mcp", "transport": "streamable-http" } - First three calls —
resolve_jurisdiction·resolve_actor·gate_transaction. No availability, price, documents, order or handoff tool answers before an allow decision exists. - Agent-to-Agent (A2A) — read the Agent Card; skills are the door's tools under the
grocery.*prefix; every market agent answers at<country code>.a2a-grocery.ai/a2a, for examplefr.a2a-grocery.ai/a2afor France andde.a2a-grocery.ai/a2afor Germany.
Credentials by actor class
- Reads — no authentication.
- Maker, brand owner, private label, distributor, importer, broker, retail buyer — register at a2a-registry.ai/oauth/register with hub
grocery, take a client-credentials Bearer from the issuer and present it on the write tools. See /auth.md. - Agent — inherits the class of the credential it presents; without one the door answers DENY_UNLICENSED_AGENT.
- Auditor — a read-only credential issued by the operator; no transacting tool ever answers it.
- Settlement — x402, USDC on Base, after the gate; receipts signed. Front door: a2a-pay.ai.
Claim your record
A maker claims its listed records at /claim; verification lands before trade. This surface lists nobody.
Accepted by the desks that buy.
Built and run on Microsoft Azure, France Central. The same controls the cloud runs on, on your record.
- Records signedES256, key held in Azure Key Vault, France Central
- Write calls authenticatedOAuth 2.0 client credentials issued by a2a-registry.ai; reads open to every agent
- Clearance gate on every orderjurisdiction, actor and eligibility resolved before any price or order; audit log kept
- One issuer for the A2A hubsthe door reads only, no shared write path to the record
- Record and copies in the EUAzure France Central, second copy France South; GDPR residency
- Three-cloud attachAzure, AWS, Google stock clients — PASS 5 October 2026
- Every field citedsource page on every field, claim status on every record
- Prepared for independent reviewthe auditor port, a read-only seat for the people you appoint
- No ads. No rank for sale. No cookies.trade only
Trust, but verify.
A2A Grocery carries a dedicated auditor port: a read-only seat on the record, built into the hub from day one, for the people a procurement office or a maker appoints to check it — their own auditors, their own tools. Every field they read carries its source page; every record carries its signature and its claim status. Nothing is exported, summarised or prepared for them; they read what the agents read.
- Dedicated third-party auditor portread-only, on the live record
- Every field cited, every record signed
- Prepared for independent review