ARD Catalog Generator

Build your /.well-known/ard.json visually - the catalog AI agents search to find your MCP servers, A2A agents and skills.

Publisher

Your domain

Publisher name (for reference)

Your resources (ARD entries)

Import instead of typing

Output options

Publishing mode

JSON-LD @context

Fill in at least one resource, then generate. Everything runs in your browser - nothing is uploaded.

Your ard.json will appear here.

Publish it in 3 steps

Generate a catalog to see your hosting snippets.

ard.json vs ai-catalog.json: what changed in ARD v0.91

ARD launched in May 2026 (v0.9) with the manifest at /.well-known/ai-catalog.json. Version 0.91, dated 26 August 2026, renamed it to /.well-known/ard.json and the HTML link relation from ai-catalog to ard. The entry format did not change - existing manifests remain valid entries - but the resolution rules did: a conformant consumer must fetch ard.json and may also check the old path as a courtesy.

That single rename strands every publisher who shipped early. Independent measurement in September 2026 found 99 publishers, with only 23 on the current path; the rest answer only on ai-catalog.json, where strict consumers never look. This generator therefore treats ard.json as the target, offers a maximum-compatibility mode that serves the same catalog at both paths during the transition, and writes the current rel="ard" link tag for you.

What makes an entry discoverable

A registry does not rank your entry by its name; it builds a semantic index from your representativeQueries - 2 to 5 sample requests written the way a user would phrase them ("what is the current wind speed in Chicago", not "weather API"). Capabilities are short tokens (WeatherTool, ForecastTool) that let registries filter without fetching your artifact. Add a trustManifest with an identity bound to the same domain as your identifier URN and registries can verify you are really the publisher. The generator scaffolds all of it; the validator linked below checks it.

How to use this tool

Enter your domain - it anchors every identifier URN the generator creates.
Add one entry per resource: MCP server, A2A agent, skill or API. Or import an MCP config / A2A card and let the tool prefill it.
Write 2 to 5 representative queries per entry, in the words your users would actually use.
Generate, review the live issue summary, then copy or download the JSON.
Host it at /.well-known/ard.json, add the link tag and robots.txt snippets shown, and run your live URL through the ARD Website Checker.

Frequently Asked Questions

Agentic Resource Discovery (ARD) is an open specification from authors at Google, Microsoft and Hugging Face that lets AI agents discover callable capabilities - MCP servers, A2A agents, skills and APIs - without hardcoding them. A publisher describes its resources once in a JSON manifest hosted at /.well-known/ard.json, and registries index that manifest so agents can search it by intent.

ai-catalog.json was the path in ARD v0.9. Version 0.91 (August 2026) renamed the well-known file to ard.json and the HTML link relation from ai-catalog to ard. Consumers must fetch ard.json; checking the old path is optional courtesy. A site that publishes only ai-catalog.json may not be found by conformant consumers, so this generator targets ard.json first and can emit both files in maximum-compatibility mode.

Per the v0.91 specification, an entry must carry an identifier (a domain-anchored URN like urn:air:example.com:server:weather), a displayName, a type written as a media type (for example application/mcp-server-card+json), and exactly one of url or data. It should also carry 2 to 5 representativeQueries - the sample questions a registry uses to match the resource to user intent - because an entry without them is a valid catalog entry but is not discoverable through ARD search.

At https://your-domain.com/.well-known/ard.json, served as JSON over HTTPS. Add a link tag with rel=ard in your homepage head and, optionally, an Agentmap line in robots.txt pointing at the same file. This generator shows all three snippets with your domain filled in.

Yes. The import panel converts an MCP server configuration (the mcpServers JSON used by MCP clients) or an A2A agent card JSON into a ready ARD entry with identifier, type and URL filled in. You then add representative queries and capabilities before generating the catalog.

Related Tools

ARD Catalog Validator

Validate a catalog against the v0.91 rules, score its discovery signals, and view it like a registry.

AI Agent Discoverability Checker

Check a live domain for ard.json, the legacy path, link tags and Agentmap - scored to 100.

AI Agent Readiness Checker

The companion audit: llms.txt, structured data and form signals - can agents use your site once they find it?

Was this tool helpful?

Comments

Loading comments...

Check Out Other Popular Tools

Professional Personality Index (Big Five / OCEAN)

Scientifically validated Big Five personality assessment based on Goldberg (1999) 50-item IPIP. Measure your OCEAN percentile scores, leadership archetype, and verified career profile.

Education71

Byte Converter

Convert between bits, bytes, KB, MB, GB, TB, and PB instantly. Supports binary (1024) and decimal (1000) conversion standards. Free data storage calculator.

Calculators408

Christmas Countdown

Count down to Christmas with a festive timer. See days, hours, minutes, and seconds until Christmas Day. Share the holiday spirit!

Entertainment895