Cryptorefills

• Name: Cryptorefills
• URL: https://www.cryptorefills.com/
• Category: crypto spend catalog / checkout API / agent-facing purchase flow
• Tags: bitcoin-ecosystem ethereum-ecosystem
• Summary: Cryptorefills at the project layer is the checkout and purchase-orchestration surface inside a broader Cryptorefills company shell. The reusable product cut is catalog search, quote, validation, order, payment, and delivery tracking across conventional partner APIs and newer MCP / x402 agent lanes. The broader operator boundary now lives in cryptorefills, which is the cleaner place to reason about supplier admission, catalog stewardship, support, disclosure requirements, and fulfillment truth.
• What it does:
  • Lets users buy gift cards, mobile top-ups, eSIMs, flights, and stays with Bitcoin, Lightning, stablecoins, and other crypto assets across many countries
  • Exposes a partner REST API for catalog browsing, product pricing, order validation, order creation, and order-status tracking via SSE or polling
  • Publishes MCP discovery artifacts, agent skills, and an HTTP MCP endpoint so AI agents can browse products and complete purchases through a structured tool layer
  • Supports autonomous x402-based purchasing for AI agents using USDC on Base without the traditional API-key or OAuth setup described on the site
  • Maintains supplier/brand partnership paths that include direct API integration for proven cases or stocked-code supply relationships
  • Positions itself as a real-world spending rail for wallet apps, rewards programs, mini apps, treasury-spend helpers, and other Web3 or agentic commerce flows
• Key claims:
  • The homepage says users can choose from 6,600+ gift cards, eSIMs, flights, stays, and mobile top-ups, pay with BTC, ETH, USDT, USDC, and many more, and receive products instantly; it also explicitly says the platform is built for AI agents via skills, MCP, and x402
  • The API landing page describes Cryptorefills as “the stablecoin checkout API for gift cards, mobile top-ups and eSIMs,” says builders can move from search to quote to payment to delivery in one deterministic flow, and says inventory can be issued at checkout time instead of pre-buying stock
  • The developer API reference documents a partner-authenticated REST surface with headers such as X-Cr-Application, X-Cr-Version, and X-Country-ISO-Code, plus endpoints for payment methods, country brand catalogs, product browsing, price conversion, validation, order creation, and order tracking
  • The developer docs recommend validating before order creation, note a 30-minute payment window, and expose both SSE subscription flow and polling fallback for order-state tracking, which is a strong signal of an operational commerce platform rather than a thin checkout wrapper
  • The AI-agents page says Cryptorefills is the first platform where AI agents can autonomously search, quote, and purchase gift cards and mobile top-ups using stablecoins, and it documents three published skills: cryptorefills-catalog, cryptorefills-buy, and cryptorefills-x402
  • The AI-agents page and llms.txt publish machine-readable discovery surfaces including an MCP manifest, API catalog, agent-skills index, HTTP/SSE MCP transports, and public agent-skill documents, which is unusually explicit agent-integration posture for a crypto spending platform
  • The public llms.txt says MCP and x402 flows work without account, OAuth, or API-key provisioning, while the partner developer API uses partner headers; together these surfaces suggest Cryptorefills is operating two access models at once: a conventional partner API and a lower-friction agent-native purchase layer
  • The supplier partnership page says Cryptorefills reaches users directly and through partners such as Binance, accepts Lightning and major cryptocurrencies, and can onboard supply either through direct brand API integration or through stocked-code relationships
  • The official materials are inconsistent on catalog scale: the homepage and API marketing pages say 6,600+ brands/products, while llms.txt, the AI-agents page, and the public GitHub agents repo say 10,500+ brands. That discrepancy is worth noting, but it does not change the broader conclusion that the company is packaging programmable crypto-spending infrastructure
• Whitepaper: No canonical standalone Cryptorefills whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, partner API docs, AI-agent pages, machine-readable discovery files, supplier-partnership page, and first-party GitHub agent-skills repo; see ../whitepapers/cryptorefills-primary-sources-2026-05-02.md.
• Sources:
  • https://www.cryptorefills.com/
  • https://www.cryptorefills.com/en/api-docs
  • https://www.cryptorefills.com/en/api-docs/developers
  • https://www.cryptorefills.com/en/ai-agents
  • https://www.cryptorefills.com/en/consumer-and-digital-brands
  • https://www.cryptorefills.com/llms.txt
  • https://api.cryptorefills.com/.well-known/mcp.json
  • https://api.cryptorefills.com/.well-known/agent-skills/index.json
  • https://github.com/Cryptorefills/agents

Internal linkages

• Company / operator boundary for supplier admission, catalog stewardship, fulfillment, and support: cryptorefills.
• Strongest product and interface contrasts: bitrefill and x402.

Protocol / company boundary

• Keep this note on the product mechanics integrators and agents touch directly: catalog search, quote and validation flow, payment-address creation, order-state tracking, and the newer MCP / x402 access paths.
• Use cryptorefills when the sharper question is who admits suppliers and partners, owns the catalog and delivery relationship, requires service disclosure, supports end users, and decides which purchase lanes stay open.
• That split matters because how does the purchase flow behave? and which company controls the catalog and fulfillment shell around it? are related but not identical questions.

Control surface

• At the product layer, practical authority sits in search, quote, validation, order-creation, payment-window, and order-tracking behavior across both classic API and agent-facing access paths.

• The broader operator dependency sits one layer up in cryptorefills: supplier admission, catalog stewardship, fulfillment handling, customer support, and the disclosure and service shell users are told to trust.

• Read it as a checkout and fulfillment workflow surface, not as a payment rail.

• Last reviewed: 2026-08-12 UTC