Spreedly
Spreedly is a United States payments orchestration platform and PCI-compliant card vault that lets merchants and platforms securely tokenize payment methods once and then transact against hundreds of payment gateways, processors, and third-party APIs through a single integration. Founded in 2008 and headquartered in Durham, North Carolina, Spreedly sits in the gateway/PSP layer of the deep, fragmented US payments market as an independent, network-agnostic intermediary rather than a card network or acquirer. Its Payments Orchestration offering combines a universal token vault, a normalized transaction API across many gateways, workflow-based routing (Composer), network tokenization, account updater (Card Refresher), 3-D Secure / SCA authentication, and Receivers for forwarding stored payment data to arbitrary third-party endpoints. Spreedly is strongly API-native: it publishes a public developer portal with complete reference documentation and a downloadable OpenAPI 3.1 specification for its Core Transactional API (https://core.spreedly.com/v1), authenticated with HTTP Basic auth using per-environment key/secret credentials.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Spreedly the way a machine reads it — 34 machine-readable artifacts across 1 API, 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 — Spreedly scores 56.1/100 (strong), with a separate agent-readiness read of 44/100 (agent native). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Spreedly's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/spreedly/"
title="Spreedly on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/spreedly.svg"
alt="Spreedly Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/spreedly/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/spreedly/"
title="Spreedly on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/spreedly/card.svg"
alt="Spreedly Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Spreedly
Each block below is one kind of artifact we hold for Spreedly. 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 26
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.
Spreedly Access Secrets API
The access_secrets API from Spreedly — 2 operation(s) for access_secrets.
Spreedly Authorize API
The authorize API from Spreedly — 1 operation(s) for authorize.
Spreedly Capture API
The capture API from Spreedly — 1 operation(s) for capture.
Spreedly Card Refresher API
The card_refresher API from Spreedly — 3 operation(s) for card_refresher.
Spreedly Certificates API
The certificates API from Spreedly — 3 operation(s) for certificates.
Spreedly Claim API
The claim API from Spreedly — 1 operation(s) for claim.
Spreedly Composer API
The composer API from Spreedly — 3 operation(s) for composer.
Spreedly Credit API
The credit API from Spreedly — 1 operation(s) for credit.
Spreedly Environments API
The environments API from Spreedly — 3 operation(s) for environments.
Spreedly Events API
The events API from Spreedly — 2 operation(s) for events.
Spreedly Gateways API
The gateways API from Spreedly — 6 operation(s) for gateways.
Spreedly General Credit API
The general_credit API from Spreedly — 1 operation(s) for general_credit.
Spreedly Merchant Profiles API
The merchant_profiles API from Spreedly — 2 operation(s) for merchant_profiles.
Spreedly Network Tokenization API
The network_tokenization API from Spreedly — 2 operation(s) for network_tokenization.
Spreedly Payment Methods API
The payment_methods API from Spreedly — 12 operation(s) for payment_methods.
Spreedly Payments API
The payments API from Spreedly — 1 operation(s) for payments.
Spreedly Protection Events API
The protection_events API from Spreedly — 2 operation(s) for protection_events.
Spreedly Protection Provider API
The protection_provider API from Spreedly — 2 operation(s) for protection_provider.
Spreedly Purchase API
The purchase API from Spreedly — 2 operation(s) for purchase.
Spreedly Receivers API
The receivers API from Spreedly — 6 operation(s) for receivers.
Spreedly Sca Authentication API
The sca_authentication API from Spreedly — 1 operation(s) for sca_authentication.
Spreedly Sca Provider API
The sca_provider API from Spreedly — 2 operation(s) for sca_provider.
Spreedly Sub Merchants API
The sub_merchants API from Spreedly — 2 operation(s) for sub_merchants.
Spreedly Transactions API
The transactions API from Spreedly — 5 operation(s) for transactions.
Spreedly Verify API
The verify API from Spreedly — 1 operation(s) for verify.
Spreedly Void API
The void API from Spreedly — 1 operation(s) for void.
Scroll within the panel for all 26 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Spreedly API V1
POSTMANOpen 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).
Spreedly API V1
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Spreedly MCP Server
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Spreedly Webhooks
ASYNCAPISecurity 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 Spreedly — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 7
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 7 ·
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/spreedly · machine-readable index on apis.io
This is an independent, third-party profile of Spreedly, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.