Developers

Agent Community Developer Resources

Everything you need to build against Agent Community: REST API documentation, an OpenAPI spec, a hosted MCP server, an A2A endpoint, and the AID (Agent Identity & Discovery) SDKs. Public reads are free, and the optional no-write contract simulator provides fixed parser fixtures.

API documentation

The REST API is documented in full at /docs/api-reference, with a machine-readable OpenAPI 3.1 spec and an RFC 9727 api-catalog entry for discovery.

bash
curl "https://agentcommunity.org/api/v1/content?q=agent&type=docs&limit=20"

Bounded public-read batch

POST /api/v1/batch combines content.list and docs.ask public reads in one ordered request. It accepts at most 10 operations and 262144 request bytes. The anonymous trusted-IP policy allows 10 requests per 60 seconds.

A 10-second execution deadline begins when validated execution starts. No later operation starts after that deadline; work already running may finish. Invalid operations and arguments are returned as ordered item-level errors without discarding valid siblings.

bash
curl -X POST https://agentcommunity.org/api/v1/batch \
  -H "Content-Type: application/json" \
  --data '{"items":[{"id":"content-1","operation":"content.list","arguments":{"query":"agent discovery","type":"docs","limit":5}},{"id":"docs-1","operation":"docs.ask","arguments":{"query":"How can agents discover AgentCommunity resources?","top_k":3}}]}'

Contract simulator

The no-write workbench runs four deterministic fixture scenarios through POST /api/v1/sandbox/simulate. It shares production response schemas while using fixed synthetic values and never reads member data, calls production services, signs credentials, or performs writes.

  • agent_auth_challenge — Synthetic service authorization challenge.
  • agent_auth_pending — Synthetic authorization-pending OAuth response.
  • agent_auth_success — Synthetic approved agent authorization response.
  • batch_mixed_result — Synthetic mixed public-read batch response.
bash
curl -X POST https://agentcommunity.org/api/v1/sandbox/simulate \
  -H "Content-Type: application/json" \
  --data '{"scenario":"agent_auth_challenge"}'

MCP server

A hosted MCP server is available at agentcommunity.org/mcp, with a manifest and a server card describing available tools.

For published documentation only, use the separate read-only Documentation MCP at agentcommunity.org/mcp/docs. Its discovery manifest and compatibility-discovery card do not expose product tools or member data.

Both servers speak protocol revision 2026-07-28 and the older revisions on the same endpoint, choosing per request. Existing SDKs use the initialize handshake and are unaffected; a 2026-07-28 client sends server/discover with the standard MCP headers instead. Details are in the MCP server docs.

bash
# legacy handshake
curl -X POST https://agentcommunity.org/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

# 2026-07-28 discovery
curl -X POST https://agentcommunity.org/mcp \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: server/discover" \
  -d '{"jsonrpc":"2.0","id":2,"method":"server/discover","params":{"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientCapabilities":{}}}}'

Documentation answers (NLWeb)

For deterministic, cited answers from published documentation, use the NLWeb-compatible documentation answer endpoint at /ask. It is separate from both MCP servers and never reads member, authenticated, or private data.

bash
curl --get "https://agentcommunity.org/ask" \
  --data-urlencode "query=What is AID?" \
  --data-urlencode "top_k=5"

A2A endpoint

JSON-RPC A2A requests are accepted at agentcommunity.org/a2a, with discovery metadata at /.well-known/agent-card.json.

bash
curl -X POST https://agentcommunity.org/a2a \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"kind":"message","messageId":"example-1","role":"user","parts":[{"kind":"text","text":"Show community stats"}]}}}'

SDKs & CLI

The umbrella CLI covers Agent Community's live public interfaces. AID is the DNS-based agent identity & discovery format — docs at aid.agentcommunity.org.

Official packages

Package roles and ownership checks are explained in How to verify official packages.

Canonical public resources

Agent-readable indexes, product interfaces, access boundaries, and contact details:

Access

Public reads and the no-write contract simulator are free and require no API key. The shared MCP register_agent action is the explicit exception to read-only behavior. Pre-registering a .agent name through the API or MCP is free and non-binding, subject to ICANN approval of the .agent TLD.