Hyperline serves an AI Catalog
manifest at /.well-known/ai-catalog.json on hyperline.co, declaring
4 agentic resources
that a discovery service can index without asking anyone’s permission.
/.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.
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.root-collections-removed-by-adr-0003content-type-not-ai-catalog-jsonhost-identifier-not-did-webSearch and read the complete public Hyperline documentation and API reference through a read-only MCP server.
Create customers, quotes, subscriptions, wallets and invoices, collect payments and read revenue data through Hyperline's REST API.
Stream usage events into Hyperline for real-time metering and usage-based billing.
Guidance for agents building billing systems, subscriptions, quotes, usage tracking and revenue workflows on Hyperline.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://hyperline.co/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Hyperline repository
as ai-catalog/hyperline-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.