Limrun serves an AI Catalog
manifest at /.well-known/ai-catalog.json on lim.run, declaring
4 agentic resources
that a discovery service can index without asking anyone’s permission.
did:web:limrun.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/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.content-type-not-ai-catalog-jsondid-web-does-not-resolveRemote MCP server that creates and drives cloud iOS simulators and Android emulators for AI agents.
Agent skills teaching the exact lim CLI workflows for building, testing, and previewing mobile apps on Limrun.
OpenAPI specification for the Limrun management API (instances, assets, tokens, organizations).
Customer documentation for Limrun cloud simulators, remote Xcode builds, and agent integrations.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://lim.run/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Limrun repository
as ai-catalog/limrun-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.