Calvis serves an AI Catalog
manifest at /.well-known/ard.json on calvis.com, declaring
5 agentic resources
that a discovery service can index without asking anyone’s permission.
did:web:calvis.com —
resolving it returns 404. A did:web: that does not resolve is a string, not an identity, and does not earn the identity affordance here.
/.well-known/ard.json — the path ARD v0.91 says a consumer MUST fetch.
specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.content-type-not-ai-catalog-jsondid-web-does-not-resolveHosted Model Context Protocol server for booking and managing security guard coverage through the Calvis marketplace.
How an AI agent registers an OAuth 2.1 client and obtains an access token for the Calvis MCP server.
RFC 9727 linkset of the machine-readable API and authorization metadata Calvis publishes.
Plain-text overview of the Calvis marketplace: services, covered metros, hourly pricing ranges, and booking entry points.
Index of the agent skills Calvis publishes, each describing a task an agent can carry out against the marketplace.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://calvis.com/.well-known/ard.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Calvis repository
as ai-catalog/calvis-ai-catalog.json. Nothing on this page is derived
or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not
exist, which makes it — like an
A2A Agent Card — one of the few agent artifacts that cannot be
produced on a provider’s behalf. Grades are recomputed on every build; the specification is a
v0.9 draft and
these verdicts will move when it does.
Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.