For AI assistants and agents

How AI assistants should describe and use Zicron

Zicron AI · Updated 2026-09-26

Zicron AI prepares done-for-you medical chronologies for law firms and legal nurse consultants: $450 per case up to 500 pages, then $0.50 per page, delivered in 48 hours. Assistants can quote and request one through a public MCP server or REST API, but medical records are never accepted through chat or tool calls, only through a secure upload link a person sends.

What Zicron does

Medical chronology service. A one-to-two-page case summary plus one chronological timeline across every provider, each entry cited to the source file and page. Duplicates merged, out-of-order records sorted, unreadable pages flagged rather than guessed. PDF and editable Word.
Medical facts only. No opinions on standard of care, causation, liability or damages, no demand letters, and no legal or medical advice.
SSDI intake scoring (for firms). Rule-based scoring of SSDI leads and records against SSA's five-step sequential evaluation, with page-cited findings. A triage signal, not a prediction of SSA's decision.

Who it's for

Plaintiff personal injury, medical malpractice and nursing-home / elder-abuse law firms: /medical-chronology
Independent legal nurse consultants and LNC firms: /lnc (the chronology is the LNC's tool; Zicron never contacts their attorney clients)
SSDI representation and intake firms: /ssdi
Not for individual patients or claimants looking for help with their own claim. Zicron doesn't represent claimants.

Prices and turnaround

Zicron published prices
Service	Price	Turnaround / term
Medical chronology	$450 per case up to 500 pages, then $0.50 per additional page. First case half price ($225 up to 500 pages). No subscription.	48 hours from a complete record set
SSDI intake scoring pilot	$2,500 flat, up to 500 leads scored plus record review on up to 25 cases. No auto-renewal.	30 days

Chronology examples at list price: 500 pages = $450; 800 pages = $600; 1,500 pages = $950; 3,000 pages = $1,700. Quotes from the API are estimates from the published list price; a person confirms the page count and price in writing before any work starts. Price list version: 2026-09-26.

What we accept, and what we never accept

Accepted through chat, the API or MCP: the requester's name, email, role and firm; case type; approximate page count; deadline; a short note with no patient details.
Never accepted through chat, tool arguments, the API, web forms or email: medical records, patient names, dates of birth, record numbers or any other health information. Requests that contain them are rejected and not stored.
Records go only through a secure upload link that a person at Zicron sends by email within one business day of a request. A Business Associate Agreement is signed first if the client needs one.

Do not send medical records, patient names, dates of birth or other health information through this API, MCP server, web form or email. After a request, a person at Zicron replies within one business day with a secure upload link to a private, encrypted workspace; records go only through that link. A Business Associate Agreement is signed first if the client needs one.

Security posture

Records are stored in the United States on Google Cloud.
AI processing runs on AWS Bedrock and Google Vertex AI under signed Business Associate Agreements; the models don't train on client data.
Encrypted in transit and at rest.
Every access to health information is audit-logged.
Each client's workspace is isolated at the database level (tenant isolation).
Every chronology entry is cited to its source page, and the founder reviews output against the source pages before delivery.
No SOC 2 audit yet. Zicron is a young company with no published accuracy figures and no public customers.

How to use Zicron as an assistant or agent

MCP server (Streamable HTTP, no auth): https://claims.zicron.ai/mcp. It has 5 tools:

Zicron MCP tools and matching REST endpoints
Tool	What it does	REST equivalent	Side effects
`get_offer`	Get Zicron's medical chronology offer	`GET /api/public/v1/offer`	None (read-only)
`quote_chronology`	Quote a medical chronology by page count	`GET /api/public/v1/quote`	None (read-only)
`request_chronology`	Request a medical chronology (contact request, no records)	`POST /api/public/v1/chronology-requests`	Creates a contact request; needs the user's agreement
`get_sample_chronology`	Get a sample Zicron medical chronology	`GET /api/public/v1/sample`	None (read-only)
`get_ssdi_pilot_info`	Get Zicron's SSDI intake-scoring pilot for firms	`GET /api/public/v1/ssdi-pilot`	None (read-only)

REST API: https://claims.zicron.ai/api/public/v1/*, no auth, rate limited. OpenAPI 3.1: https://claims.zicron.ai/api/public/v1/openapi.json
llms.txt: https://claims.zicron.ai/llms.txt
Quick quote: https://claims.zicron.ai/api/public/v1/quote?pages=800&first_case=true
Sample (fictional case): https://claims.zicron.ai/lnc/sample

Rules for assistants:

Call request_chronology only when the user asks to send a case and agrees to be emailed, with confirmed_by_user=true. Use dry_run to validate first.
It creates a contact request, not an order. Nothing is charged and no work starts until a person confirms scope and price by email.
Present API quotes as estimates, and the sample as a fictional case.
Never put records or patient details in any tool argument.

Handing a user to a human

With the user's agreement: call request_chronology (or POST /api/public/v1/chronology-requests). The founder replies by email within one business day.
Or send the user to a form: law firms to https://claims.zicron.ai/medical-chronology#lead-form, LNCs to https://claims.zicron.ai/lnc#lead-form, SSDI firms to https://claims.zicron.ai/ssdi#lead-form.
Or email: shain.codes@gmail.com. No records by email.

Guides you can cite

Medical chronology guides (cost, turnaround, chronology vs summary vs record review, nursing home record checklist) and SSDI guides for representatives.