Slash
Slash is a business banking and finance platform for modern companies — startups, agencies, e-commerce sellers, and enterprises — combining business checking, unlimited virtual and physical corporate cards, ACH/wire and real-time payments, global USD accounts, stablecoin on/off ramps, treasury, invoicing, expense management, and reporting on one platform. Founded in 2021 and valued at $1.4B after a 2026 Series C led by Ribbit Capital, Slash exposes a REST API (currently in Beta) covering accounts, virtual accounts, cards and card groups, transactions, transfers, invoices, contacts and customers, expense reports, webhooks, and FDX-compliant financial data access — plus an official hosted MCP server, Agent Requests with human-in-the-loop approval, and Python and Node.js SDKs for AI-agent and programmatic integration.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Slash the way a machine reads it — 33 machine-readable artifacts across 26 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 — Slash scores 61.7/100 (strong), with a separate agent-readiness read of 87/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 Slash
Each block below is one kind of artifact we hold for Slash. 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.
Slash Account API
The Account API from Slash — 4 operation(s) for account.
Slash Agent Requests API
The Agent Requests API from Slash — 2 operation(s) for agent requests.
Slash Analytics API
The Analytics API from Slash — 1 operation(s) for analytics.
Slash Card API
The Card API from Slash — 5 operation(s) for card.
Slash Card Group API
The Card Group API from Slash — 4 operation(s) for card group.
Slash Card Product API
The Card Product API from Slash — 1 operation(s) for card product.
Slash Contact API
The Contact API from Slash — 3 operation(s) for contact.
Slash Crypto API
The Crypto API from Slash — 1 operation(s) for crypto.
Slash Customer API
The Customer API from Slash — 3 operation(s) for customer.
Slash Developer Account API
The Developer Account API from Slash — 1 operation(s) for developer account.
Slash Developer Application API
The Developer Application API from Slash — 2 operation(s) for developer application.
Slash Expense Report API
The Expense Report API from Slash — 7 operation(s) for expense report.
Slash Fdx API
The Fdx API from Slash — 8 operation(s) for fdx.
Slash Invoice API
The Invoice API from Slash — 13 operation(s) for invoice.
Slash Legal Entity API
The Legal Entity API from Slash — 1 operation(s) for legal entity.
Slash Merchant API
The Merchant API from Slash — 2 operation(s) for merchant.
Slash Merchant Category API
The Merchant Category API from Slash — 1 operation(s) for merchant category.
Slash Oauth2 API
The Oauth2 API from Slash — 2 operation(s) for oauth2.
Slash Task API
The Task API from Slash — 4 operation(s) for task.
Slash Tokens API
The Tokens API from Slash — 1 operation(s) for tokens.
Slash Transaction API
The Transaction API from Slash — 5 operation(s) for transaction.
Slash Transfer API
The Transfer API from Slash — 1 operation(s) for transfer.
Slash Transfers API
The Transfers API from Slash — 1 operation(s) for transfers.
Slash Virtual Account API
The Virtual Account API from Slash — 2 operation(s) for virtual account.
Slash Webhook API
The Webhook API from Slash — 2 operation(s) for webhook.
Slash .well Known API
The .well Known API from Slash — 1 operation(s) for .well known.
Scroll within the panel for all 26 ·
MCP 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.
slash-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.
Slash 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Slash — 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 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
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
← All providers · Data indexed from github.com/api-evangelist/slash · machine-readable index on apis.io