How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Divvy website screenshot

Divvy

Divvy is a corporate card and spend-management platform (free software plus business credit cards) that was acquired by BILL and now operates as BILL Spend & Expense; getdivvy.com redirects to bill.com. Its API for budgets, users, virtual cards, transactions, and reimbursements is delivered through the BILL developer platform (developer.bill.com) as part of the BILL v3 API, authenticated with a Spend & Expense API token, with a documented webhook event surface, dated changelog, sandbox environment, and per-token rate limits. This profile was surfaced as an Insight Partners portfolio company and has been enriched from BILL's public developer surface.

agent native

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.

Kin Score

API Evangelist profiles Divvy the way a machine reads it — 54 machine-readable artifacts across 2 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 — Divvy scores 53.0/100 (developing), with a separate agent-readiness read of 63/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0
Composite quality — 53.0/100 · developing
Contract Quality 16.7 / 25
Access Clarity 8.9 / 20
Discoverability 5.2 / 10
Divvy Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Divvy's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/divvy/"
   title="Divvy on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/divvy.svg"
       alt="Divvy Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Divvy

Each block below is one kind of artifact we hold for Divvy. 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 35

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.

Divvy Attachments API

The attachments API from Divvy — 4 operation(s) for attachments.

Divvy Authentication API

The authentication API from Divvy — 4 operation(s) for authentication.

Divvy Bill Approvals API

The bill-approvals API from Divvy — 4 operation(s) for bill-approvals.

Divvy Bills API

The bills API from Divvy — 6 operation(s) for bills.

Divvy Budgets API

The budgets API from Divvy — 5 operation(s) for budgets.

Divvy Cards API

The cards API from Divvy — 5 operation(s) for cards.

Divvy Classifications API

The classifications API from Divvy — 49 operation(s) for classifications.

Divvy Credit Memos API

The credit-memos API from Divvy — 7 operation(s) for credit-memos.

Divvy Custom Fields API

The custom-fields API from Divvy — 4 operation(s) for custom-fields.

Divvy Customers API

The customers API from Divvy — 12 operation(s) for customers.

Divvy Documents API

The documents API from Divvy — 3 operation(s) for documents.

Divvy Events API

The events API from Divvy — 3 operation(s) for events.

Divvy Exports API

The exports API from Divvy — 2 operation(s) for exports.

Divvy Funding Accounts API

The funding-accounts API from Divvy — 13 operation(s) for funding-accounts.

Divvy Health API

The health API from Divvy — 1 operation(s) for health.

Divvy Invoices API

The invoices API from Divvy — 7 operation(s) for invoices.

Divvy Mfa API

The mfa API from Divvy — 6 operation(s) for mfa.

Divvy Network API

The network API from Divvy — 5 operation(s) for network.

Divvy Organization Users API

The organization-users API from Divvy — 4 operation(s) for organization-users.

Divvy Organizations API

The organizations API from Divvy — 5 operation(s) for organizations.

Divvy Partner API

The partner API from Divvy — 11 operation(s) for partner.

Divvy Payment Terms API

The payment-terms API from Divvy — 2 operation(s) for payment-terms.

Divvy Payments API

The payments API from Divvy — 10 operation(s) for payments.

Divvy Receivable Payments API

The receivable-payments API from Divvy — 2 operation(s) for receivable-payments.

Divvy Recurring Invoices API

The recurring-invoices API from Divvy — 4 operation(s) for recurring-invoices.

Divvy Recurringbills API

The recurringbills API from Divvy — 4 operation(s) for recurringbills.

Divvy Reimbursements API

The reimbursements API from Divvy — 6 operation(s) for reimbursements.

Divvy Reports API

The reports API from Divvy — 1 operation(s) for reports.

Divvy Risk Verifications API

The risk-verifications API from Divvy — 2 operation(s) for risk-verifications.

Divvy Roles API

The roles API from Divvy — 2 operation(s) for roles.

Divvy Subscriptions API

The subscriptions API from Divvy — 4 operation(s) for subscriptions.

Divvy Transactions API

The transactions API from Divvy — 8 operation(s) for transactions.

Divvy Users API

The users API from Divvy — 3 operation(s) for users.

Divvy Vendor Credits API

The vendor-credits API from Divvy — 5 operation(s) for vendor-credits.

Divvy Vendors API

The vendors API from Divvy — 8 operation(s) for vendors.

Scroll within the panel for all 35 ·

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.

Divvy Rate Limits

5 limits

RATE LIMITS

Event 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.

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.

Divvy Context

120 classes · 149 properties

JSON-LD

Spectral Rules 1

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.

Divvy API Rules

15 rules · 9 errors · 5 warnings

SPECTRAL

JSON Schema 12

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.

BudgetCreateDto

21 properties

JSON SCHEMA

EventDto

7 properties

JSON SCHEMA

InvoiceReplaceRequestDto

14 properties

JSON SCHEMA

InvoiceResponseDto

28 properties

JSON SCHEMA

PaymentRequestDto

12 properties

JSON SCHEMA

PaymentResponseDto

28 properties

JSON SCHEMA

SendTestEventRequestDto

12 properties

JSON SCHEMA

SubscriptionRequestDto

4 properties

JSON SCHEMA

SubscriptionResponseDto

8 properties

JSON SCHEMA

SubscriptionUpdateRequestDto

4 properties

JSON SCHEMA

TransactionResponseDto

54 properties

JSON SCHEMA

Scroll within the panel for all 12 ·

Security 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.

Divvy Authentication

apiKey · 3 schemes

SECURITY

Divvy Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

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.

Divvy Agentic Access

326 operations · 208 acting

326 operations · 208 acting

AGENTIC

Resources

Every other property we hold for Divvy — 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 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/divvy · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Divvy, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.