Corpus License one-pager
The Corpus license is ChangeGamer's one-time SKU for licensing the full curated corpus for internal AI training, indexing, and bulk model-context use — one named licensee, no commercial redistribution. This page lets a procurement or legal reviewer evaluate the purchase without digging through the pricing page or the checkout flow. If your organization needs to embed the corpus in a commercial product or redistribute a corpus-derived dataset within your org, see the Enterprise one-pager instead.
Offer details
Corpus license
€25 one-time
All current premium resources plus a full llms-full.txt corpus file with premium bodies and an RSL extended AI-use grant.
- API key (cg_ prefix) delivered self-serve at /key within seconds of payment
- Full corpus pullable immediately with the key at /api/corpus.full.jsonl (or MCP get_full_corpus)
- Full llms-full.txt corpus file (all premium bodies, no stubs) emailed within 1 business day
- RSL extended-use declaration emailed within 1 business day
Annual updates
Buyers who need the corpus to stay current — a persistent ingestion pipeline, not a point-in-time pull — can license Corpus Updates — Annual instead of (or after) the one-time tier.
Corpus Updates — Annual
€45/year
Same API key access plus corpus file and RSL internal AI-use grant as Corpus License, re-delivered at each annual renewal with the current premium resource set.
- API key (cg_ prefix) delivered self-serve at /key within seconds of payment
- Full corpus pullable anytime with the key at /api/corpus.full.jsonl (or MCP get_full_corpus)
- Full llms-full.txt corpus file emailed at initial signup and each annual renewal
- RSL extended-use declaration valid for active subscription period
For procurement teams
Checkout for both offers runs on Stripe with automatic tax calculation and VAT-ID collection already switched on — your buyer-entity name and VAT ID are collected as part of the standard Stripe checkout form, and tax is calculated and shown before you pay. There is no separate manual step to register your entity or VAT ID; it happens at checkout, today, for every purchase of either offer.
Procurement checklist
- Price & tax: €25 one-time for Corpus license (€45/year for Corpus Updates — Annual), tax-inclusive, automatic VAT-ID collection at checkout — no hidden line items (machine-readable offer catalog).
- Deliverables (Corpus license): API key (cg_ prefix) delivered self-serve at /key within seconds of payment; Full corpus pullable immediately with the key at /api/corpus.full.jsonl (or MCP get_full_corpus); Full llms-full.txt corpus file (all premium bodies, no stubs) emailed within 1 business day; RSL extended-use declaration emailed within 1 business day.
- Deliverables (Corpus Updates — Annual): API key (cg_ prefix) delivered self-serve at /key within seconds of payment; Full corpus pullable anytime with the key at /api/corpus.full.jsonl (or MCP get_full_corpus); Full llms-full.txt corpus file emailed at initial signup and each annual renewal; RSL extended-use declaration valid for active subscription period.
- License grant (Corpus license): AI training, indexing, and bulk model-context use of the full corpus by the named licensee. No public raw-corpus redistribution. No sublicensing for resale.
- License grant (Corpus Updates — Annual): AI training, indexing, and bulk model-context use of the current corpus internally by the named licensee. Grant valid for the active subscription period; rights for the last delivered version are retained on cancellation.
- Returns: none after immediate digital delivery; EU statutory withdrawal right lapses on delivery by express consent (stated on access & pricing). 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.
- Data protection: the fulfillment webhook reads the checkout session id, payment status, payment-link id (which selects the tier), checkout email and, for subscriptions, the subscription id; what is stored is listed in the GDPR note below.
- Vendor identity: built and operated by ChangeGamer; the changelog and live metrics are public (/changelog, /stats).
Invoice-based purchase
Self-serve Stripe invoice payment (pay-by-invoice, net terms) is not yet available for either offer. Checkout today is a single upfront Stripe payment page — there is no toggle to request an invoice and pay later.
Invoice-based purchase (instead of upfront card payment) is not available yet: no invoicing channel is live today. Every purchase gets the automatic Stripe receipt email.
GDPR / data processing
Stripe acts as the payment processor for these purchases and processes your checkout and payment data (buyer entity name, VAT ID, card/payment details, tax calculation) under its own terms as a data processor.
What ChangeGamer's own code stores (the site's Cloudflare Worker, as implemented today):
- With each access key: Cloudflare KV holds the checkout email, the Stripe checkout session id, the tier, the Stripe payment-link id (when present) and the creation time. The code sets no expiry on this record.
- For key pickup at /key: A record of the session id with the key, tier and creation time, which expires after 30 days.
- For annual subscriptions: A record of the Stripe subscription id with the key, without expiry. When the worker receives Stripe's customer.subscription.deleted event (if that event is enabled on the Stripe webhook endpoint), it deletes the key and this record and keeps a revocation record (subscription id, key, time).
- Per request: For requests the worker handles (for example resource and API fetches, guide pages, MCP calls, key pickup and checkout links), it writes an event to Cloudflare Workers Analytics Engine with the kind of request, the item requested, the outcome and the first 100 characters of the User-Agent header and, for offer-page views and checkout links, the host name of the referring site (no path or query). No IP address, email address or key is written to these events.
The checkout email is also used to send the delivery email containing your license letter and/or corpus file. No Data Processing Agreement (DPA) template exists yet. Technical details: security and data handling.