Build with AI
Every fact on this site is a public URL. There are three ways to put it in front of your agent, and they combine: the plugin is the one command that sets up the other two.
This documentation live, queried a paragraph at a time as your agent works. It cannot go stale, because it is this site answering.
One command that sets your agent up with both of the others: the skills as files, the server as a connection.
One file per job, carrying a whole milestone: every endpoint, header, error code and test. Works offline, and ages until you update it.
Connect the Docs MCP server
A skill is a snapshot. The Docs MCP server is the same catalogue live, queried a paragraph at a time instead of loaded whole.
Install the plugin
One command for both halves: the skills as files and the server as a connection. Claude takes it as a plugin; Cursor, Codex, ChatGPT and anything else that can fetch a URL take the same setup as a line to paste.
Install a skill
One file per job, in three shapes. A module skill carries every endpoint, header, error code and test case for that milestone, provider side (M1 to M4) or patient side (P1 to P3). A scaffold or debug skill is a procedure instead: it works against the sandbox in a loop that ends on an observed result, not on a call returning 200. Those exist for M1 to M3, the milestones the catalogue has flows and errors for. The FHIR skills build or audit NRCES compliant bundles.
Prompting an agent to build against ABDM
An agent with this site loaded still writes a plausible integration rather than a correct one, because the parts of ABDM that catch people are the parts a model cannot infer. Tell it these, and check its output against them.
| Tell it | Because |
|---|---|
| Look the operation up here before writing the call | NHA's v3 differs from the v1 and v2 an agent was trained on. The MCP server above is this site answering live, so it cannot be recalling an older shape |
| Identifiers are encrypted, and the plaintext has a shape | An agent encrypts what looks like the value. An ABHA number keeps its dashes, and the bare digits are refused. See encryption |
| Callbacks are how the answer arrives, from M2 onward | Left alone, an agent writes a synchronous call and a response handler for a flow where the 202 means accepted and nothing else. See the gateway |
| Do not invent an error code or an endpoint | Both exist here in full. An invented ABDM- code is indistinguishable from a real one until somebody hits it |
| One bridge serves every facility, so the callback URL and the credentials are not facility settings | Left alone, an agent builds a settings screen per facility and puts them on it. That works for the first facility. See one bridge, many facilities |
| Aadhaar numbers, one time passwords and passwords never reach a log, a fixture or a test | An agent writing test data will otherwise put a real looking Aadhaar number in your repository |
Point it at Build it well for the handling rules themselves: what to validate, what each error means, what is safe to retry, and what the screen should say.
Read this site as an agent
llms.txt is a map of every page here; llms-full.txt is every page's text in one file. Add /index.md to any URL on this site to get that page as plain Markdown, no scraping required.
Ask AI
Ask this catalogue a question directly, without setting anything up.
The same assistant sits in the search box at the top of every page, labelled "Search or ask AI".