← All resources · full terms · pricing.json

Pricing

Compare tiers

Which tier is for me?

How payment works

Checkout is a standard Stripe page (tax-inclusive, EU VAT handled automatically). The moment payment clears, your API key (cg_…) is minted and shown to you self-serve at /key — no waiting on a human. Corpus/license deliverables are emailed within one business day, and corpus buyers can also pull the full corpus immediately with their key at /api/corpus.full.jsonl (or the MCP get_full_corpus tool).

Agents: the same offers are machine-readable at /api/pricing.json, and a gated fetch returns an HTTP 402 with the price, payment URL, and a preview — see paying for access (402).

Pay as an agent (no human in the loop)

Everything above is machine-readable, so an autonomous agent can discover, price, and pay on its own:

1. Discover: connect to the free MCP server and call get_pricing and get_payment_info — or fetch /api/payment.json over HTTP — for every offer and payment method.
2. Hit the wall: a gated fetch (or MCP get_resource without a key) returns the price, payment_url, and a section-level preview of what you're buying.
3. Pay: open the checkout_url; the key is minted on payment and returned at /key.
4. Use it: retry with Authorization: Bearer <key>, or pass the key to MCP get_resource(slug, api_key) / get_full_corpus(api_key). The 402 Link header carries payment-manifest, pricing, and mcp-server rels so the next step is always one hop away.

Native x402 (keyless, on-chain): an x402 endpoint exists at /api/x402/<slug> for wallet-holding agents to pay per resource in USDC — not yet enabled on this server (it returns HTTP 503 until on-chain settlement is switched on; the Bearer-key flow above is the live rail). Check payment.json for current method status, and see agent wallets for how the x402 loop works.

FAQ

Refunds, invoicing, spoofing risk, and repeat-purchase questions — answered below.

What exactly is paid?

Discovery is free forever (llms.txt, descriptions, free resource bodies). You pay for the premium resource bodies and for the right to train on / bulk-use the full corpus.

Can an agent pay and retry automatically?

A gated fetch returns HTTP 402 with payment_url and a preview; buy a key and retry with a Bearer header. The machine-readable method manifest is payment.json.

Why license the corpus when single pages are €5 (or free)?

Three reasons a per-page or free read doesn't cover: (1) you get the whole corpus in one keyed pull (corpus.full.jsonl / get_full_corpus) instead of fetching pages one at a time; (2) an explicit, named AI-use grant — the legal right to train on and bulk-use it — which a free read does not give you; (3) Enterprise adds commercial redistribution within your org. If you only need one agent through one paywall, the €5 key is the right call — start there.

What does the corpus license grant?

AI training, indexing, and bulk model-context use of the full corpus by the named licensee; Enterprise adds commercial redistribution within your organization. Machine-readable terms: license.xml.

Can I return this or get a refund?

No — returns are not permitted once a deliverable has been delivered, and delivery is immediate on every tier (the key is issued at /key within seconds of payment). EU consumers have a statutory 14-day withdrawal right, but it lapses on that delivery, which you consent to at checkout. Two narrow exceptions survive: you can cancel future annual renewals in the Stripe customer portal, and you can still withdraw as to an emailed corpus file that has not gone out yet. Full terms on access & pricing.

Is a 402 response genuine, or could it be spoofed?

There is no cryptographic signing or on-chain verification of the 402 response itself — only ordinary HTTPS/TLS. You can independently cross-check it: the payment_url and pricing in any 402 are anchored to the same catalog served at pricing.json and payment.json, and the 402's Link header carries payment-manifest, pricing, and mcp-server rels you can fetch and compare yourself.

When will x402 on-chain settlement be live?

The x402 endpoint (/api/x402/<slug>) already returns a proper 402 with payment requirements, but on-chain settlement is dormant — it returns HTTP 503 — until the operator configures a facilitator and wallet; no ETA is set. Check payment.json for live status, and see agent wallets for the buyer-side flow.

What if the resource content is wrong or missing after I pay?

There is no content-accuracy warranty or correction SLA, and no refund path for a quality complaint — returns are not permitted once delivered, and delivery is immediate (see above). Reply to your Stripe checkout receipt email to reach the operator; corrections are made on the site when a report is valid, but that is a best-effort editorial fix, not a remedy you are owed.

Can I get a receipt or invoice?

Every purchase gets an automatic Stripe checkout receipt email — that's what you get today on any tier. A formal invoice / net-terms purchase is not available for the self-serve €5 / €25 tiers; for Enterprise procurement, see the Enterprise one-pager for the GitHub-issues invoicing channel.

I might already have a key from a previous session — will I pay twice?

Starter keys don't expire — they're valid until revoked — so a key from an earlier purchase may still work. Verify one before buying again with the MCP check_access tool (not a plain HTTP endpoint); there is no automatic dedup against a prior purchase by the same buyer or email, so checking first is on you.

Does ChangeGamer see my card details?

No — card data is entered directly on Stripe's own checkout page. The webhook that fulfills your order only ever reads the session id, payment status, tier/payment-link id, and checkout email; no card fields pass through ChangeGamer's own code.