Anatomy IT for developers
Developer documentation for www.anatomyit.com. Last updated .
Anatomy IT provides healthcare IT, cybersecurity and compliance services. This website offers a small public surface to programs and AI agents: every page as Markdown, an MCP server, an A2A agent and a REST API with an OpenAPI 3.1 description. This page documents all of it. For the facts about the company itself, read AI Instructions + Information.
When to use this
- To answer a question about Anatomy IT (its services, solutions, the organizations it serves, its leadership, news or blog posts): read the page as Markdown, or call the
get_pagetool. No credentials are needed. - To ask Anatomy IT to contact a person who has asked for that: call
submit_contact_request, or the REST endpoint behind it. This needs a token, and tokens are issued to registered agents only. - Not for anything else. There is no access to client data, tickets, accounts or pricing here. Anatomy IT clients get support through the client support and portal page.
Read the site as Markdown
Every public page has a Markdown copy. Ask for it in either of two ways:
- Add
.mdto the address of the page. The home page is/index.md. - Send an
Acceptheader that preferstext/markdownovertext/html.
curl https://www.anatomyit.com/services/cybersecurity-risk-management.md
curl -H "Accept: text/markdown" https://www.anatomyit.com/services/cybersecurity-risk-management
To find the right page, start from llms.txt, which lists the main pages with a sentence on each, or from sitemap.xml, which lists every public address. An address that does not exist answers 404 with a short Markdown body when Markdown was asked for.
MCP server
The MCP (Model Context Protocol) server is at https://www.anatomyit.com/mcp. It speaks protocol version 2025-06-18 over Streamable HTTP: one POST with a JSON-RPC message, one JSON object back. It keeps no session and has no event stream. It identifies itself as anatomy-it-mcp, version 1.0.0.
| Tool | What it does | Needs |
|---|---|---|
get_page | Returns one page of www.anatomyit.com as Markdown. One argument, path, such as /services/cybersecurity-risk-management or / for the home page. | Nothing |
submit_contact_request | Sends a contact request for a person who asked to be contacted. Same fields as the contact request in the REST API below. | A Bearer token with the scope leads:write on the Authorization header of the request |
Call a tool:
curl -X POST https://www.anatomyit.com/mcp \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": {"name": "get_page", "arguments": {"path": "/about"}}}'
A tool that ran and failed answers with isError: true and a message in its result. A call that names a tool the server does not have answers a JSON-RPC error with the code -32602. The server card is at /.well-known/mcp/server-card.json.
REST API
The API has three operations. The full description, with every field, status and error, is the OpenAPI 3.1 document at /openapi.json.
| Method and address | What it does | Needs |
|---|---|---|
GET /api | Returns the name and version of the API and a list of its public endpoints. | Nothing |
POST /api/agent/token | Returns a Bearer token, good for one hour, with the scope leads:write (OAuth 2.0 Client Credentials). | The client_id and client_secret of a registered agent |
POST /api/lead/contact | Sends a contact request to Anatomy IT, the same one the form on the contact page sends. | A Bearer token. Without one, the request must carry a Turnstile token that only a browser on the contact page can obtain. |
Get a token:
curl -X POST https://www.anatomyit.com/api/agent/token \
-d grant_type=client_credentials \
-d client_id=YOUR_CLIENT_ID \
-d client_secret=YOUR_CLIENT_SECRET
Send a contact request:
curl -X POST https://www.anatomyit.com/api/lead/contact \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_TOKEN" \
-d '{"fields": {"firstname": "Jordan", "lastname": "Rivera",
"email": "jordan.rivera@example.com", "state_name": "NY",
"reason_for_inquiry": "Sales",
"message": "We are a 40-provider practice looking for managed IT."}}'
The fields of a contact request:
| Field | Required | Value |
|---|---|---|
firstname | Yes | First name |
lastname | Yes | Last name |
email | Yes | Business email address |
state_name | Yes | US state, as its two-letter postal code |
reason_for_inquiry | Yes | General, Sales, Partner or Media |
phone | No | 7 to 20 characters |
company | No | Organization name |
jobtitle | No | Job title |
how_did_you_heart_about_us | No | Referral, Webinar, Event, Social, News Story or Online Search. The field name is spelled this way. |
message | No | Up to 2,000 characters |
A request that is accepted answers 200 with {"ok": true, "message": "..."}. Every request sent with a token is marked in Anatomy IT's records as submitted by an agent, with the name of the registered client.
A2A agent
The same two capabilities are offered over the A2A (Agent2Agent) protocol at https://www.anatomyit.com/a2a, with the JSON-RPC binding. Send a SendMessage request whose message has a part with a data member that names the skill and its arguments:
curl -X POST https://www.anatomyit.com/a2a \
-H "Content-Type: application/json" \
-d '{"jsonrpc": "2.0", "id": 1, "method": "SendMessage",
"params": {"message": {"parts": [{"data":
{"skill": "get_page", "arguments": {"path": "/about"}}}]}}}'
Every call completes in one response and no task is stored. The agent card is at /.well-known/agent-card.json.
Authentication and registration
- Reading needs no credentials: Markdown pages,
get_pageandGET /apiare open. - Sending a contact request needs a token. Registration is reviewed by a person and is not self-serve: ask through the contact page, saying that you operate an agent and want API access. An approved agent receives a
client_idand aclient_secret. - The token comes from
POST /api/agent/token, lasts one hour and carries the scopeleads:write. Send it asAuthorization: Bearer <token>.
auth.md gives the full steps. The OAuth metadata is at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/api/lead/contact.
Errors
Every error from the API is a JSON object with an error member. Some also carry a message. Token errors follow OAuth 2.0 and may carry error_description instead.
| Status | error | Meaning |
|---|---|---|
| 400 | invalid_fields | A field failed validation. fieldErrors has one message per field. |
| 400 | Send application/json, Invalid JSON, Send a JSON object | The contact request could not be read. Here error is a sentence, not a code. |
| 400 | invalid_request, unsupported_grant_type, invalid_scope | The token request was not well formed. |
| 401 | invalid_client | Unknown client or wrong secret. |
| 401 | invalid_token | The Bearer token is expired, not valid or lacks the scope. |
| 403 | challenge_failed | No Bearer token was sent and the Turnstile check did not pass. |
| 404 | not_found | No API endpoint lives at that address. |
| 405 | method_not_allowed | The endpoint exists but does not answer that method. |
| 503 | not_configured | This deployment does not issue tokens. |
| 502 | upstream_unreachable, upstream_error | The request could not be passed on. Safe to try again. |
Discovery files
- /llms.txt: the main pages of the site, with a sentence on each.
- /openapi.json: the OpenAPI 3.1 description of the REST API.
- /.well-known/api-catalog: every machine-readable address in one list (RFC 9727).
- /.well-known/mcp/server-card.json: the MCP server card.
- /.well-known/agent-card.json: the A2A agent card.
- /.well-known/agent-skills/index.json: two agent skills, one for reading a page and one for sending a contact request.
- /.well-known/ai-catalog.json: the catalog that lists the skills and both servers.
- /auth.md: how an agent registers and uses a token.
- /sitemap.xml and /robots.txt: every public address, and the crawler policy.
SDKs, limits and versions
- SDKs: there is no SDK and no command-line tool. The API is three operations, and any HTTP client or MCP client can call it.
- Limits: no rate limit is published. Read at the pace of a person browsing, and send a contact request only when a person has asked for one.
- Versions: the API and the MCP server are both at version 1.0.0, as their descriptions state. The addresses carry no version number.
Questions about this page go through the contact page.