Theta EdgeCloud serves an AI Catalog
manifest at /.well-known/ard.json on www.thetaedgecloud.com, declaring
4 agentic resources
that a discovery service can index without asking anyone’s permission.
/.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.host-no-identifiercontent-type-not-ai-catalog-jsonMarkdown documentation for Theta EdgeCloud: GPU node rental, on-demand model inference, dedicated model serving, notebooks and GPU clusters. The full page index is at https://docs.thetatoken.org/llms.txt.
RFC 9727 API catalog listing the Theta EdgeCloud controller API and the on-demand model inference API, with links to their documentation. Authentication is a project-scoped API key in the x-api-key header.
Agent skill (SKILL.md) explaining how to rent GPU nodes, run on-demand inference and read billing through the Theta EdgeCloud API, including authentication and safety rules for billable actions.
Hourly rates and availability for community RTX GPUs (5090, 4090, 3090 and more) on Theta EdgeCloud, with a quiz to pick the right GPU. Also served as Markdown when requested with Accept: text/markdown.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://www.thetaedgecloud.com/.well-known/ard.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Theta EdgeCloud repository
as ai-catalog/theta-edge-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.