WebMCP registry entry
agent-bev.ai
What PurposeBot's crawler found when it checked agent-bev.ai for WebMCP, MCP, and API discovery signals agents can use.
Evidence
Machine document or MCP registry listing
The crawler retrieved a machine-readable discovery document, MCP manifest, registry feed, or published API endpoints for this domain, or the MCP registry lists this domain's site.
- Hosts
- agent-bev.ai
- URLs checked
- 1
- Protocol class
- mcp
- Last seen
- 2026-10-09
- Discovered via
- MCP registry
- Published API endpoints
- 16
- MCP quality score
- 0.73 (pass)
Discovered API endpoints
Endpoints published in machine-readable API documents on agent-bev.ai.
| Method | Path | Description | Auth |
|---|---|---|---|
| GET | /facts.json | The hub's facts file (surface version, operator, hosts, keys). | not stated |
| GET | /ai-catalog.json | The AI catalog (specVersion 1.0): the host and its doors. | not stated |
| GET | /.well-known/ai-catalog.json | The AI catalog at its well-known address (same file as /ai-catalog.json). | not stated |
| GET | /.well-known/api-catalog | RFC 9727 API catalog: the hub, this OpenAPI description and the three MCP doors. | not stated |
| GET | /.well-known/mcp.json | The buyers' door MCP server card (streamable-http). | not stated |
| GET | /.well-known/mcp/server-card.json | The buyers' door MCP server card (same file as /.well-known/mcp.json). | not stated |
| GET | /.well-known/mcp/server-cards.json | The MCP server cards of the three doors: buyers, sellers and the audit port. | not stated |
| GET | /.well-known/agent-card.json | The hub's A2A Agent Card (the doors as supported interfaces). | not stated |
| GET | /.well-known/agent-skills/index.json | The agent skills index (one SKILL.md per door, with its sha256 digest). | not stated |
| GET | /.well-known/jwks.json | The public keyring (Ed25519, JWK set) the signed records and receipts verify against. | not stated |
| GET | /verified/{record_id} | A record's verification as the Registry holds it: the signed JWS, its key and the domain proof. | not stated |
| GET | /api | The payment door: a settled payment answers with a signed receipt. | not stated |
| GET | /x402/jwks.json | The receipt key (Ed25519, JWK set, kid bev-x402-2026-10) the door's receipts verify against. | not stated |
| GET | /x402/receipt/{nonce} | A signed receipt of the payment door, forever, by its nonce. | not stated |
| GET | /x402/settled.json | The door's settled register: its count and its last settlement (never amounts per caller). | not stated |
| GET | /receipt/{nonce} | A signed receipt issued by the retired proof on the Rail, forever, by its nonce. | not stated |
Capability keywords
Terms extracted from the tool and API descriptions found on this domain.
URLs checked and signals found
- https://agent-bev.ai/Published API endpoints found · MCP registry · 2026-10-09
- Page HTML references WebMCP
Should an agent trust agent-bev.ai?
Discovery signals show that a site exposes something to agents. They do not show who operates it or how it behaves. PurposeBot, the AI agent trust layer, adds identity, provenance, and conduct-based trust scores on top of discovery. Operators of agent-bev.ai can register and verify their agents and tools to earn a trust score.