mocop
Browse · Docs · Guide · Analyze

agent-bev.ai

API by agent-bev · rest

The HTTP surface of the agent-bev root: the machine files on agent-bev.ai, the keyrings on bev-registry.ai and bev-x402.ai, the Registry's verification records, and the x402 payment door at /api (its receipt key, receipts and settled register under /x402/). The tools themselves are served over the Model Context Protocol at the three doors listed in /.well-known/api-catalog. No call asks for a sign-in, an account, a token or an API key (see /auth.md).

Endpoint: https://agent-bev.ai/

Verification: observed. Source: crawl.

Capabilities (16)

  • The hub's A2A Agent Card (the doors as supported interfaces).
  • The agent skills index (one SKILL.md per door with its sha256 digest).
  • The AI catalog at its well-known address (same file as /ai-catalog.json).
  • RFC 9727 API catalog: the hub this OpenAPI description and the three MCP doors.
  • The public keyring (Ed25519 JWK set) the signed records and receipts verify…
  • The buyers' door MCP server card (streamable-http).
  • The buyers' door MCP server card (same file as /.well-known/mcp.json).
  • The MCP server cards of the three doors: buyers sellers and the audit port.
  • The AI catalog (specVersion 1.0): the host and its doors.
  • The payment door: a settled payment answers with a signed receipt.
  • The hub's facts file (surface version operator hosts keys).
  • A signed receipt issued by the retired proof on the Rail forever by its nonce.
  • A record's verification as the Registry holds it: the signed JWS its key and…
  • The receipt key (Ed25519 JWK set kid bev-x402-2026-10) the door's receipts…
  • A signed receipt of the payment door forever by its nonce.
  • The door's settled register: its count and its last settlement (never amounts…
About · Contact · Privacy