How Card Perks API works

Card Perks API is the canonical, machine-readable database of credit-card benefits. There has never been one clean, current source of truth for what every card actually offers — issuer guides are scattered PDFs that change quietly. We continuously gather, structure, and verify that data, then expose it through a single REST API your application can query.

Two objects: cards and benefits. A card has identity + terms (issuer, network, annual fee, FX fee) and a list of benefits. Every benefit is one atomic row with exactly one type — bundles are split apart, so "airline benefits" becomes a separate fee credit, a free-bag perk, and a priority-boarding status.

Benefits are organized on two axes: where it lives (category → subcategory) and what it is (type). The type decides which fields appear inside the nested attributes object — that's where the real depth lives.

Every benefit also has a stable slug (e.g. chase-sapphire-reserve:300-annual-travel-credit) that never changes across re-ingestion, so you can rely on it as a key. Resolve any benefit with GET /v1/benefits/{id-or-slug}.

There are nine types. Fetch the live list (and the fields each carries) from GET /v1/types:

The power of the typed model is that you can filter all the way down into a benefit's attributes:

# Cards whose cell-phone protection has a low deductible & high cap
GET /v1/benefits?type=protection&max_deductible=50&min_coverage=800

# Monthly auto-triggered credits over $15
GET /v1/benefits?type=credit&reset_cadence=monthly&min_value=15

# Priority Pass lounge access
GET /v1/benefits?type=access&provider_network=Priority%20Pass

Get a whole card with its benefits grouped by category via GET /v1/cards/{id}, browse the structure with GET /v1/taxonomy, or try everything live in the interactive playground.

Two public surfaces let you (and your users) feel the data before writing a line of code:

Every benefit carries trust metadata so you can decide how much to rely on it:

• source — the document and section a fact came from, plus a verbatim citation quoting the source line.
• confidence — a 0–1 score blending extraction confidence, attribute completeness, verification, and freshness.
• verified — whether the row was confirmed against an authoritative document.
• last_verified_at — when we last checked it.

Create a free account in the developer portal to generate API keys. Send your key as an X-API-Key header on every /v1 request. Each plan has a request rate limit; usage is metered per key and visible in your dashboard. A public read-only demo key powers the docs playground so you can try the API before signing up.

See full limits on the pricing page. Billing is handled securely through Stripe.