Reverb
Reverb is a marketplace for musicians to buy and sell new, used, and vintage musical instruments and gear, owned by Etsy. The Reverb API is a HATEOAS hypermedia REST API using application/hal+json, with interactive Swagger documentation and an X-Auth-Token header authentication scheme.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Reverb the way a machine reads it — 29 machine-readable artifacts across 21 APIs, 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 — Reverb scores 33.0/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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 Reverb
Each block below is one kind of artifact we hold for Reverb. 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.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Reverb REST API
HATEOAS hypermedia REST API at https://reverb.com/api using application/hal+json. Auth via POST /api/auth/tokens to obtain a token used in X-Auth-Token header. Endpoints exposed...
Reverb Accounts API
The Accounts API from Reverb — 1 operation(s) for accounts.
Reverb Articles API
The Articles API from Reverb — 2 operation(s) for articles.
Reverb Auth API
The Auth API from Reverb — 4 operation(s) for auth.
Reverb Autocomplete API
The Autocomplete API from Reverb — 1 operation(s) for autocomplete.
Reverb Autosuggest API
The Autosuggest API from Reverb — 1 operation(s) for autosuggest.
Reverb Braintree API
The Braintree API from Reverb — 1 operation(s) for braintree.
Reverb Cart API
The Cart API from Reverb — 1 operation(s) for cart.
Reverb Categories API
The Categories API from Reverb — 2 operation(s) for categories.
Reverb Collections API
The Collections API from Reverb — 1 operation(s) for collections.
Reverb Countries API
The Countries API from Reverb — 1 operation(s) for countries.
Reverb Currencies API
The Currencies API from Reverb — 2 operation(s) for currencies.
Reverb Listings API
The Listings API from Reverb — 1 operation(s) for listings.
Reverb My API
The My API from Reverb — 21 operation(s) for my.
Reverb Payment Methods API
The Payment Methods API from Reverb — 1 operation(s) for payment methods.
Reverb Priceguide API
The Priceguide API from Reverb — 1 operation(s) for priceguide.
Reverb Push Notifications API
The Push Notifications API from Reverb — 1 operation(s) for push notifications.
Reverb Reverb API API
The Reverb API API from Reverb — 1 operation(s) for reverb api.
Reverb Shipping API
The Shipping API from Reverb — 2 operation(s) for shipping.
Reverb Shop API
The Shop API from Reverb — 3 operation(s) for shop.
Reverb Wants API
The Wants API from Reverb — 1 operation(s) for wants.
Scroll within the panel for all 21 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Reverb API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Reverb Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Reverb Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Reverb Finops
FINOPSSecurity Posture 3
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Reverb — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
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/reverb · machine-readable index on apis.io