Fragment

Fragment is the ledger API for engineers who move money. It provides a double-entry accounting engine — "the database for money" — that lets developers model any funds flow as declarative, typed schemas and post balanced, immutable ledger entries through a GraphQL API. Fragment generates a typesafe SDK from your chart-of-accounts schema, tracks real-time, historical, period, and strongly-consistent balances across multi-currency and custom-currency accounts, and reconciles internal ledgers against external systems (Stripe, Increase, Unit, banks) via linked and external accounts. Every write mutation is idempotent (per-Ledger idempotency keys), responses are GraphQL union types with typed errors, list queries are cursor-paginated, and the API is deployed across AWS regions. Fragment is used by companies including Bill, Ramp, Pleo, AtoB, Basic Capital, and Nala, and is backed by General Catalyst.

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.

How we profile Fragment

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

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.

Fragment Ledger API

Fragment's GraphQL Ledger API. Store a double-entry chart-of-accounts schema, create ledgers, post idempotent ledger entries and lines, read aggregated / historical / period / s...

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.

fragment-mcp.yml

MCP SERVER

Security Posture 4

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.

Fragment Authentication

oauth2 · 1 scheme

SECURITY

Fragment Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Fragment Vulnerability Disclosure

Hackerone · contact published

SECURITY

Fragment Trust Center

SOC 2 Type II

SECURITY

Resources

Every other property we hold for Fragment — 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.

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