Pricing

Per-call prices in USD. Machine-readable version: /v1/pricing. Payments mode: x402. POST /v1/research costs $0.50 per call (config-driven).

Endpoint	Price (USD / call)
`POST /v1/research`	$0.50
`GET /v1/search`	$0.02
`GET /v1/tenders/:id`	$0.02
`GET /v1/companies/:id`	$0.05
`GET /v1/companies/:id/awards`	$0.05
`GET /v1/companies/:id/opportunities`	$0.10
`GET /v1/buyers/:id/history`	$0.05
`GET /v1/renewals`	$0.25
`GET /v1/pricing`	free
`GET /v1/stats`	free
`GET /v1/demo`	free
`POST /v1/billing/credits/5`	$5.00
`POST /v1/billing/credits/10`	$10.00
`POST /v1/billing/credits/25`	$25.00
`GET /v1/billing`	free

GET /v1/demo is free: a labeled sample of the paid data (recent tender + renewal signal), so agents can validate quality before paying.

Credits & billing

Prepaid credit bundles — a one-time purchase. Buy a bundle, then pay every call from your balance by sending x-client-key: <your key> on the request (instead of a per-call payment proof).

Bundle	Price (USD)
`POST /v1/billing/credits/5`	$5.00
`POST /v1/billing/credits/10`	$10.00
`POST /v1/billing/credits/25`	$25.00

Two payment rails, chosen by how you buy: the monthly subscription is paid in EUR by card via Creem (no crypto wallet); pay-per-call and prepaid credits are priced in USD and paid with USDC proofs via x402.

Monthly subscription

Creem MoR: subscribe at POST /v1/creem/checkout for €29.00/month (config-driven — always the configured CREEM_PRICE_CENTS). After payment Creem calls POST /v1/creem/webhook (signature-verified) and the account is marked kind=creem for 30 days. Subscriber calls debit one-time credits — running out returns 402 until you refill.

Buy: POST /v1/billing/credits/5 (or /10 /25) with the normal machine-to-machine payment flow (402 → PAYMENT-SIGNATURE retry). Check balance: GET /v1/billing with header x-client-key: <your key>. MCP: billing_purchase_credits / billing_get_balance.

How payment works

Call a paid endpoint → 402 with a base64 PAYMENT-REQUIRED header describing the exact USDC requirement (scheme exact, EIP-3009 transferWithAuthorization).
Sign the authorization with an x402 client and retry with PAYMENT-SIGNATURE: <payload> (v2; the legacy X-PAYMENT header still works).
The server verifies and settles the payment before serving content; proofs are single-use.
Local dev only (PAYMENTS_MODE=dev): POST /v1/dev-faucet {"endpoint":"<METHOD PATH>"} → { token, expires_at }, then retry with X-PAYMENT (REST) or payment_token (MCP). Not available in production.