Merchant Intelligence

The dataset behind the directory

Verified merchant stablecoin acceptance — which coins, which chains, which gateway, checked against primary sources and dated. Available as CSV, JSON and an API.

Merchant records
109
Cited sources
235
Change events
127
Gateways tracked
28

Updated on every publish. Current build: .

Look at it before you talk to us

The sample is 20 complete records — provenance, sources and change history included — not a field list. If the shape does not suit you, you will know in two minutes rather than after a call.

Sample: 20 full records (JSON) Full merchant list (CSV) Spend Index (CSV)

What a record contains

Fields available on a merchant record, by tier
Field group Contains Available
Identity Name, slug, canonical website, profile URL, short description Public
Acceptance Stablecoins accepted, settlement networks, direct wallet vs gateway Public
Commerce Category and subcategories, countries, exclusions, global availability Public
Checkout How the payment option is reached, KYC posture, minimums, restrictions Public
Placement Whether the listing is standard, featured or sponsored Public
Verification summary Status, freshness, date verified, last reviewed, source count Public
Verification provenance Methods used, editor note, every source URL with what it supports Research and above
Change history Dated, sourced acceptance changes per merchant Research and above
Historical snapshots Frozen quarterly captures and diffs between them Professional
Webhooks Push notification on acceptance changes Developer and above

Every field marked Public is already visible on the merchant's profile page. Nothing in the dataset is derived from form submissions, listing claims or private correspondence.

Who uses it

  • Payment gateways

    See which merchants route through which gateway, where a competitor has displaced you, and which categories are still unserved.

  • Stablecoin issuers

    Track real merchant acceptance of your asset against others, by category and region, from merchant documentation rather than self-report.

  • Wallets and exchanges

    Power a "where can I spend this?" surface with verified merchants, filtered by the assets and chains your users actually hold.

  • Researchers and analysts

    A citable, dated, source-backed dataset with its methodology and limitations published alongside it.

  • Ecommerce and fintech teams

    Benchmark what comparable merchants accept before committing to a payment stack.

API

These endpoints are live now, need no key, are CORS-open and are free to use with attribution. They are prebuilt documents rather than a query API — the dataset is small enough that pagination would be ceremony.

Public JSON endpoints
Endpoint Returns
/api/v1/merchants.json Every published merchant with acceptance claims and verification summary.
/api/v1/merchants/{slug}.json One merchant in full: provenance, sources, restrictions, change history.
/api/v1/stablecoins.json Stablecoins tracked, with issuer, peg and merchant counts.
/api/v1/networks.json Networks, typical fees and settlement, with merchant counts and the disclosure gap.
/api/v1/categories.json The category tree with merchant counts.
/api/v1/payment-providers.json Gateways profiled, with settlement model and merchant counts.
/api/v1/changes.json Dated, sourced acceptance changes across the directory.
/api/v1/spend-index.json The full Stablecoin Spend Index as computed for the current build.
/api/v1/sample.json Full records for 20 merchants, for evaluation.

Example response

