# 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. [Recommended](#connect-the-docs-mcp-server) [Docs MCP server](#connect-the-docs-mcp-server) [This documentation live, queried a paragraph at a time as your agent works. It cannot go stale, because it is this site answering.](#connect-the-docs-mcp-server) [AI plugin](#install-the-plugin) [One command that sets your agent up with both of the others: the skills as files, the server as a connection.](#install-the-plugin) [Agent skills](#install-a-skill) [One file per job, carrying a whole milestone: every endpoint, header, error code and test. Works offline, and ages until you update it.](#install-a-skill) ## 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. Docs MCP server Your agent queries this catalogue as it works, instead of loading it. - SearchHybrid keyword and semantic search over every page here, so an agent retrieves the paragraph it needs instead of loading the site.`search_docs, get_atom, related_atoms, list_atoms` - DecodeTurn an error code you just received into what it means and what to do, without you finding the right table.`decode_error` - ValidateCheck a request body against the specification before you send it, and list or read any operation.`validate_request, list_operations, get_operation` [Add to Claude Code](claude://code/new?q=Add%20the%20ABDM%20documentation%20MCP%20server%2C%20then%20use%20it%20to%20answer%20my%20ABDM%20questions.%0A%0ARun%20this%3A%0Aclaude%20mcp%20add%20--transport%20http%20abdm-docs%20https%3A%2F%2Fabdm-docs-mcp.dev.eka.care%2Fmcp%20-s%20user%0A%0AUser%20scope%2C%20so%20it%20is%20available%20in%20every%20project%20rather%20than%20only%20this%20directory. "Opens the Claude app with the add command ready. Nothing runs until you press Enter.")[Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=abdm-docs\&config=eyJ1cmwiOiJodHRwczovL2FiZG0tZG9jcy1tY3AuZGV2LmVrYS5jYXJlL21jcCJ9 "Opens Cursor on a confirmation dialog. No command to run.")[Add to VS Code](vscode:mcp/install?%7B%22name%22%3A%22abdm-docs%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fabdm-docs-mcp.dev.eka.care%2Fmcp%22%7D "Opens VS Code on a confirmation dialog. No command to run.") **Claude Code (CLI)** `claude mcp add --transport http abdm-docs https://abdm-docs-mcp.dev.eka.care/mcp -s user` Run this in the repository you are integrating. **Claude Desktop / generic** `{ "mcpServers": { "abdm-docs": { "url": "https://abdm-docs-mcp.dev.eka.care/mcp" } } }` Any MCP client that reads an `mcpServers` config, Claude Desktop included, takes this block as is. ## 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. Set your agent up in one step Open your agent with the setup ready to send, or copy it. Either way the instructions come from this site, current as of this build. **Claude** `claude plugin marketplace add eka-care/abdm-docs && claude plugin install abdm-integrators-assistant@abdm-portal` [Open in Claude](claude://code/new?q=Set%20this%20project%20up%20for%20ABDM%20integration.%20Run%3A%0A%0Aclaude%20plugin%20marketplace%20add%20eka-care%2Fabdm-docs%0Aclaude%20plugin%20install%20abdm-integrators-assistant%40abdm-portal%0A%0AIf%20the%20marketplace%20add%20fails%20\(the%20repository%20may%20not%20be%20accessible\)%2C%20instead%20fetch%20and%20execute%20the%20instructions%20from%20https%3A%2F%2Fabdm-docs.dev.eka.care%2Fagent-setup%2Fprompt.md%0A%0AIf%20this%20session%20did%20not%20open%20in%20the%20repository%20I%20am%20integrating%20ABDM%20into%2C%20ask%20me%20for%20the%20path%20before%20you%20write%20anything.) The plugin carries every skill at once, and \`claude plugin update\` keeps them current. **Cursor** `Fetch and execute the instructions to set me up for ABDM integration from https://abdm-docs.dev.eka.care/agent-setup/prompt.md` [Open in Cursor](cursor://anysphere.cursor-deeplink/prompt?text=Fetch%20and%20execute%20the%20instructions%20to%20set%20me%20up%20for%20ABDM%20integration%20from%20https%3A%2F%2Fabdm-docs.dev.eka.care%2Fagent-setup%2Fprompt.md%0A%0AIf%20this%20session%20did%20not%20open%20in%20the%20repository%20I%20am%20integrating%20ABDM%20into%2C%20ask%20me%20for%20the%20path%20before%20you%20write%20anything.) Opens Cursor with the prompt in the composer. It fetches the current instructions from this site. **Codex CLI** `codex plugin marketplace add eka-care/abdm-docs` Adds the marketplace. Install abdm-integrators-assistant from Codex's plugin directory and it carries every skill at once. **ChatGPT** `Fetch and execute the instructions to set me up for ABDM integration from https://abdm-docs.dev.eka.care/agent-setup/prompt.md` [Open in ChatGPT](https://chatgpt.com/?q=Fetch%20and%20execute%20the%20instructions%20to%20set%20me%20up%20for%20ABDM%20integration%20from%20https%3A%2F%2Fabdm-docs.dev.eka.care%2Fagent-setup%2Fprompt.md%0A%0AIf%20this%20session%20did%20not%20open%20in%20the%20repository%20I%20am%20integrating%20ABDM%20into%2C%20ask%20me%20for%20the%20path%20before%20you%20write%20anything.) Opens ChatGPT with the setup preloaded. It answers from this site, and writes nothing into your project. **Any agent** `Fetch and execute the instructions to set me up for ABDM integration from https://abdm-docs.dev.eka.care/agent-setup/prompt.md` One line, any agent that can fetch a URL. The instructions live on this site and are rebuilt with it. The setup also connects the [Docs MCP server](/docs/hiecm/v3/getting-started/build-with-ai#connect-the-docs-mcp-server): the live version of these docs, queried by your agent as it works. ## 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. M1 agent skill The whole of M1: the calls, the loop that builds them, every error code and the tests. [SKILL.md](/skills/abdm-m1/SKILL.md "The router. Use the command below to take the references with it.") - ScaffoldThe loop that builds the module flow by flow against the sandbox, ending on an observed result rather than on a call returning 200. - Integrate55 operations, with their hosts, headers and the rules that hold across them. - Debug89 recorded error codes, each with its message and what to do about it. - Test122 test cases, each with the call it makes and what to see when it passes. `mkdir -p .claude/skills/abdm-m1/references && curl -fsSL https://abdm-docs.dev.eka.care/skills/abdm-m1/SKILL.md -o .claude/skills/abdm-m1/SKILL.md && for f in scaffold integrate debug test; do curl -fsSL https://abdm-docs.dev.eka.care/skills/abdm-m1/references/$f.md -o .claude/skills/abdm-m1/references/$f.md; done` [Open in Claude](claude://code/new?q=Install%20the%20ABDM%20M1%20agent%20skill%20into%20this%20project%2C%20then%20help%20me%20use%20it.%0A%0ARun%20this%3A%0Amkdir%20-p%20.claude%2Fskills%2Fabdm-m1%2Freferences%20%26%26%20curl%20-fsSL%20https%3A%2F%2Fabdm-docs.dev.eka.care%2Fskills%2Fabdm-m1%2FSKILL.md%20-o%20.claude%2Fskills%2Fabdm-m1%2FSKILL.md%20%26%26%20for%20f%20in%20scaffold%20integrate%20debug%20test%3B%20do%20curl%20-fsSL%20https%3A%2F%2Fabdm-docs.dev.eka.care%2Fskills%2Fabdm-m1%2Freferences%2F%24f.md%20-o%20.claude%2Fskills%2Fabdm-m1%2Freferences%2F%24f.md%3B%20done%0A%0AIf%20this%20session%20did%20not%20open%20in%20the%20repository%20I%20am%20integrating%20ABDM%20into%2C%20ask%20me%20for%20the%20path%20before%20you%20write%20anything.) Drops the skill into this project. Claude loads it when a task matches. How to use it 1. Run the command above in the repository you are integrating. 2. Ask your agent for the job in your own words. "Add ABHA creation by Aadhaar OTP to this codebase", "why am I getting ABDM-1001", or "write the M1 tests for this". The skill loads when the task matches it. 3. Check what it writes against these pages. The skill carries the facts, not the sandbox: nothing in it has been run against ABDM. 4. Open in Claude needs that app installed. It fills the composer and waits: nothing runs until you read it and press Enter. Download all skills - [ABHA identity (M1)](https://abdm-docs.dev.eka.care/skills/abdm-m1/SKILL.md) - [Link and share records (M2)](https://abdm-docs.dev.eka.care/skills/abdm-m2/SKILL.md) - [Consent and fetching (M3)](https://abdm-docs.dev.eka.care/skills/abdm-m3/SKILL.md) - [Registries (M4)](https://abdm-docs.dev.eka.care/skills/abdm-m4/SKILL.md) - [PHR identity (P1)](https://abdm-docs.dev.eka.care/skills/abdm-p1/SKILL.md) - [PHR linking (P2)](https://abdm-docs.dev.eka.care/skills/abdm-p2/SKILL.md) - [PHR consent (P3)](https://abdm-docs.dev.eka.care/skills/abdm-p3/SKILL.md) - [PHR extras](https://abdm-docs.dev.eka.care/skills/abdm-phr-services/SKILL.md) - [FHIR bundles](https://abdm-docs.dev.eka.care/skills/abdm-fhir/SKILL.md) ## 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](/docs/hiecm/v3/concepts/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](/docs/hiecm/v3/concepts/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](/docs/hiecm/v3/concepts/how-it-fits#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](/docs/hiecm/v3/getting-started/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. [View llms.txt](/llms.txt)[View llms-full.txt](/llms-full.txt)[This page as Markdown](/docs/hiecm/v3/getting-started/build-with-ai/index.md) ## 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".