QuanticData for AI agents: read, register, pay and call

Read us as data, not as a website

Nothing on quanticdata.io needs a browser. Every page has a Markdown twin at the same URL plus index.md, announced in the page head with <link rel="alternate" type="text/markdown">, and the whole site is concatenated in one file. The API reference exists as HTML, Markdown, OpenAPI 3.1 and a Postman collection, so an agent can read the shape of every call before it makes one.

• Start here: llms.txt, the curated index of every product, tool, collector and guide, with a section written for agents at the top.
• Any page as Markdown: append index.md; this page is for-agents/index.md. The whole site: llms-full.txt.
• The API reference: docs, docs/index.md, openapi.json, openapi.yaml and postman.json. The Agents tag documents registration and the checkout below.
• Credentials, written for agents: auth.md, one file that says which credential each surface wants and how to obtain it.

Three ways to authenticate

One account holds everything: the API key calls the data API, lists and generates proxies from the plans, and completes a checkout. How the credential is issued depends on who is at the keyboard.

Anonymous registration and identity assertions are not offered: a person always confirms the account once, by reading one code. After that the agent runs alone, and the person can see, rotate or revoke the key at any time.

What the agent can do with that key

The 29 MCP tools and the REST endpoints are the same calls with the same prices: every successful call is billed at its unit price, a failed, blocked or empty call is not.

What to ask the human, and what never to ask

An agent on QuanticData needs a person exactly twice, and both moments are designed to be short.

• The code, once. Before registering, tell the person which service you are registering with. Then ask them for the 6 digits in the email whose subject ends with "an AI agent asked to register". The code lives 10 minutes.
• A top-up or a plan, when the balance is short. A checkout the balance cannot cover answers requires_escalation with a continue_url: give the person that link and stop. They pay by card, PayPal or crypto on the dashboard; you poll the session until it is completed.
• Never a password: the account the agent opens has none the agent knows; the person signs in through the password reset link.
• Never card details: the agent holds one instrument, the prepaid balance of its own account. Cards exist only on the dashboard, in the person's hands.
• Never the key in chat: it is returned once, by the API, and belongs in an environment variable. The person can rotate or revoke it from the API keys page.

Buy a plan by itself

QuanticData publishes a checkout in the Universal Commerce Protocol shape (UCP, capability dev.ucp.shopping.checkout) at /.well-known/ucp. The agent opens a session for one plan from GET /v1/public/plans, reads the real total, and completes it with the one payment handler an agent owns, the account balance, at 0% VAT. If the balance is short, the session carries the link where the person finishes the order. The plainer, non-UCP way to do the same is POST /v1/public/purchase. Step by step: let an agent buy proxies.

POST https://api.quanticdata.io/v1/agent/ucp/checkout-sessions
Authorization: Bearer qd_live_…      Idempotency-Key: order-2026-10-26-001
{"line_items":[{"item":{"id":"PLAN_ID"},"quantity":1}],"payment_method":"BALANCE"}

→ 201 { "status": "ready_for_complete", "totals": [ … ], "continue_url": "…" }

POST …/checkout-sessions/SESSION_ID/complete
{"payment":{"instruments":[{"handler_id":"balance","type":"account_balance","selected":true}]}}

→ 200 { "status": "completed", "order": { "id": "ord_…" } }   # then POST /v1/public/proxies/generate

Prices and limits an agent can read

Unit prices are published on the pricing page and in llms.txt; the live list with the account's own discount comes back from GET /v1/scraper/billing. The entry prices an agent meets first:

• Free tier: $2 of free API usage every month on every account, no card to start, renewed monthly.
• No subscription, $0 monthly minimum: pay as you go from a prepaid balance that does not expire; the smallest top-up the dashboard accepts is $5.
• Limits on pay as you go: 20 requests a minute per key and 5 concurrent batch slots; the paid tiers raise both and discount unit prices by 10% to 30% (see rate limits and tiers). A 429 carries Retry-After and is not billed.
• Registration caps: 5 registrations an hour and 20 a day per IP, 3 codes an hour per email, 5 wrong codes cancel a registration.

Discovery endpoints

Everything an agent needs to find by itself, in the formats the standards prescribe:

Paste into AGENTS.md or CLAUDE.md

These lines give a coding agent the whole picture in the place it keeps standing instructions. They repeat what the five skills say, in the short form a repository wants.

## QuanticData (web data, SERP, proxies)
- Read first: https://quanticdata.io/llms.txt (index), https://quanticdata.io/auth.md (credentials),
  https://quanticdata.io/docs/index.md (API reference as Markdown).
- Install the skills once: npx skills add https://quanticdata.io
- MCP: claude mcp add quanticdata -e QUANTICDATA_API_KEY=... -- npx -y quanticdata-mcp
  or the hosted server https://api.quanticdata.io/mcp (OAuth, no key to copy).
- The key lives in QUANTICDATA_API_KEY, never in code, logs or chat. No key yet: follow the
  verified-email registration in auth.md; tell the user first, then ask them for the 6-digit code.
- REST: https://api.quanticdata.io/v1, Authorization: Bearer; every reply is
  {type, message, payload}; type "error" is never billed.
- Budget before big jobs: GET /v1/scraper/billing (prices, free allowance left, balance).
  Pay as you go allows 20 requests a minute: use /v1/batch for many URLs, /v1/serp/bulk for many pages.
- Buying a plan: POST /v1/agent/ucp/checkout-sessions, complete it from the balance only.
  If the balance is short, give the user continue_url and stop. Never ask for card details.