Slope
Slope is a fintech company providing credit infrastructure for business lending - an embedded buy-now-pay-later (BNPL) and working-capital solution that lets merchants offer flexible net-terms financing to their business (B2B) buyers at checkout with no added risk. Its platform combines an embedded line-of-credit product, the SlopeScore business cash-flow score for underwriting, and a developer API (v4) for creating customers and orders, driving checkout via the Slope.js widget or a hosted redirect, finalizing orders for payout, issuing refunds/adjustments, handling repayments, and subscribing to webhook events. Slope is backed by GGV Capital and has announced a relationship with Amazon.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Slope the way a machine reads it — 31 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 — Slope scores 47.7/100 (developing), with a separate agent-readiness read of 35/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. 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 Slope'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/slope/"
title="Slope on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/slope.svg"
alt="Slope Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/slope/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/slope/"
title="Slope on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/slope/card.svg"
alt="Slope 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 Slope
Each block below is one kind of artifact we hold for Slope. 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 10
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.
Slope Auth API
The Auth API from Slope — 2 operation(s) for auth.
Slope Customers API
The Customers API from Slope — 6 operation(s) for customers.
Slope Files API
The Files API from Slope — 1 operation(s) for files.
Slope Orders API
The Orders API from Slope — 11 operation(s) for orders.
Slope Payout Accounts API
The Payout Accounts API from Slope — 2 operation(s) for payout accounts.
Slope Persons API
The Persons API from Slope — 1 operation(s) for persons.
Slope Prescreens API
The Prescreens API from Slope — 2 operation(s) for prescreens.
Slope Simulation API
The Simulation API from Slope — 7 operation(s) for simulation.
Slope Transactions API
The Transactions API from Slope — 1 operation(s) for transactions.
Slope User Links API
The User Links API from Slope — 2 operation(s) for user links.
Scroll within the panel for all 10 ·
Open Collections 11
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).
API Collection
OPEN COLLECTIONSlope v4 Auth API
OPEN COLLECTIONSlope v4 Auth Customers API
OPEN COLLECTIONSlope v4 Auth Files API
OPEN COLLECTIONSlope v4 Auth Orders API
OPEN COLLECTIONSlope v4 Auth Payout Accounts API
OPEN COLLECTIONSlope v4 Auth Persons API
OPEN COLLECTIONSlope v4 Auth Prescreens API
OPEN COLLECTIONSlope v4 Auth Simulation API
OPEN COLLECTIONSlope v4 Auth Transactions API
OPEN COLLECTIONSlope v4 Auth User Links API
OPEN COLLECTIONScroll within the panel for all 11 ·
Arazzo Workflows 4
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.
Create a Slope order and finalize it
Create an order, wait for the customer to open it, then finalize for payout.
ARAZZOEstimate and repay a Slope order
Get a repayment estimate then fully repay an order (requires Slope-Link-Token).
ARAZZOSimulate an approved order in the sandbox
Create a sandbox test customer, set eligibility, create an order, and approve it.
ARAZZORate 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.
Slope Rate Limits
RATE LIMITSEvent Specifications 2
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.
Slope Webhook Events
Generated event surface for Slope webhooks. Payload schemas documented at https://developers.slopepay.com/docs/schema. Signed via the Slope-Signature header (HMAC-SHA256).
ASYNCAPISlope Webhooks
ASYNCAPISecurity 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.
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 Slope — 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 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 12
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 12 ·
Access & Security 2
Authentication, authorization, and security posture
Operate 5
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 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/slope · machine-readable index on apis.io
This is an independent, third-party profile of Slope, 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.