Rainforest
Rainforest is a payfac-as-a-service (payment-facilitator-as-a-service) provider that lets vertical SaaS platforms embed payments and monetize them as revenue. Platforms integrate via embeddable, PCI-scope-reducing Components (loaded from a JavaScript bundle and configured in Component Studio) or a direct server-to-server REST API, and Rainforest handles merchant onboarding (KYC/KYB), card and ACH processing, payouts/deposits, chargebacks, disputes, and PCI compliance. The API is organized into Authentication/API keys, Merchants and merchant applications, Payments (payins, payment methods, refunds, chargebacks, ACH returns, devices), Deposits, File Uploads, Forward Requests, and Health, versioned by date (current 2024-10-16) and secured with HTTP Bearer API keys plus short-lived Component session tokens. Rainforest is PCI DSS Level 1 certified and hosted on AWS. Backed by Accel, Matrix Partners, and Y Combinator.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Rainforest the way a machine reads it — 32 machine-readable artifacts across 23 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 — Rainforest scores 61.9/100 (strong), with a separate agent-readiness read of 80/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Rainforest
Each block below is one kind of artifact we hold for Rainforest. 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 23
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.
Rainforest ACH Returns API
Resources for ACH return functions.
Rainforest API Keys API
Resources for api key functions.
Rainforest Billing Profiles API
Resources for billing profile functions.
Rainforest BIN Lookups API
Resources for BIN lookup functions.
Rainforest Chargebacks API
Resources for chargeback functions.
Rainforest Deposit Method Configs API
Resources for deposit method config functions.
Rainforest Deposit Methods API
Resources for deposit method functions.
Rainforest Deposits API
Resources for deposit functions.
Rainforest Devices API
Resources for device functions.
Rainforest File Upload Configs API
Resources for file upload config functions.
Rainforest File Uploads API
Resources for file upload functions.
Rainforest Forward Requests API
Resources for forwarding sensitive data to 3rd parties.
Rainforest Health API
Resources for health functions.
Rainforest Merchant Applications API
Resources for merchant application functions.
Rainforest Merchants API
Resources for merchant functions.
Rainforest Payin Configs API
Resources for payin configs functions.
Rainforest Payins API
Resources for payin functions.
Rainforest Payment Method Configs API
Resources for payment method configs functions.
Rainforest Payment Method Domains API
Resources for payment method domain functions.
Rainforest Payment Methods API
Resources for payment method functions.
Rainforest Payments API
Resources for payment functions.
Rainforest Refunds API
Resources for refund functions.
Rainforest Sessions API
Resources for session functions.
Scroll within the panel for all 23 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZORainforest — configure and process a payin
Create a payin config with an idempotency key, process the payin, and confirm its status.
ARAZZORainforest — onboard a merchant
Create a merchant, submit its application, and confirm it reaches ACTIVE.
ARAZZOMCP 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.
rainforest-mcp.yml
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.
Rainforest 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 Rainforest — 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 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 4
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 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/rainforest · machine-readable index on apis.io