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: Fetch Receipt Processor (Reference Specification). Tagged areas include Company, Rewards, Loyalty, Consumer, and Retail.

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

26.4/100 thin ▬ flat Agent 20/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
CompanyRewardsLoyaltyConsumerRetailAdvertisingReceiptsConsumer Packaged GoodsMobileMarketing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 26.4/100 · thin
Contract Quality 10.0 / 25
Developer Ergonomics 1.4 / 20
Access Clarity 4.2 / 20
Operational Transparency 1.7 / 13
Contract Governance 2.0 / 12
Discoverability 7.0 / 10
Agent readiness — 20/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 0 / 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 3 / 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 Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. 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. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Fetch Receipt Processor (Reference Specification)

A two-operation OpenAPI 3.0.3 document Fetch publishes in its public GitHub organization as the specification for its engineering take-home exercise: submit a receipt for proces...

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

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 6

The organization behind the API

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
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:receipt-processor
  name: Fetch Receipt Processor (Reference Specification)
  description: 'A two-operation OpenAPI 3.0.3 document Fetch publishes in its public GitHub organization as the specification
    for its engineering take-home exercise: submit a receipt for processing and retrieve the points awarded for that receipt.
    It is a reference contract, not a hosted production service - the document declares no servers, no security schemes and
    no operationIds, and Fetch exposes no public endpoint implementing it. It is captured here because it is the only machine-readable
    contract Fetch publishes, and it faithfully describes the shape of the receipt and line-item data at the core of the Fetch
    product.'
  humanURL: https://github.com/fetch-rewards/receipt-processor-challenge
  tags:
  - Receipts
  - Rewards
  - Points
  properties:
  - type: OpenAPI
    url: openapi/fetch-rewards-receipt-processor-openapi.yml
  - type: ErrorCatalog
    url: errors/fetch-rewards-problem-types.yml
  - type: DataModel
    url: data-model/fetch-rewards-data-model.yml
  - type: Overlay
    url: overlays/fetch-rewards-receipt-processor-overlay.yaml
  - type: Conventions
    url: conventions/fetch-rewards-conventions.yml
  - type: SourceCode
    url: https://github.com/fetch-rewards/receipt-processor-challenge
  x-status: reference-specification
  x-production: false
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- 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

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 email required.

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