Ebates
Ebates is a consumer cash-back and rebate shopping platform founded in 2000 in San Francisco that pays members a percentage of their purchases back as cash when they shop through its links at thousands of partner retailers. Rakuten acquired Ebates in 2014 and rebranded the U.S. service as Rakuten Rewards in 2019; the ebates.com domain now redirects to rakuten.com. The business is a consumer-facing rewards and affiliate-commerce brand and does not operate an independent public developer API program. It was surfaced as a portfolio company of Canaan Partners and added to the API Evangelist network for enrichment.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Ebates the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Ebates scores 6.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ebates
Each block below is one kind of artifact we hold for Ebates. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Ebates — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ebates · machine-readable index on apis.io