Chartely

For developers & agents

Chronology building built to be called by AI agents

Legal-AI agents are being handed real case files right now, drafting demand letters, prepping depositions, triaging intake, and every one of them needs a trustworthy, page-cited read of the medical records first. Chartely exposes the exact engine behind the site as a REST API and a hosted MCP server, so an agent calls a tool instead of guessing at a scanned PDF.

QuickstartMCP server docs

Quickstart

One key, one call

Get a key at /signup (free account, no card. API access itself is a Pro+ feature), then POST a record set.

request

curl -X POST https://chartely.com/api/v1/chronology \
  -H "Authorization: Bearer cty_live_..." \
  -F "file=@records.pdf"

response 200

{
  "chronology_id": "chr_9f3ac1d0",
  "status": "completed",
  "meta": { "patient_ref": "Jordan A. Rivera", "provider_count": 4, ... },
  "events": [ { "date": "2026-02-03", "event_type": "emergency", "page_ref": 3, ... } ],
  "gaps": [ { "from_date": "2026-03-03", "to_date": "2026-05-19", "days": 77 } ],
  "confidence": 0.91,
  "page_count": 34,
  "request_id": "req_9f3ac1d0"
}

Built for agents

Six things an agent needs from an API

Single-key auth

One API key unlocks the REST API and the MCP server. No OAuth dance, no per-endpoint credentials, a bearer key you generate once in Settings.

Machine-readable docs

A full reference, a spec at /api/openapi, and a plain-text summary at /llms.txt so an agent can onboard itself without a human reading a page first.

Safe by default

Anonymous calls work for a dry run, throttled per IP. Every key is scoped to your plan's rate limit, so a misbehaving agent loop can't run up an unbounded bill.

Reliable & inspectable

Errors are always structured JSON with a stable code, every response carries a request_id for tracing, and idempotency keys make retries safe. Pro+ plans get an exportable request log.

Citations on every call

Every event returns its page_ref and a confidence signal, so an agent can decide whether to trust an event or flag it for review, not just get a date back.

Usage-metered pricing

Priced per page, not per seat, see the machine-readable pricing endpoint or the plans page.

REST API

Every endpoint

Base URL https://chartely.com/api/v1. Optional for /chronology and /pricing (anonymous = throttled trial, no API/MCP access on Free). Send `Authorization: Bearer cty_live_…` (or `x-api-key`) for a Pro/Scale key.

POST

/api/v1/chronology

Build a page-cited chronology from a case medical-record PDF or text - every event dated, cited to its page, with treatment gaps flagged.

curl -X POST https://chartely.com/api/v1/chronology \
  -H "Authorization: Bearer cty_live_..." \
  -F "file=@records.pdf"
POST

/api/v1/chronology/batch

Pro+

Build chronologies for several record sets in one call (Pro: up to 25, Scale: up to 200). One bad file fails only that item, never the whole batch.

curl -X POST https://chartely.com/api/v1/chronology/batch \
  -H "Authorization: Bearer cty_live_..." \
  -F "file=@case-a.pdf" -F "file=@case-b.pdf"
GET

/api/v1/chronologies

Pro+

List the caller's own saved chronologies, newest first.

curl https://chartely.com/api/v1/chronologies -H "Authorization: Bearer cty_live_..."
GET

/api/v1/chronologies/{id}

Pro+

Get one saved chronology with its full event list.

curl https://chartely.com/api/v1/chronologies/CHRONOLOGY_ID -H "Authorization: Bearer cty_live_..."
GET

/api/v1/chronologies/{id}/export

Pro+

Download a saved chronology converted to CSV, JSON or Word.

curl -OJ "https://chartely.com/api/v1/chronologies/CHRONOLOGY_ID/export?format=word" -H "Authorization: Bearer cty_live_..."
GET

/api/v1/pricing

Machine-readable pricing - plans, included pages, per-page overage, rate limits and features.

curl https://chartely.com/api/v1/pricing

Chartely organizes the medical records you provide. It is not legal or medical advice, and automated extraction can misread poor-quality scans. Review the chronology before you rely on it. Every event links to its source page, so review takes minutes, not days.

Full API reference MCP server setup

Usage-metered pricing

Priced by the page, not the seat. Pro includes 1,000 pages/mo then $0.06/page, Scale includes 7,500/mo then $0.04/page. See /api/v1/pricing for the machine-readable version.

See plans & quotas