Paid
Paid (paid.ai) is the monetization platform for AI agents. It gives teams that build and sell AI agents the pricing, billing, and margin infrastructure to charge with flexible models — credits, usage-based, seat-based, and outcome-based pricing — while tracking the AI costs and delivered value behind every customer. Paid exposes a REST API (v1 and v2 on api.agentpaid.io), first-party SDKs for Node, Python, Go, and Java, a CLI, embeddable UI components, billing webhooks, an agent skill, and a hosted MCP server. Backed by EQT Ventures, Lightspeed Venture Partners, Seedcamp, and Techstars.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Paid the way a machine reads it — 49 machine-readable artifacts across 2 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 — Paid scores 59.3/100 (strong), with a separate agent-readiness read of 37/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 Paid'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/paid/"
title="Paid on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/paid.svg"
alt="Paid Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/paid/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/paid/"
title="Paid on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/paid/card.svg"
alt="Paid 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 Paid
Each block below is one kind of artifact we hold for Paid. 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 22
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.
Paid agents API
The agents API from Paid — 3 operation(s) for agents.
Paid analyticsExperimental API
The analyticsExperimental API from Paid — 3 operation(s) for analyticsexperimental.
Paid checkouts API
The checkouts API from Paid — 2 operation(s) for checkouts.
Paid contacts API
The contacts API from Paid — 5 operation(s) for contacts.
Paid costs API
The costs API from Paid — 1 operation(s) for costs.
Paid credits API
The credits API from Paid — 2 operation(s) for credits.
Paid customer-groups API
The customer-groups API from Paid — 3 operation(s) for customer-groups.
Paid customer-portals API
The customer-portals API from Paid — 1 operation(s) for customer-portals.
Paid customers API
The customers API from Paid — 22 operation(s) for customers.
Paid customViewsExperimental API
The customViewsExperimental API from Paid — 6 operation(s) for customviewsexperimental.
Paid invoices API
The invoices API from Paid — 3 operation(s) for invoices.
Paid orders API
The orders API from Paid — 14 operation(s) for orders.
Paid orders > lines API
The orders > lines API from Paid — 1 operation(s) for orders > lines.
Paid plans API
The plans API from Paid — 12 operation(s) for plans.
Paid pricing API
The pricing API from Paid — 2 operation(s) for pricing.
Paid products API
The products API from Paid — 5 operation(s) for products.
Paid signals API
The signals API from Paid — 1 operation(s) for signals.
Paid traces API
The traces API from Paid — 1 operation(s) for traces.
Paid usage API
The usage API from Paid — 3 operation(s) for usage.
Paid value-models API
The value-models API from Paid — 4 operation(s) for value-models.
Paid value-receipts API
The value-receipts API from Paid — 9 operation(s) for value-receipts.
Paid webhooks API
The webhooks API from Paid — 4 operation(s) for webhooks.
Scroll within the panel for all 22 ·
Open Collections 23
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 COLLECTIONAPI Reference agents API
OPEN COLLECTIONAPI Reference agents analyticsExperimental API
OPEN COLLECTIONAPI Reference agents checkouts API
OPEN COLLECTIONAPI Reference agents contacts API
OPEN COLLECTIONAPI Reference agents costs API
OPEN COLLECTIONAPI Reference agents credits API
OPEN COLLECTIONAPI Reference agents customer-groups API
OPEN COLLECTIONAPI Reference agents customer-portals API
OPEN COLLECTIONAPI Reference agents customers API
OPEN COLLECTIONAPI Reference agents customViewsExperimental API
OPEN COLLECTIONAPI Reference agents invoices API
OPEN COLLECTIONAPI Reference agents orders API
OPEN COLLECTIONAPI Reference agents orders > lines API
OPEN COLLECTIONAPI Reference agents plans API
OPEN COLLECTIONAPI Reference agents pricing API
OPEN COLLECTIONAPI Reference agents products API
OPEN COLLECTIONAPI Reference agents signals API
OPEN COLLECTIONAPI Reference agents traces API
OPEN COLLECTIONAPI Reference agents usage API
OPEN COLLECTIONAPI Reference agents value-models API
OPEN COLLECTIONAPI Reference agents value-receipts API
OPEN COLLECTIONAPI Reference agents webhooks API
OPEN COLLECTIONScroll within the panel for all 23 ·
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.
Paid 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.
Paid 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.
Resources
Every other property we hold for Paid — 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 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 3
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/paid · machine-readable index on apis.io
This is an independent, third-party profile of Paid, 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.