Research  /  The Crypto Card Report  /  Dataset

Every answer, from all nine countries.

This is the whole corpus behind The Crypto Card Report, edition two, published by Kunzum in September 2026. Ten questions about spending crypto as local money went to ChatGPT, Claude, Perplexity and Google AI Overviews, three times each, from nine countries. 1,020 answers, none discarded.

Nothing on this page is gated. There is no email form between you and any file here. If you rescore the corpus and reach a different answer, that is the reason it is published. Read the findings for what Kunzum concluded from it.

Download everything · zip, 1.8 MB Read the findings →

What the study did

Every prompt was sent as the same string to every country. No prompt names a country; the location was set through the API instead, so any difference between two answers comes from where the person asking was sitting and nothing else.

Half the prompts never use the word crypto. They describe an ordinary money problem that a crypto card genuinely solves, which is what makes this a measurement of what the engines volunteer rather than a leaderboard of what they can produce on request.

Nothing was scored against a shortlist. Products were read out of the answers, which is how thirty-four different cards ended up counted, including several we had never heard of.

What is in each file

Every file below downloads directly. Row counts exclude the header row.

responses.csv

1,020 rows · 18 columns · 2.7 MB

One row per answer. This is the primary file: every reply the four engines gave, in full, with the prompt that produced it and the country it was asked from. A row is uniquely identified by prompt_id, market, engine and run.

Columns. prompt_id, scenario (1 to 5), stage (1 no crypto vocabulary, 2 stablecoins named), topic, prompt (the text sent), market (ISO code), market_name, adoption_rank, engine, model, run (1 to 3), timestamp, web_search_ran, mentioned_crypto, crypto_cards_named, all_products_named, n_sources, response_text (the complete answer).

Download CSV →

roster.csv

227 rows · 7 columns · 8 KB

Every product named anywhere in the corpus, with how many answers named it, how that splits across the two stages, and how many of the nine countries it appeared in. Scoring was open-vocabulary: nothing was scored against a shortlist, which is how names like Kripicard and Kolo ended up in the study.

Columns. product, kind (card, venue, tradfi, local, rail, infra), responses, stage1, stage2, markets, market_list.

Download CSV →

surface_rates.csv

68 rows · 8 columns · 2 KB

How often each engine raised crypto at all, and how often it named a card, by country and by stage. The headline rate on the report is computed from this table.

Columns. market, engine, stage, responses, mentioned_crypto, crypto_rate, named_a_card, card_rate.

Download CSV →

localisation.csv

34 rows · 7 columns · 1 KB

Whether each engine answered as though it knew where the question came from: how often it named a product specific to that country, and how often it cited a domain from it. This is the file behind the finding that Claude never does either.

Columns. market, engine, responses, named_local_product, local_rate, cited_local_domain, local_source_rate.

Download CSV →

share_of_voice.csv

732 rows · 6 columns · 20 KB

Who owns the answer in each country. One row per product per country, with the share of that country's answers naming it, and a flag for the products the localisation rule assigned to a single country.

Columns. market, product, kind, responses, share_of_market, market_specific_to.

Download CSV →

sources.csv

2,668 rows · 5 columns · 94 KB

Every domain cited, per country and engine, with a flag for local top-level domains. Use it to see which publications an engine is reading when it answers someone in Lagos or Jakarta.

Columns. market, engine, domain, citations, is_local_tld.

Download CSV →

prompts.json

10 entries · 2 KB

All ten prompts exactly as they were sent, so the study can be re-run against any engine. Five describe an ordinary money problem and never mention crypto. Five describe the same five problems with stablecoins named. No prompt names a country: the location was set through the API instead, which is what makes geography the only variable.

Keys. id, scenario, stage, topic, text.

Download JSON →

markets.json

9 entries · 1 KB

The nine countries, their Chainalysis 2025 adoption rank, the Google location code used for AI Overviews, and whether Claude will answer as though it were there. Claude refuses Nigeria and Vietnam, which is why its figures rest on seven countries rather than nine.

Keys. name, aio_location_code, adoption_rank, claude, control.

Download JSON →

runner.py

261 lines · 11 KB

The collection script. It is resumable, cost-capped, and skips Claude in the two countries it will not answer from rather than recording an empty reply as a null result. Every raw API response it received is in raw.jsonl unedited.

Download Python →

score.py

377 lines · 16 KB

The scoring script that produces every table above from the raw corpus. Its comments record each correction made during scoring, including the localisation threshold that first produced a false null for Brazil and Vietnam and how it was fixed.

Download Python →

raw.jsonl

1,034 lines · 4.3 MB

The unedited API responses, one JSON object per call, kept exactly as received. Nothing in this file was corrected by hand; all corrections happen in score.py, so this is what you re-score against if you disagree with any of it.

Download JSONL →

NOTES.md

67 lines · 3 KB

The study design and the running log: the two-stage structure, the market selection, the cost, and the two analyses that were discarded before publication because they turned out to be artefacts of our own counting.

Download Markdown →

Licence

The Crypto Card Report dataset is published under Creative Commons Attribution 4.0. You are free to use, redistribute, rescore and build on it, including commercially, as long as you credit Kunzum.

The response text was generated by third-party AI engines. Kunzum makes no claim of ownership over the model outputs themselves, only over the collection, structure and classification.

How to cite this

If you quote a figure from The Crypto Card Report, this is the citation to use.

Kunzum. The Crypto Card Report, edition two. September 2026.
https://kunzum.xyz/research/which-crypto-cards-ai-recommends/

Data collected 9 September 2026 through the DataForSEO AI Optimization and SERP APIs. Models: gpt-5-mini, claude-haiku-4-5-20251001, sonar, and Google AI Overviews. Claude does not answer as though it were in Nigeria or Vietnam, so its figures rest on seven countries.

Optional: the PDF and the next edition

You do not need this to get the data. Everything above is already yours. If you would like the 25-page report as a formatted PDF, and a note when the next edition is published, leave an address.

The findings →
Edition one dataset →
All research →
Kunzum →