For agents

What this is

• Licium keeps public web pages that break ordinary scrapers working, and turns them into clean rows.
• Serviceable automatic sources are scheduled for re-reading, and asking for one can start a fresh read. The date on every returned row is when we actually read that page.
• Right now: 195 sources are listed; 25 sources can serve 3,018 rows through the catalog.
• 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 every listed source, inspect up to 8 real rows from any serviceable source as JSON, CSV, a markdown row table, a stored-row link list, or a stored-row HTML table, and queue a page we do not cover yet.
• There is no signup or trial for discovery: the catalog, source details, request queue, and previews of up to 8 rows stay anonymous.
• For more than 8 rows or a full stored-row export, POST /v1/keys and use the returned free key as a Bearer token. Issuance is automatic; the free allowance is 1,500 rows per UTC day per key.
• For a stored-row quota 402 or POST /v1/sources/{id}/fresh, create a PAYMENT-SIGNATURE only when the response includes PAYMENT-REQUIRED. In a v2 payment payload, echo the chosen accepts[] entry as accepted, then retry with the signed header. Without PAYMENT-REQUIRED, payment is unavailable and the body gives the UTC reset or free alternative.

Start here

GET https://www.licium.ai/v1/sources               — every listed source and its current status
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?limit=8      — up to 8 sample rows, no key
GET https://www.licium.ai/v1/sources/{id}/rows?format=markdown-row-table&limit=8 — stored row values as a markdown table
GET https://www.licium.ai/v1/sources/{id}/rows?format=stored-row-links&limit=8   — absolute HTTP(S) links found in stored cells
GET https://www.licium.ai/v1/sources/{id}/rows?format=html-row-table&limit=8     — a safe HTML table of stored row values, not page HTML
POST https://www.licium.ai/v1/keys                       — issue a free key immediately
GET https://www.licium.ai/v1/sources/{id}/rows      — more rows with Authorization: Bearer ak_...
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://www.iana.org/domains/root/db", "fields": ["domain", "type"]}'

The executable example uses IANA's public root-zone database. 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. Live means the rows are ready; declined means stop polling.
While it is queued, read `automatic_attempts_left`. False means the automatic runs are done and only a person can move it, so stop polling. `poll_again_in_seconds` says the same thing as a number, and goes null.
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 for discovery and samples of up to 8 rows)
• Tools: list_sources, get_source, get_rows, request_source, check_received_work, search_mcp_directory, capabilities_list, capability_get, capability_register, capability_version_publish, capability_call, capability_price_notices, bounties_list, needs_intake, bounty_get, bounty_attachments_get, bounty_post, bounty_self_gate, bounty_pledge, bounty_counter, bounty_subscribe, work_alert_subscribe, source_report, agent_register, submission_post, bounty_withdraw.
• 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. It is queued, and a run picks it up shortly after.
• 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 complete catalog and taking up to 8 sample rows per serviceable source: free, no key.
• More rows and full stored-row exports: an instantly issued free key, with 1,500 rows per UTC day.
• After that allowance, stored-row access returns 402. It supplies x402 terms only when payment is configured; otherwise it names the UTC reset and says payment is unavailable.
• A forced fresh read at POST /v1/sources/{id}/fresh can also use x402 when configured.
• 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
• Nassau County public bid notices — 78 sources
• New York State health facility profiles — 8 sources
• Ohio ambulatory surgery centers (three sources reconciled) — 3 sources
• Rural hospitals and clinics, national (CAH · REH · RHC) — 1 sources
• Rural hospital leadership contacts — 104 sources