A real record from the current build — HOSTKEY , as /api/v1/merchants/hostkey.json returns it, with the long prose fields shortened for the page. coin_networks is the per-coin map; a coin missing from it has undocumented pairing with every listed network, and consumers must not assume the cross product. 

              {
  "slug": "hostkey",
  "name": "HOSTKEY",
  "url": "https://stablecoinspend.com/merchants/hostkey/",
  "website": "https://www.hostkey.com",
  "short_description": "Dedicated and GPU server provider taking five stablecoins through BitPay — and stating, unusually, that ERC-20 tokens are accepted on Ethereum only.",
  "category": "Web Hosting",
  "category_slug": "hosting",
  "subcategories": [
    "cloud-hosting",
    "developer-tools"
  ],
  "stablecoins": [
    "USDC",
    "USDT",
    "DAI",
    "GUSD",
    "USDP"
  ],
  "networks": [
    "Ethereum"
  ],
  "coin_networks": {
    "USDC": [
      "Ethereum"
    ],
    "USDT": [
      "Ethereum"
    ],
    "DAI": [
      "Ethereum"
    ],
    "GUSD": [
      "Ethereum"
    ],
    "USDP": [
      "Ethereum"
    ]
  },
  "payment_providers": [
    {
      "slug": "bitpay",
      "name": "BitPay"
    }
  ],
  "payment_providers_other": [],
  "direct_wallet_payment": false,
  "checkout_method": "hosted-checkout",
  "online": true,
  "physical_locations": false,
  "countries": [],
  "global_availability": true,
  "excluded_countries": [],
  "kyc_required": "sometimes",
  "tags": [
    "dedicated-servers",
    "gpu-servers",
    "vps",
    "colocation",
    "europe",
    "bitpay",
    "ethereum-only"
  ],
  "placement": "standard",
  "verification": {
    "status": "verified",
    "label": "Verified",
    "fresh": true,
    "date_verified": "2026-09-22",
    "last_reviewed": "2026-09-22",
    "source_count": 3
  },
  "added": "2026-09-13",
  "updated": "2026-09-22",
  "description": "HOSTKEY rents dedicated servers, GPU servers for AI and HPC, VPS and private cloud from TIER III data centres in the Net…",
  "minimum_payment": null,
  "payment_notes": "HOSTKEY's payment-terms page says: \"We accept P2P cryptocurrency payments through BitPay from any wallet, app, or exchange,\" and lists the supported currencies …",
  "refund_policy": "Documented. Account balance \"can be used to pay for any HOSTKEY service or refunded via the original payment method\"; ea…",
  "restrictions": [
    "Ethereum mainnet only for stablecoins, by the merchant's own statement. BitPay supports Base, Polygon and Solana elsewhere; HOSTKEY says it does not take them.",
    "A BitPay ID (identity verification) \"may be required for cryptocurrency payments\".",
    "All services are prepaid. Payments credit an account balance, which can be spent on any HOSTKEY service.",
    "Licence costs, domain names, SSL certificates and server administration fees are not refundable; refunds for unused time follow the published refund policy."
  ],
  "location_count": null,
  "indexable": true,
  "verification_detail": {
    "methods": [
      "merchant-documentation",
      "payment-provider-documentation"
    ],
    "note": "HOSTKEY's own \"Payment terms and methods\" page names BitPay, lists the stablecoins, restricts ERC-20 tokens to Ethereum mainnet, notes the possible BitPay ID re…",
    "sources": [
      {
        "url": "https://www.hostkey.com/about-us/payment-terms-and-methods/",
        "title": "HOSTKEY — Payment terms and methods",
        "supports": "BitPay as the crypto route; the stablecoin list; \"ERC-20 tokens are only accepted on the Ethereum (ETH) network\"; possible BitPay ID; credit balance and refund rules.",
        "accessed": "2026-09-22"
      },
      {
        "url": "https://www.hostkey.com/about-us/",
        "title": "HOSTKEY — About us",
        "supports": "Dedicated, GPU and private-cloud services from TIER III data centres in the Netherlands, Germany, Finland, Iceland, the UK, the USA and Turkey.",
        "accessed": "2026-09-13"
      }
    ]
  },
  "changelog": [
    {
      "date": "2026-09-13",
      "event": "merchant_added",
      "field": null,
      "from": null,
      "to": null,
      "note": "Added after reading HOSTKEY's own payment-terms page, which names five stablecoins via BitPay and restricts ERC-20 tokens to Ethereum.",
      "source": null
    }
  ]
}

MCP server for AI assistants

The same dataset is available to ChatGPT, Claude, Codex and any other Model Context Protocol client as ten read-only tools — search and compare merchants, list stablecoins, networks, categories and payment providers, read the change feed and the Spend Index, and a Spending Finder that maps a request like “gift cards with USDC on Solana” to the documented records. Every result carries the verification status and dates. The server cannot send funds, sign transactions or return a payment address.

