For agents

What this is

• Licium keeps public web pages that break ordinary scrapers working, and turns them into clean rows.
• Sources are re-read daily, and asking for a source you care about starts a fresh read of it. The date on every row is when we actually read that page.
• Right now: 195 maintained sources, 105 of them current, 9,702 rows behind them.
• Every row names the source it came from and the date we read that page.
• Sources we currently cannot read are listed as broken instead of quietly dropped. A catalog that never reports a problem is not being watched.

What you can do without a key

• Browse everything we maintain, read any single source, take its rows as JSON or CSV, and queue a page we do not cover yet.
• There is no signup, no trial, and no rate limit worth worrying about for normal use.
• A key is only needed for scheduled deliveries into your own table, which is a paid arrangement made with a person.
• If a resource ever needs paying for, you will get an HTTP 402 with x402 payment terms rather than a login wall. Nothing is priced today.

Start here

GET https://www.licium.ai/v1/sources               — everything we keep working
GET https://www.licium.ai/v1/sources?q=hospital     — search it
GET https://www.licium.ai/v1/sources/{id}           — one source, with its limits stated
GET https://www.licium.ai/v1/sources/{id}/rows      — the rows (add ?format=csv for a file)
GET https://www.licium.ai/v1/bundles                — sources grouped the way people order them

If we do not have the page you need

This is the useful case, not the failure case. Ask for it:

  curl -X POST https://www.licium.ai/v1/requests \
    -H "Content-Type: application/json" \
    -d '{"url": "https://the-page.example/list", "fields": ["title", "url"]}'

If it turns out we already cover it, you get the source and its rows straight back.
If not, you get a request id. Poll it:

  GET https://www.licium.ai/v1/requests/{request_id}

States are queued, live, or declined. Declined means stop polling; nobody is going to change their mind quietly.
Pages that fight back are the intended case. Registries, notice boards, JS-heavy directories, PDF lists.

MCP

• Endpoint: https://www.licium.ai/mcp (streamable HTTP, JSON-RPC 2.0, no auth)
• Tools: list_sources, get_source, get_rows, request_source.
• Discovery: https://www.licium.ai/.well-known/ai-catalog.json and https://www.licium.ai/.well-known/agent-card.json

What we will not do

• We do not crawl your URL the moment you POST it. Requests are queued and a person decides.
• We do not scrape anything behind a login, and we do not take private data.
• We do not report a number we have not checked. If a count was not independently verified, the source says so.
• We will not tell you how a given page is extracted. You get the rows and their provenance, not the method.

What it costs

• Reading the catalog and taking rows from it: free, no key.
• Keeping a source you asked for alive on a schedule and delivered into your table: paid, arranged with a person at hello@licium.ai.
• Pricing is per source and per month, because what you are buying is the maintenance, not one download.

Bundles we currently keep

• AABB accredited blood facilities (national) — 1 sources, 1,102 rows
• Nassau County public bid notices — 78 sources, 882 rows
• New York State health facility profiles — 8 sources
• Ohio ambulatory surgery centers (three sources reconciled) — 3 sources, 521 rows
• Rural hospitals and clinics, national (CAH · REH · RHC) — 1 sources, 6,975 rows
• Rural hospital leadership contacts — 104 sources, 266 rows