CryptoSpend API (v0 / v1)

Fee schedules and spend-route rankings from the same database powering Fee Tracker and Route Engine. Free public read — attribution appreciated.

Fee dump (v0)

Full card fee snapshot as JSON or CSV. Same rows as Fee Tracker — dated verifiedAt per program.

GET /api/public/fees
GET /api/public/fees?format=csv

Cards filter (v1)

Filter programs by country eligibility and asset support.

GET /api/v1/cards?country=ES&asset=USDT

Routes engine (v1)

POST or GET the Route Engine: country + asset + held_at + monthly spend → best / cheapest / simplest routes with annual cost.

GET /api/v1/routes?country=ES&asset=USDT&held_at=bybit&monthly_spend=2500

POST /api/v1/routes
Content-Type: application/json

{
  "country": "ES",
  "asset": "USDT",
  "held_at": "bybit",
  "monthly_spend": 2500,
  "foreign_spend_share": 0.2
}

Example response metadata

Every v1 response includes dataset_version, generated_at, fee_verified_at and model_status. Schema changes are additive only.

{
  "api": "cryptospend.routes",
  "version": "v1",
  "dataset_version": "2026.10.09",
  "generated_at": "2026-09-25T12:00:00.000Z",
  "fee_verified_at": "2026-10-09",
  "model_status": "mixed",
  "docs": "https://www.cryptospend.cards/en/developers",
  "best_route": { "id": "…", "annual_cost_usd": 382, "cost_confidence": "verified" },
  "roles": { "best": {…}, "cheapest": {…}, "simplest": {…} }
}

Notes

Not financial advice. Bank off-ramp costs are modeled ranges until verified like card fees. No API keys yet — rate limits may apply later. Changelog lives on Fee Tracker.