Endpoint (Streamable HTTP, no key required)

https://mcp.stablecoinspend.com/mcp

  • ChatGPT: Settings → Connectors → add a custom connector with the URL above, authentication None.
  • Claude: Settings → Connectors → add custom connector; or claude mcp add --transport http stablecoinspend https://mcp.stablecoinspend.com/mcp.
  • Any MCP client: transport streamable-http, no authentication. Health at /health.

Free for public use under the same attribution licence as the JSON endpoints; rate limited per client. Responses name StablecoinSpend as the source and link to each merchant’s profile.

Access tiers

Prices are read from the same source as every other page that quotes them. Each tier's limits and fields are listed on the card; the public endpoints above stay free with attribution whichever tier you choose, and no tier changes what a record says.

  • Research

    $9.99 per month

    For analysts and writers who need the numbers behind the charts.

    • Full merchant dataset as CSV and JSON, refreshed on every publish
    • Quarterly and monthly snapshot archive
    • Change history export
    • Citation licence for published research
    Register interest

    No self-serve checkout yet — we will reply by email.

  • Most popular

    Developer

    $19.99 per month

    Programmatic access for products that need to know who accepts what.

    • Everything in Research
    • REST API access with a personal key
    • 10,000 requests per month
    • Merchant, stablecoin, network and change endpoints
    • Webhook on acceptance changes
    Register interest

    No self-serve checkout yet — we will reply by email.

  • Professional

    $29.99 per month

    Higher limits and the fields that only matter at scale.

    • Everything in Developer
    • 100,000 requests per month
    • Full verification provenance: methods, sources, dates
    • Historical snapshot diffs
    • Priority support
    Register interest

    No self-serve checkout yet — we will reply by email.

Request a demo Contact sales

A demo is a call with the people who maintain the records, walking through the sample and the change feed against your use case. There is no sales team; you get an editor.

Questions about the data

How large is the dataset?
109 researched merchants, 102 of which have documented stablecoin acceptance (a further 4 confirm crypto acceptance without naming a stablecoin), backed by 235 cited primary sources. It is a focused dataset rather than a large one, and it is worth being direct about that: the value is that every record was checked against the merchant's own documentation, not that there are a lot of them.
How often does it update?
On every publish, which is typically several times a week as records are added and rechecked. Verification dates and the change feed tell you exactly how fresh any individual record is, so you never have to assume.
What is in the change feed that is not elsewhere?
Dated, sourced records of merchants gaining and losing stablecoin support — a gateway switch, a coin dropped for regulatory reasons, acceptance withdrawn entirely. Every entry that alters an acceptance claim carries a source URL because the content schema refuses to build without one. This is the part of the dataset nobody else has.
Is the API available now?
The public JSON endpoints listed above are live, need no key, and are free to use with attribution. The authenticated service — higher limits, filtering, full provenance, webhooks — is built and runs behind a key we issue by hand, because there is no self-serve billing yet. Email us and we will set you up; we will not pretend a checkout exists that does not.
Can I redistribute the data?
Free use with attribution covers research, journalism, internal analysis and citation. Redistribution as a dataset, or embedding it in a commercial product, needs a separate licence. Email us with what you are building; the answer is usually yes with terms.
Does the dataset contain personal information?
No. Every field we publish is already on a public merchant profile page. Form submissions, listing claims and correspondence are held outside the web root and are not reachable from the API — there is no code path from a submission record to a response.
Do paid customers get different data?
They get more of it and faster access to it — full provenance, historical snapshots, higher limits. They do not get different facts. A merchant record says the same thing to a paying customer as to a reader on the public site, and a merchant paying for a listing does not get a better verification status in the dataset than the evidence supports.

Talk to us about access

Tell us what you are building and which fields you need. If the public endpoints already cover it we will say so rather than sell you a tier — that answer costs us a subscription and buys a reference.

Email hello@stablecoinspend.com See the research first

Related