Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Earn.com website screenshot

Earn.com

Earn.com was a cryptocurrency startup founded in 2013 as 21e6 and later known as 21 Inc and 21.co, backed by a16z and others, which raised over $116 million. It began as a Bitcoin mining venture selling the 21 Bitcoin Computer, then pivoted to a paid-messaging marketplace where senders paid recipients in cryptocurrency to read and reply to email. Coinbase acquired Earn.com in April 2018 for a reported $120 million, and co-founder Balaji Srinivasan became Coinbase's first Chief Technology Officer. The standalone Earn.com product was retired and the brand was folded into Coinbase Earn, the learn-and-earn program. As of July 2026 the earn.com domain issues a blanket HTTP 301 redirect for every path to https://www.coinbase.com/earn, and no developer, documentation, or API subdomain resolves. Earn.com therefore has no independent API surface; any remaining API capability lives under Coinbase.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Earn.com the way a machine reads it — 2 machine-readable artifacts, 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 — Earn.com scores 16.0/100 (emerging), with a separate agent-readiness read of 17/100 (agent aware). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 16.0/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 4.8 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Payments 3.9 / 15
Agent readiness — 17/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 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

How we profile Earn.com

Each block below is one kind of artifact we hold for Earn.com. 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 2

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.

Earncom Authentication

http/custom-signature · 2 schemes

SECURITY

Earncom Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Earn.com — 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.

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/earncom · machine-readable index on apis.io