Rout Data · Developer preview
Better decisions begin withbetter card data.
One independent source for card identities, issuer artwork and structured rewards. Built by Rout, with evidence you can trace.
Local API available now. Commercial access is in development.
One product. A clear lineage.
From the issuer’s page to your product.
Issuer source
card.sourcecreditcards.chase.com
Reviewed facts
card.versionVersioned on publication
Your product
source.checksAudited on every attempt
Source-backed identities. Explicit unknowns. No guessed rewards.
- 4,001card identities
- 3,880original artwork mappings
- 75cards with reviewed earning rules
- 4,000identity coverage target
Catalog snapshot · November 6, 2026. 120 records have some reviewed facts; coverage is still growing. Inspect the complete breakdown ↗
01 / Quickstart
From a question to a card record.
Make a server-side request with a Rout Data key. The local backend exposes a dedicated read-only API, separate from customer banking data.
curl --fail-with-body \ -H "Authorization: Bearer $ROUT_DATA_KEY" \ 'http://localhost:3001/data/v1/cards?q=freedom'
{
"id": "chase-freedom-flex",
"issuer": "Chase",
"name": "Freedom Flex",
"verification": "identity-only",
"artwork": {
"sourcePage": "https://creditcards.chase.com/all-credit-cards",
"width": 289,
"height": 181
},
"facts": {
"annualFee": null,
"rules": []
}
}Unknown fees stay null. Empty rules mean no published rules, not that a card earns no rewards. Always check verification before recommending a card.
02 / API reference
A small surface. A useful foundation.
Base path /data/v1. Every endpoint below requires a bearer key. The downloadable OpenAPI contract includes parameters, response schemas and errors.
- GET/cards
Search products by name, issuer or reward category.
- GET/cards/{id}
Get the exact product, artwork and reviewed facts.
- GET/cards/{id}/verification
Inspect the daily status of each supporting source.
- GET/cards/{id}/checks
Read the source-check audit trail.
- GET/cards/{id}/history
See published versions and review dates.
- GET/changes
Keep your integration in sync with catalog events.
- GET/issuers
Discover registered issuer identities.
- GET/coverage
Measure field completeness and inventory gaps.
- GET/health
See source availability, freshness and overdue work.
03 / Daily verification
Know when it changed. Know when we checked.
Every monitored source is scheduled for another check within 24 hours. We retain the result, source hash and timestamps. A change opens a review; it does not silently rewrite financial advice.
Confirmed
Published evidence still matches, with successful audited checks within 24 hours.
Changed
A source differs. The last published version stays visible, marked for review.
Unavailable
A source could not be checked. We expose the gap and retry.
Identity-only records remain separate. Overdue checks are visible. Daily collection is a target, subject to source availability and an always-running worker.
04 / The data model
More than a rate.
A useful reward rule includes the category, booking channel, enrollment requirement, cap, dates and exclusions. Points stay points; miles stay miles. The API never invents a cash valuation.
- IIdentity & artworkExact product variants, original assets, issuer source URLs and image checksums.
- IIFees & reward rulesStructured fields with explicit unknowns and evidence for every published fact.
- IIIBenefits, offers & transfersSupported by the schema. Current completeness is reported field by field.
- IVSource & revision historySeparate collection, review and publication timestamps, plus incremental changes.
05 / Access & operations
Built to stand on its own.
Expiring, revocable API keys. Persisted per-key limits. Versioned responses. An operator workflow for evidence review and publication. These are the foundations of Rout’s independent card-data product.
Our growing asset is the normalized catalog and its accumulated source, matching and review history. Public issuer facts and trademarks remain their owners’.
Developer preview Now
The API runs in the current backend. Commercial hosting, billing, self-service provisioning and a production SLA are still ahead. The complete guide covers setup, rotation, pagination, change feeds, errors and deployment requirements.
Read the integration & operations guide