Abacus
Abacus (now part of Emburse Spend) is an expense management platform that allows businesses to streamline expense reporting, receipts, and reimbursements. The Abacus API is available to partners and enterprise customers, providing programmatic access to member management and expense operations using OAuth 2.0 authentication.
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 Abacus the way a machine reads it — 53 machine-readable artifacts across 3 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 — Abacus scores 59.8/100 (developing), 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 Abacus
Each block below is one kind of artifact we hold for Abacus. 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 3
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.
Abacus Authentication API
OAuth 2.0 authentication operations
Abacus Expenses API
Expense report management and operations
Abacus Members API
Member management operations for inviting and managing expense users
Pricing 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.
Abacus Plans Pricing
PLANSRate 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.
Abacus 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.
Abacus Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Member Management
Invite, update, and suspend organization members programmatically
Expense Tracking
Retrieve and filter expense reports by status, member, and date range
OAuth 2.0 Authentication
Secure API access using client credentials grant flow
Receipt Management
Link receipts to expense reports via URL references
Multi-category Expenses
Categorize expenses across meals, travel, lodging, office supplies, and software
Paginated Results
Paginated API responses with configurable page sizes
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Abacus Api Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Abacus API Rules
SPECTRALAbacus API Rules
SPECTRALJSON Schema 8
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ExpenseListResponse
JSON SCHEMAExpense
JSON SCHEMAInviteMemberRequest
JSON SCHEMAMemberListResponse
JSON SCHEMAMember
JSON SCHEMAOAuthTokenRequest
JSON SCHEMAOAuthTokenResponse
JSON SCHEMAUpdateMemberRequest
JSON SCHEMAScroll within the panel for all 8 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Abacus Expense List Response Structure
JSON STRUCTUREAbacus Expense Structure
JSON STRUCTUREAbacus Invite Member Request Structure
JSON STRUCTUREAbacus Member List Response Structure
JSON STRUCTUREAbacus Member Structure
JSON STRUCTUREAbacus Oauth Token Request Structure
JSON STRUCTUREAbacus Oauth Token Response Structure
JSON STRUCTUREAbacus Update Member Request Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 8
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Abacus Expense Example
EXAMPLEAbacus Member Example
EXAMPLEScroll within the panel for all 8 ·
Security 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Employee Onboarding
Automatically invite new employees to the expense platform via API
Employee Offboarding
Programmatically suspend departed employees from expense access
Expense Reconciliation
Retrieve and reconcile expense reports for accounting integration
Spend Analytics
Pull expense data by category, member, or date range for reporting
Third-party Integration
Connect Abacus expense data with ERP and accounting systems
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
QuickBooks
Sync expense data with QuickBooks for accounting reconciliation
Xero
Integrate with Xero for automated expense accounting
NetSuite
Connect expense reports with NetSuite ERP
Sage Intacct
Sync expenses with Sage Intacct for financial management
Resources
Every other property we hold for Abacus — 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 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/abacus · machine-readable index on apis.io