RecVue
RecVue is an enterprise revenue management platform (RevOS - the Revenue Operating System) that unifies complex billing, revenue recognition, order-to-cash, usage-based monetization, and partner settlements for the office of the CFO. It automates recurring, usage, milestone, and hybrid billing models and recognizes revenue in compliance with ASC 606 and IFRS 15, with performance-obligation tracking, allocation, deferral, and audit trails. RecVue is API-first and exposes a documented, RESTful developer API (JSON, OAuth2 client-credentials, a Bulk API for large data sets, and official Node, Ruby, JavaScript, and Python client libraries) covering orders, order lines, bill runs, billing schedules, pricing, usage/deliveries, customers, invoices/adjustments, and revenue contracts. The platform is enterprise/sales-gated for provisioning (production and sandbox tenants), but the API reference is public at developer.recvue.com.
RecVue publishes 10 API contracts indexed on the APIs.io network, including Authentication API, Billing API, Billing Schedules API, and 7 more. Tagged areas include Revenue Recognition, ASC 606, Billing, Order-to-Cash, and Revenue Management.
RecVue’s developer surface includes authentication, documentation, engineering blog, and 7 more developer resources.
What this lets a business do 3
Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Billing, Subscriptions and Monetization | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 10
Individual APIs this provider publishes, each with its own machine-readable definition.
RecVue Authentication API
OAuth2 client-credentials token issuance.
RecVue Billing API
Bill runs and invoice generation.
RecVue Billing Schedules API
Dated billing schedule records.
RecVue Customers API
Customer accounts, sites, and contacts.
RecVue Invoices API
Invoices and adjustments (AR integration).
RecVue Orders API
Order and order-line lifecycle (order-to-cash).
RecVue Pricing API
Price lists, tier pricing, and pricing rules.
RecVue Programs API
Asynchronous concurrent programs (bill runs, revenue, exports).
RecVue Revenue Recognition API
ASC 606 / IFRS 15 revenue-contract configuration.
RecVue Usage API
Usage/delivery ingestion for consumption billing.
Scroll for all 10
Open Collections 11
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
RecVue Authentication API
OPEN COLLECTIONRecVue Authentication Billing API
OPEN COLLECTIONRecVue Authentication Billing Schedules API
OPEN COLLECTIONRecVue Authentication Customers API
OPEN COLLECTIONRecVue Authentication Invoices API
OPEN COLLECTIONRecVue Authentication Orders API
OPEN COLLECTIONRecVue Authentication Pricing API
OPEN COLLECTIONRecVue Authentication Programs API
OPEN COLLECTIONRecVue Authentication Revenue Recognition API
OPEN COLLECTIONRecVue Authentication Usage API
OPEN COLLECTIONRecVue API
OPEN COLLECTIONScroll for all 11
Pricing Plans 1
Published pricing tiers and plan structures.
Recvue Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Recvue Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Recvue Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
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
Source (apis.yml)
RecVue API — frequently asked questions
Does RecVue have an API?
Yes. APIs.io lists 10 APIs from RecVue, including RecVue Authentication API, RecVue Billing API and RecVue Billing Schedules API, and 7 more.
Is there an OpenAPI specification for the RecVue API?
Yes. APIs.io indexes 10 OpenAPI specifications for RecVue, each linked for download from this page.
How do I authenticate with the RecVue API?
RecVue documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Recvue Authentication.
How much does the RecVue API cost?
APIs.io lists 1 pricing plan for RecVue, with each plan's price, limits and inclusions under Pricing Plans on this page.
Is the RecVue API ready for AI agents?
RecVue has a Kin Score of 13.7 out of 100 (emerging) and an Agent Readiness score of 21.7 (agent-aware), scored by API Evangelist on 2026-10-31.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.