Intlayer serves an AI Catalog
manifest at /.well-known/ai-catalog.json on intlayer.org, declaring
18 agentic resources
that a discovery service can index without asking anyone’s permission.
Run against this exact body with the project’s own
conformance CLI.
Discovery path
predecessor
Answered only at /.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.
Declared spec version
1.0
The 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.
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
content-type-not-ai-catalog-json
host-identifier-not-did-web
18 entries
5 media types
53 representative queries
0 trust manifests
Host identifier: https://intlayer.org
What this manifest advertises
Intlayer MCP Server
urn:air:intlayer.org:mcp:intlayer
Remote MCP server exposing Intlayer as tools: search the documentation, run CLI commands such as dictionary builds and translation fills, and manage CMS projects, environments and dictionaries.
“what is Intlayer and which frameworks does it support”
Intlayer for Angular
urn:air:intlayer.org:skill:intlayer-angular
Integrates Intlayer internationalization with Angular applications. Use when the user asks to "setup Angular i18n", create a new translated component, use the "useIntlayer" composable, or configure providers.
“set up internationalization in an Angular application”
“translate an Angular component with Intlayer”
“register the Intlayer providers in an Angular app”
Intlayer for Astro
urn:air:intlayer.org:skill:intlayer-astro
Integrates Intlayer internationalization with Astro applications. Use when the user asks to "setup Astro i18n", use "getIntlayer" in Astro components, or manage server-side content in Astro.
Manages Intlayer dictionaries and configuration via the Command Line Interface. Use when the user asks to "audit translations", "build dictionaries", "sync content", or run "intlayer" commands.
“extract translations from my components automatically”
“use Intlayer without writing content declaration files by hand”
“configure the Intlayer compiler in my build tool”
Intlayer Configuration
urn:air:intlayer.org:skill:intlayer-config
Configures Intlayer project settings and environment variables. Use when the user asks to "setup intlayer.config", "configure locales", or "customize Intlayer settings".
“change where Intlayer writes its generated dictionaries”
Intlayer Content Declaration
urn:air:intlayer.org:skill:intlayer-content
Define rich content structures using Intlayer content nodes. Use when the user asks to "create translations", "handle pluralization", "use markdown in content", or implement "conditional content".
“declare conditional or nested content per locale”
Intlayer for Next.js
urn:air:intlayer.org:skill:intlayer-next-js
Integrates Intlayer internationalization with Next.js App Router and Pages Router. Use when the user asks to "setup Next.js i18n", use "useIntlayer" in Server Components, or handle client-side translations in Next.js.
“set up internationalization in a Next.js App Router project”
“translate a Next.js server component”
“add localized routing to a Next.js application”
Intlayer for Preact
urn:air:intlayer.org:skill:intlayer-preact
Integrates Intlayer internationalization with Preact applications. Use when the user asks to "setup Preact i18n", create a new translated component, use the "useIntlayer" hook in Preact, or configure providers.
“set up internationalization in a Preact application”
“translate a Preact component with Intlayer”
“use the useIntlayer hook in Preact”
Intlayer for React
urn:air:intlayer.org:skill:intlayer-react
Integrates Intlayer internationalization with React component. Use when the user asks to "setup React i18n", create a new translated component, use the "useIntlayer" hook, or configure providers.
“set up internationalization in a React application”
“translate a React component with Intlayer”
“read translations with the useIntlayer hook”
intlayer-cms
urn:air:intlayer.org:skill:intlayer-cms
Manages remote content and server-side dictionaries using the Intlayer CMS. Use when the user asks to "fetch remote translations", "use Intlayer CMS", or "handle server-side content".
“Manages remote content and server-side dictionaries using the Intlayer CMS”
intlayer-solid-js
urn:air:intlayer.org:skill:intlayer-solid-js
Integrates Intlayer internationalization with SolidJS components. Use when the user asks to "setup SolidJS i18n", create a new translated component, use the "useIntlayer" hook in Solid, or configure providers.
“Integrates Intlayer internationalization with SolidJS components”
Intlayer for Svelte and SvelteKit
urn:air:intlayer.org:skill:intlayer-svelte
Integrates Intlayer internationalization with Svelte and SvelteKit applications. Use when the user asks to "setup Svelte i18n", create a new translated component, use the "useIntlayer" store, or configure providers.
“set up internationalization in a SvelteKit application”
“translate a Svelte component with Intlayer”
“read an Intlayer store in Svelte”
Intlayer Getting Started
urn:air:intlayer.org:skill:intlayer-usage
Provides general guidelines for using Intlayer in any project. Use when the user asks to "get started with Intlayer", "declare content files", or understand the "project structure" for internationalization.
“get started with Intlayer in an existing project”
“where do I declare Intlayer content files”
“how does Intlayer structure a multilingual project”
Intlayer for Vue and Nuxt
urn:air:intlayer.org:skill:intlayer-vue
Integrates Intlayer internationalization with Vue.js and Nuxt applications. Use when the user asks to "setup Vue i18n", use the "useIntlayer" composable, or manage translations in Vue components.
“set up internationalization in a Vue or Nuxt application”
“translate a Vue component with Intlayer”
“use the useIntlayer composable in Vue”
How it is served
The publishing guide asks for three things at the transport layer, because a crawler is the
consumer that matters and a crawler is a browser-shaped client.
HTTPS only — yes (HTTP 200)
Content-Type: application/json —
yes
Access-Control-Allow-Origin: * —
yes
Evidence. Fetched https://intlayer.org/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Intlayer repository
as ai-catalog/intlayer-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.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for agent discovery
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.