Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Light website screenshot

Light

Light is an agentic accounting and financial-operations platform positioned as an alternative to traditional ERPs and fragmented finance stacks. It combines a multi-entity general ledger and consolidation engine with accounts payable, accounts receivable, spend management and corporate cards, contracts and subscription billing, purchase orders and expense reimbursement. The Light API is a REST API over HTTPS returning camelCase JSON, covering 183 operations across 28 resource groups — invoice payables and receivables, credit notes, customer credits, journal entries, ledger accounts, bank accounts and transactions, cards and card transactions, contracts, purchase orders, products, vendors, customers and users. Authentication is either an API key sent as HTTP Basic or an OAuth 2.0 access token, access is governed by the same roles as user accounts, and writes on 14 operations accept an X-Idempotency-Key header. Light also publishes a live Model Context Protocol server over its documentation and markets a Claude MCP integration against the live ledger.

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 Light the way a machine reads it — 34 machine-readable artifacts across 28 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 — Light scores 45.1/100 (developing), with a separate agent-readiness read of 81/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 45.1/100 · developing
Contract Quality 11.7 / 25
Developer Ergonomics 13.5 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 81/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Light

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

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.

Light Authorization API

The Authorization API from Light — 2 operation(s) for authorization.

Light v1 - Accounting Documents API

The v1 - Accounting Documents API from Light — 1 operation(s) for v1 - accounting documents.

Light v1 - Attachments API

The v1 - Attachments API from Light — 4 operation(s) for v1 - attachments.

Light v1 - Bank Accounts API

The v1 - Bank Accounts API from Light — 4 operation(s) for v1 - bank accounts.

Light v1 - Card Balance Accounts API

The v1 - Card Balance Accounts API from Light — 4 operation(s) for v1 - card balance accounts.

Light v1 - Card Customers API

The v1 - Card Customers API from Light — 1 operation(s) for v1 - card customers.

Light v1 - Card Transactions API

The v1 - Card Transactions API from Light — 9 operation(s) for v1 - card transactions.

Light v1 - Cards API

The v1 - Cards API from Light — 4 operation(s) for v1 - cards.

Light v1 - Companies API

The v1 - Companies API from Light — 1 operation(s) for v1 - companies.

Light v1 - Contracts API

The v1 - Contracts API from Light — 10 operation(s) for v1 - contracts.

Light v1 - Credit Notes API

The v1 - Credit Notes API from Light — 10 operation(s) for v1 - credit notes.

Light v1 - Custom Properties API

The v1 - Custom Properties API from Light — 4 operation(s) for v1 - custom properties.

Light v1 - Customer Credits API

The v1 - Customer Credits API from Light — 12 operation(s) for v1 - customer credits.

Light v1 - Customers API

The v1 - Customers API from Light — 4 operation(s) for v1 - customers.

Light v1 - Entities API

The v1 - Entities API from Light — 1 operation(s) for v1 - entities.

Light v1 - Exchange API

The v1 - Exchange API from Light — 2 operation(s) for v1 - exchange.

Light v1 - Expenses API

The v1 - Expenses API from Light — 8 operation(s) for v1 - expenses.

Light v1 - Invoice Approvals API

The v1 - Invoice Approvals API from Light — 1 operation(s) for v1 - invoice approvals.

Light v1 - Invoice Payables API

The v1 - Invoice Payables API from Light — 17 operation(s) for v1 - invoice payables.

Light v1 - Invoice Receivables API

The v1 - Invoice Receivables API from Light — 11 operation(s) for v1 - invoice receivables.

Light v1 - Journal Entries API

The v1 - Journal Entries API from Light — 3 operation(s) for v1 - journal entries.

Light v1 - Ledger accounts API

The v1 - Ledger accounts API from Light — 1 operation(s) for v1 - ledger accounts.

Light v1 - Ledger Transactions API

The v1 - Ledger Transactions API from Light — 1 operation(s) for v1 - ledger transactions.

Light v1 - Products API

The v1 - Products API from Light — 3 operation(s) for v1 - products.

Light v1 - Purchase Orders API

The v1 - Purchase Orders API from Light — 9 operation(s) for v1 - purchase orders.

Light v1 - User Comments API

The v1 - User Comments API from Light — 2 operation(s) for v1 - user comments.

Light v1 - Users API

The v1 - Users API from Light — 5 operation(s) for v1 - users.

Light v1 - Vendors API

The v1 - Vendors API from Light — 2 operation(s) for v1 - vendors.

Scroll within the panel for all 28 ·

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.

light-mcp.yml

MCP SERVER

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.

Light Rate Limits

0 limits

RATE LIMITS

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.

Light Authentication

apiKey/http/oauth2 · 3 schemes

SECURITY

Light Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Light Trust Center

SOC 2 Type II, SOC 1 Type II, SOX / Sarbanes-Oxley compliance

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.

Light Agentic Access

183 operations · 120 acting · 5 human-in-the-loop

183 operations · 120 acting

AGENTIC

Resources

Every other property we hold for Light — 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 4

MCP servers, agent skills, and machine-readable catalogs

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

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