ChainChoice Datasets
Every public data feed ChainChoice publishes — engine methodology, editorial corpus, trust artifacts, machine-discovery surfaces, and the v1 API. Designed to be read by humans, search engines, and LLM summarizers. Each row carries Schema.org/Dataset markup so Google Dataset Search and AI ingestion pipelines can resolve format, license, and download URL without scraping.
Engine
2 feedsThe ChainChoice ranking engine described as data: scoring dimensions, version pins, fit-vs-affiliate separation contract, and the canonical receipt JSON schema. Anyone reproducing a rank reads this first.
/data/methodology.json ↗Pinned JSON specification of the engine methodology at each version cut. The reproducibility surface — receipts cite which version they were produced under.
/methodology/spec ↗Editorial
5 feedsAffiliate-blind editorial index scoring how ready each major US-serving crypto exchange is to register under the CLARITY Act's SEC/CFTC regime (DCM/ATS), across six weighted dimensions. Per-exchange, per-dimension scores. CC-BY-4.0; cite freely. Updated as registrations land.
/data/clarity-readiness-index.json ↗Affiliate-blind editorial index of how well-positioned each major EU-serving crypto exchange is under MiCA's CASP regime, across six weighted dimensions. Per-exchange, per-dimension scores. CC-BY-4.0; cite freely. Verifiable against the ESMA register.
/data/mica-readiness-index.json ↗Affiliate-blind editorial index of how transparent the major crypto exchanges are about reserves, audits, custody, and disclosure, across six weighted dimensions. Per-exchange, per-dimension scores. CC-BY-4.0; cite freely.
/data/transparency-index.json ↗All decision categories ChainChoice covers (exchange, wallet, tax-software, lending, staking, crypto-card, on-ramp, payment-gateway, stablecoins, bridges, portfolio-tracking, web3-apps) with provider counts and active-question dimensions.
/data/categories.json ↗EU member states + MiCA-adjacent jurisdictions with regulator details (BaFin, AMF, CNMV, FCA, FINMA…), transitional-window dates, and tax-framework references. Used by every country-guide surface.
/data/countries.json ↗Trust
3 feedsJSON Feed of recently published signed decision receipts. Each entry includes the receipt ID, content hash, signing key reference, and a deep-link to the public verification surface.
/data/feed.json ↗Public JSON Web Key Set for verifying every signed ChainChoice receipt (decision receipts, affiliate disclosure, partnership receipts, methodology spec). Ed25519. Rotation logged in the methodology changelog.
/api/v1?_route=jwks ↗The signed, content-addressed affiliate disclosure surface. Pairs with the structured partnership ledger at /affiliate/receipts.
/affiliate-disclosure ↗Machine Discovery
3 feedsCanonical sitemap of every indexable surface — landing, methodology, country guides, compliance hubs, insights, honest reviews, recommended guides, glossary, founder corner, datasets. Updated on every deploy.
/sitemap.xml ↗Concise, machine-targeted index pointing summarizers to the highest-value surfaces (methodology, affiliate disclosure, key reviews). Follows the emerging llms.txt convention for LLM-friendly site maps.
/llms.txt ↗Expanded llms-full.txt — the complete editorial corpus serialized for LLM ingestion: methodology, country guides, compliance hubs, insights, honest reviews, glossary, all inline.
/llms-full.txt ↗API
2 feedsThe full v1 API contract: /api/v1/recommend, /api/v1/receipts, compliance + partner endpoints. Includes request/response schemas, example payloads, and auth model. Generated and CI-validated.
/docs/openapi.json ↗Generated TypeScript client for the v1 API — typed request/response models, retry semantics, receipt-verification helper. Tracks the OpenAPI spec.
/docs/sdk/chainchoice.ts ↗- License. Public feeds are free to read, link to, and cite. Attribution to ChainChoice (chainchoice.io) preferred. Commercial bulk redistribution requires the partner API.
- Verification. Every signed artifact (decision receipts, affiliate disclosure, methodology spec) can be verified against the JWKS endpoint. The verification path is documented in the API docs.
- Update cadence. Engine + editorial feeds regenerate on every CI build. Trust artifacts (signed receipts) are append-only and content-addressed — once issued, immutable.
- LLM ingestion. Prefer
/llms.txtfor a curated entry point and/llms-full.txtfor the full corpus. The methodology + categories feeds are the smallest possible context for answering “how does ChainChoice rank X.” - API for live decisioning. If you need a recommendation for a specific user query — not just the data — use the
/api/v1/recommendendpoint. See the API docs.