Tabs
Tabs is an AI-native revenue automation platform for B2B companies that streamlines the entire contract-to-cash lifecycle — contract ingestion, billing generation, invoicing, collections, cash application, ASC 606 revenue recognition, and reporting. Its Universal (External) API v3 exposes the underlying revenue data model of customers, contracts, obligations, billing terms, performance obligations, invoices, payments, credit memos, products, commitments, and renewals, while a dedicated Usage API (Beta) ingests high-throughput usage events with strong idempotency. Tabs also operates an official read-only MCP server over its "Commercial Graph" so AI agents can query live billing, revenue, and contract data. Backed by Lightspeed Venture Partners and General Catalyst ($91M+ raised through its 2025 Series B), Tabs integrates with QuickBooks, NetSuite, Sage Intacct, Salesforce, HubSpot, Stripe, Plaid, Anrok, and Avalara.
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 Tabs the way a machine reads it — 28 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 — Tabs scores 54.0/100 (developing), with a separate agent-readiness read of 70/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 Tabs
Each block below is one kind of artifact we hold for Tabs. 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.
Tabs Billing Terms API
The Billing Terms API from Tabs — 1 operation(s) for billing terms.
Tabs Categories API
The Categories API from Tabs — 2 operation(s) for categories.
Tabs Classes (QBO only) API
The Classes (QBO only) API from Tabs — 1 operation(s) for classes (qbo only).
Tabs Commitments API
The Commitments API from Tabs — 2 operation(s) for commitments.
Tabs Contracts API
The Contracts API from Tabs — 17 operation(s) for contracts.
Tabs Credit Memos API
The Credit Memos API from Tabs — 3 operation(s) for credit memos.
Tabs Custom Fields API
The Custom Fields API from Tabs — 1 operation(s) for custom fields.
Tabs Customers API
The Customers API from Tabs — 21 operation(s) for customers.
Tabs Departments API
The Departments API from Tabs — 1 operation(s) for departments.
Tabs Events API
The Events API from Tabs — 8 operation(s) for events.
Tabs Health API
The Health API from Tabs — 3 operation(s) for health.
Tabs Invoices API
The Invoices API from Tabs — 1 operation(s) for invoices.
Tabs Items API
The Items API from Tabs — 2 operation(s) for items.
Tabs Jobs API
The Jobs API from Tabs — 1 operation(s) for jobs.
Tabs Merchant API
The Merchant API from Tabs — 2 operation(s) for merchant.
Tabs Obligations API
The Obligations API from Tabs — 1 operation(s) for obligations.
Tabs Payments API
The Payments API from Tabs — 1 operation(s) for payments.
Tabs Performance Obligations API
The Performance Obligations API from Tabs — 2 operation(s) for performance obligations.
Tabs Products API
The Products API from Tabs — 2 operation(s) for products.
Tabs Projects API
The Projects API from Tabs — 1 operation(s) for projects.
Tabs Renewals API
The Renewals API from Tabs — 1 operation(s) for renewals.
Tabs Reports API
The Reports API from Tabs — 2 operation(s) for reports.
Tabs Revenue API
The Revenue API from Tabs — 1 operation(s) for revenue.
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.
tabs-mcp.yml
MCP SERVERRate 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.
Tabs Rate Limits
RATE LIMITSSecurity 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.
Resources
Every other property we hold for Tabs — 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 3
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 6
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/tabs · machine-readable index on apis.io