Tabs
Tabs is an AI-native revenue automation platform for B2B companies, unifying billing, collections, revenue recognition, and reporting on top of a contract-driven data model. The platform ingests executed contracts and automatically generates invoices, schedules ASC 606-compliant revenue, drives collections through AI agents, and produces real-time ARR, cash, and AR reporting. It is designed for finance teams at SaaS and B2B subscription companies who need flexibility across subscription, usage-based, metered, and hybrid billing models. Tabs exposes a REST API and integrates with ERP, CRM, payment, and tax systems so contract, billing, and revenue data can flow into the rest of the finance stack. It is SOC 2 compliant and includes a unified customer record spanning contracts, usage, payments, and terms.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Tabs the way a machine reads it — 29 machine-readable artifacts across 22 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 35.0/100 (thin), with a separate agent-readiness read of 48/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.
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 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.
Tabs Platform API
REST API for the Tabs revenue automation platform that exposes the core data model of customers, contracts, items, revenue categories, obligations, invoices, payments, and usage...
Tabs BillingTerms API
The BillingTerms API from Tabs — 3 operation(s) for billingterms.
Tabs Categories API
The Categories API from Tabs — 3 operation(s) for categories.
Tabs Commitments API
The Commitments API from Tabs — 2 operation(s) for commitments.
Tabs Contracts API
The Contracts API from Tabs — 4 operation(s) for contracts.
Tabs CreditMemos API
The CreditMemos API from Tabs — 3 operation(s) for creditmemos.
Tabs Customers API
The Customers API from Tabs — 5 operation(s) for customers.
Tabs CustomFields API
The CustomFields API from Tabs — 1 operation(s) for customfields.
Tabs Events API
The Events API from Tabs — 3 operation(s) for events.
Tabs EventTypes API
The EventTypes API from Tabs — 2 operation(s) for eventtypes.
Tabs Invoices API
The Invoices API from Tabs — 4 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 — 1 operation(s) for merchant.
Tabs Obligations API
The Obligations API from Tabs — 4 operation(s) for obligations.
Tabs Payments API
The Payments API from Tabs — 3 operation(s) for payments.
Tabs PerformanceObligations API
The PerformanceObligations API from Tabs — 4 operation(s) for performanceobligations.
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.
Tabs System API
The System API from Tabs — 4 operation(s) for system.
Tabs UsageEvents API
The UsageEvents API from Tabs — 2 operation(s) for usageevents.
Scroll within the panel for all 22 ·
Open Collections 1
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).
Tabs Platform API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate 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 Fi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tabs Fi Finops
FINOPSSecurity 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 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tabs-fi · machine-readable index on apis.io