Drippay
Drippay, Inc. ("drip") is a Y Combinator company (YC P26) building two connected products. drip is a local-first Mac app that turns LinkedIn, iMessage, and email conversations into a self-filling CRM with AI drafting, follow-up, and meeting booking. The Drip API is a usage-based billing and execution-ledger platform for AI agents — a Stripe-like metering and monetization backend exposing customers, subscriptions, pricing plans, billable metrics, usage events, invoices, credit notes, coupons, entitlements, charges, dunning, tax, contracts, drift detection, and webhooks over a REST interface at api.drippay.dev. It ships official Node, Python, and C++ SDKs, an idempotency-key contract, cursor pagination, a hosted MCP server, and a SOC 2 Type I security posture monitored with Vanta.
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 Drippay the way a machine reads it — 30 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 — Drippay scores 57.5/100 (developing), with a separate agent-readiness read of 67/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 Drippay
Each block below is one kind of artifact we hold for Drippay. 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.
Drippay BillableMetrics API
Evaluate and preview billable metrics.
Drippay Business API
Business-level settings and configuration.
Drippay Charges API
View charge history and settlement status.
Drippay Contracts API
Per-customer commercial agreements with custom pricing, prepaid commits, and spend caps. All contract endpoints require a secret key (`sk_*`) with the `ADMIN` role.
Drippay Coupons API
Coupons and promotion codes for discounts.
Drippay Credit Notes API
Create, issue, and void credit notes.
Drippay Customer Portal API
Self-service customer portal for profile, subscriptions, and address management.
Drippay Customers API
Create and manage billable customers.
Drippay Drift API
The Drift API from Drippay — 6 operation(s) for drift.
Drippay Dunning API
Automatic retry + dunning email flow for failed payments. Configure a per-business retry schedule, list failed charges in collections, and manually re-trigger retries.
Drippay Entitlements API
Quota management and pre-request access checks.
Drippay Events API
Record execution events for observability.
Drippay Integrations API
Manage billing, CRM, and marketplace integrations (Stripe, Xero, Salesforce).
Drippay Internal API
The Internal API from Drippay — 1 operation(s) for internal.
Drippay Invoices API
Generate, issue, and manage invoices. Supports usage-based and subscription-based billing periods.
Drippay Pricing Plans API
Define per-unit pricing for usage types. Creating, updating, and deleting plans requires a secret key (`sk_*`) with the `ADMIN` role.
Drippay Product Categories API
Controlled taxonomy for strict-products governance. Groups pricing plans into service-line categories for ARR rollups and revenue reporting.
Drippay Runs API
Start, update, and inspect agent runs.
Drippay Subscriptions API
Recurring billing and subscription lifecycle management.
Drippay Tax API
Sales tax configuration: customer tax addresses, exemptions, business registrations, and jurisdiction rates. Requires a secret key with ADMIN role and full mode (`SIMPLE_MODE=fa...
Drippay Usage API
Record metered usage. Creates charges when a pricing plan matches.
Drippay Webhooks API
Manage webhook endpoints for real-time event notifications.
Drippay Workflows API
Define workflow templates for agent execution.
Scroll 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.
drippay-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.
Drippay Webhooks
ASYNCAPISecurity Posture 4
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 Drippay — 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 5
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 1
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/drippay · machine-readable index on apis.io