Fetch Rewards website screenshot

Fetch Rewards

Fetch (legally Fetch Rewards, LLC) is a Madison, Wisconsin consumer rewards platform whose mobile app lets shoppers scan paper receipts, connect e-receipts and link accounts to earn points redeemable for gift cards and other rewards. On the demand side, Fetch For Business sells consumer packaged goods brands, retailers and restaurants receipt-verified offers, video and display advertising, point boosts, loyalty programs and omnichannel audience activation, all measured against real purchase data and managed through its Mission Control campaign platform. Fetch publishes no public developer or partner API and operates no developer portal; its only public machine-readable contract is the Receipt Processor reference OpenAPI it publishes on GitHub as an engineering hiring exercise. It does run a coordinated vulnerability disclosure program via HackerOne and publishes an RFC 9116 security.txt, and its GitHub organization ships several first-party open-source Swift and Python developer libraries.

Fetch Rewards publishes 1 API on the APIs.io network: Receipts API. Tagged areas include Company, Rewards, Loyalty, Consumer, and Retail.

Fetch Rewards’ developer surface includes engineering blog, support, FAQ, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub
24.6/100 emerging ▬ flat Agent 21/100 agent aware Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
1 APIs
CompanyRewardsLoyaltyConsumerRetailAdvertisingReceiptsConsumer Packaged GoodsMobileMarketing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Composite quality — 24.6/100 · emerging
Contract Quality 9.7 / 23
Developer Ergonomics 1.3 / 18
Access Clarity 3.8 / 18
Operational Transparency 1.5 / 12
Contract Governance 0.5 / 11
Discoverability 6.0 / 9
Create-or-Update Ergonomics 0.0 / 10
Agent readiness — 21/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/fetch-rewards: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Fetch Rewards Receipts API

The Receipts API from Fetch Rewards — 2 operation(s) for receipts.

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Receipt Processor

OPEN COLLECTION

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Fetch Rewards Domain Security

TLSv1.3 · DMARC

SECURITY

Fetch Rewards Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 LLMsTxt
LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

Extensions
Extensions
 GitHubOrganization
GitHubOrganization
 Packages
Packages

Access & Security 4

Authentication, authorization, and security posture

Security
Security
 VulnerabilityDisclosure
VulnerabilityDisclosure
 SecurityTxt
SecurityTxt
 DomainSecurity
DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support
Support
 FAQ
FAQ
 ContactUs
ContactUs

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy
PrivacyPolicy
 TermsOfService
TermsOfService

Company 6

The organization behind the API

Website
Website
 Blog
Blog
 Newsroom
Newsroom
 Careers
Careers
 LinkedIn
LinkedIn
 Twitter
Twitter

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: fetch-rewards
name: Fetch Rewards
description: Fetch (legally Fetch Rewards, LLC) is a Madison, Wisconsin consumer rewards platform whose mobile app lets shoppers
  scan paper receipts, connect e-receipts and link accounts to earn points redeemable for gift cards and other rewards. On
  the demand side, Fetch For Business sells consumer packaged goods brands, retailers and restaurants receipt-verified offers,
  video and display advertising, point boosts, loyalty programs and omnichannel audience activation, all measured against
  real purchase data and managed through its Mission Control campaign platform. Fetch publishes no public developer or partner
  API and operates no developer portal; its only public machine-readable contract is the Receipt Processor reference OpenAPI
  it publishes on GitHub as an engineering hiring exercise. It does run a coordinated vulnerability disclosure program via
  HackerOne and publishes an RFC 9116 security.txt, and its GitHub organization ships several first-party open-source Swift
  and Python developer libraries.
url: https://raw.githubusercontent.com/api-evangelist/fetch-rewards/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pass
deliveryModel:
  model: unknown
  open_source: unknown
  commercial: true
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  - pricing
  - repository-unlicensed
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  generated: '2026-09-02'
  method: derived
image: https://fetch.com/favicon.png
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- Company
- Rewards
- Loyalty
- Consumer
- Retail
- Advertising
- Receipts
- Consumer Packaged Goods
- Mobile
- Marketing
apis:
- aid: fetch-rewards:fetch-rewards-receipts-api
  name: Fetch Rewards Receipts API
  description: The Receipts API from Fetch Rewards — 2 operation(s) for receipts.
  humanURL: https://github.com/fetch-rewards/receipt-processor-challenge
  tags:
  - Receipts
  properties:
  - type: OpenAPI
    url: openapi/fetch-rewards-receipts-api-openapi.yml
  - type: ErrorCatalog
    url: errors/fetch-rewards-problem-types.yml
  - type: DataModel
    url: data-model/fetch-rewards-data-model.yml
  - type: Conventions
    url: conventions/fetch-rewards-conventions.yml
  - type: SourceCode
    url: https://github.com/fetch-rewards/receipt-processor-challenge
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/fetch-rewards-receipt-processor-overlay.yaml
- type: Website
  url: https://fetch.com/
- type: Solutions
  url: https://business.fetch.com/solutions
- type: Blog
  url: https://fetch.com/blog
- type: Support
  url: https://help.fetch.com/hc/en-us
- type: FAQ
  url: https://fetch.com/faq
- type: ContactUs
  url: https://business.fetch.com/contact-us
- type: Newsroom
  url: https://business.fetch.com/newsroom
- type: Careers
  url: https://fetch.com/careers/jobs
- type: Extensions
  url: https://chromewebstore.google.com/detail/fetch/hgpkkikfhmllgfnclpfiklpcpehelhda
- type: GitHubOrganization
  url: https://github.com/fetch-rewards
- type: PrivacyPolicy
  url: https://fetch.com/privacy-policy
- type: TermsOfService
  url: https://fetch.com/terms-of-service
- type: LinkedIn
  url: https://www.linkedin.com/company/fetch-rewards-llc/
- type: Twitter
  url: https://x.com/FetchRewards
- type: Security
  url: https://hackerone.com/fetchrewards_vdp
- type: VulnerabilityDisclosure
  url: security/fetch-rewards-vulnerability-disclosure.yml
- type: SecurityTxt
  url: well-known/fetch-rewards-security.txt
- type: WellKnown
  url: well-known/fetch-rewards-well-known.yml
- type: DomainSecurity
  url: security/fetch-rewards-domain-security.yml
- type: Packages
  url: packages/fetch-rewards-packages.yml
- type: Conformance
  url: conformance/fetch-rewards-conformance.yml
- type: LLMsTxt
  url: llms/fetch-rewards-llms.txt
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 12
  pass: local-v1
x-parent: fetch
x-relationship: product

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/fetch-rewards"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/fetch-rewards/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/fetch-rewards/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.