TigerBeetle website screenshot

TigerBeetle

TigerBeetle is an open-source (Apache 2.0) distributed financial accounting and transactions database, purpose-built for high-throughput, mission-critical double-entry bookkeeping and online transaction processing (OLTP). It is NOT an HTTP/REST API and ships no OpenAPI - the database is accessed over a custom binary wire protocol on TCP (default port 3000) via official client libraries for .NET, Go, Java, Node.js, Python, Ruby, and Rust. The "API" is the set of client operations - create_accounts, create_transfers, lookup_accounts, lookup_transfers, get_account_transfers, get_account_balances, query_accounts, and query_transfers - that use fixed-size, cache-line-aligned structs for zero-deserialization performance. TigerBeetle is self-hostable; a fully managed service is also offered to select enterprise partners via sales@tigerbeetle.com.

TigerBeetle publishes 4 APIs on the APIs.io network. Tagged areas include Financial, Accounting, Transaction, Database, and Double-Entry.

TigerBeetle’s developer surface includes documentation, engineering blog, and 6 more developer resources.

16.4/100 emerging ▬ flat Agent 0/100 human only saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
AccessFreemium
4 APIs
FinancialAccountingTransactionDatabaseDouble-EntryLedgerOLTPDistributedOpen-SourceBinary Protocol

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/tigerbeetle: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

TigerBeetle Accounts API

Client-library operations for managing 128-byte double-entry accounts - create_accounts (establish immutable accounts on a ledger with debit/credit constraint flags), lookup_acc...

TigerBeetle Transfers API

Client-library operations for moving funds between accounts as immutable 128-byte double-entry transfers - create_transfers (single-phase, plus two-phase pending / post-pending ...

TigerBeetle Account Balances API

The get_account_balances operation returns the historical balances of an account over time (for accounts created with the history flag), each a point-in-time AccountBalance reco...

TigerBeetle Account Filter Queries API

Query surface for retrieving the transfers and balances tied to a single account. The get_account_transfers operation takes an AccountFilter (account_id, timestamp range, limit,...

Pricing Plans 1

Published pricing tiers and plan structures.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Tigerbeetle Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: tigerbeetle
url: https://raw.githubusercontent.com/api-evangelist/tigerbeetle/refs/heads/main/apis.yml
name: TigerBeetle
kind: company
description: TigerBeetle is an open-source (Apache 2.0) distributed financial accounting and transactions database, purpose-built
  for high-throughput, mission-critical double-entry bookkeeping and online transaction processing (OLTP). It is NOT an HTTP/REST
  API and ships no OpenAPI - the database is accessed over a custom binary wire protocol on TCP (default port 3000) via official
  client libraries for .NET, Go, Java, Node.js, Python, Ruby, and Rust. The "API" is the set of client operations - create_accounts,
  create_transfers, lookup_accounts, lookup_transfers, get_account_transfers, get_account_balances, query_accounts, and query_transfers
  - that use fixed-size, cache-line-aligned structs for zero-deserialization performance. TigerBeetle is self-hostable; a
  fully managed service is also offered to select enterprise partners via sales@tigerbeetle.com.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/tigerbeetle.png
tags:
- Financial
- Accounting
- Transaction
- Database
- Double-Entry
- Ledger
- OLTP
- Distributed
- Open-Source
- Binary Protocol
tags_raw:
- Financial
- Accounting
- Transactions
- Database
- Double-Entry
- Ledger
- OLTP
- Distributed
- Open Source
- Binary Protocol
created: '2026-07-02'
modified: '2026-07-02'
specificationVersion: '0.23'
apis:
- aid: tigerbeetle:tigerbeetle-accounts-api
  name: TigerBeetle Accounts API
  tags:
  - Account
  - Ledger
  - Double-Entry
  tags_raw:
  - Accounts
  - Ledger
  - Double-Entry
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.tigerbeetle.com/reference/account/
  description: Client-library operations for managing 128-byte double-entry accounts - create_accounts (establish immutable
    accounts on a ledger with debit/credit constraint flags), lookup_accounts (fetch accounts by 128-bit id), and query_accounts
    (filter accounts by ledger, code, and user_data). Accounts carry pending and posted debit/credit balances. These are binary
    wire-protocol operations invoked through the official clients, not HTTP endpoints; there is no REST baseURL or OpenAPI.
  properties:
  - url: https://docs.tigerbeetle.com/reference/account/
    type: Documentation
  - url: https://docs.tigerbeetle.com/reference/requests/create_accounts/
    type: APIReference
  - url: https://docs.tigerbeetle.com/reference/requests/lookup_accounts/
    type: APIReference
  - url: https://docs.tigerbeetle.com/reference/requests/query_accounts/
    type: APIReference
- aid: tigerbeetle:tigerbeetle-transfers-api
  name: TigerBeetle Transfers API
  tags:
  - Transfers
  - Two-Phase
  - Pending
  - Double-Entry
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.tigerbeetle.com/reference/transfer/
  description: Client-library operations for moving funds between accounts as immutable 128-byte double-entry transfers -
    create_transfers (single-phase, plus two-phase pending / post-pending / void-pending transfers, linked transfers, balancing
    transfers, and timeouts), lookup_transfers (fetch by 128-bit id), and query_transfers (filter by ledger, code, and user_data).
    Delivered over the binary TCP wire protocol via the official clients - no REST endpoints, no OpenAPI.
  properties:
  - url: https://docs.tigerbeetle.com/reference/transfer/
    type: Documentation
  - url: https://docs.tigerbeetle.com/reference/requests/create_transfers/
    type: APIReference
  - url: https://docs.tigerbeetle.com/reference/requests/lookup_transfers/
    type: APIReference
  - url: https://docs.tigerbeetle.com/reference/requests/query_transfers/
    type: APIReference
- aid: tigerbeetle:tigerbeetle-account-balances-api
  name: TigerBeetle Account Balances API
  tags:
  - Balances
  - History
  - Ledger
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.tigerbeetle.com/reference/account-balance/
  description: The get_account_balances operation returns the historical balances of an account over time (for accounts created
    with the history flag), each a point-in-time AccountBalance record of pending and posted debits and credits. A binary
    wire-protocol operation invoked through the official client libraries, not an HTTP endpoint.
  properties:
  - url: https://docs.tigerbeetle.com/reference/account-balance/
    type: Documentation
  - url: https://docs.tigerbeetle.com/reference/requests/get_account_balances/
    type: APIReference
- aid: tigerbeetle:tigerbeetle-account-filter-queries-api
  name: TigerBeetle Account Filter Queries API
  tags:
  - Query
  - Filters
  - Transfers
  tags_raw:
  - Queries
  - Filters
  - Transfers
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.tigerbeetle.com/reference/account-filter/
  description: Query surface for retrieving the transfers and balances tied to a single account. The get_account_transfers
    operation takes an AccountFilter (account_id, timestamp range, limit, direction, and flags) to page through an account's
    transfers, and the same filter drives get_account_balances. QueryFilter powers the broader query_accounts / query_transfers
    searches. Binary wire-protocol operations via the official clients - no REST, no OpenAPI.
  properties:
  - url: https://docs.tigerbeetle.com/reference/account-filter/
    type: Documentation
  - url: https://docs.tigerbeetle.com/reference/query-filter/
    type: Documentation
  - url: https://docs.tigerbeetle.com/reference/requests/get_account_transfers/
    type: APIReference
common:
- type: DomainSecurity
  url: security/tigerbeetle-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/tigerbeetle
- type: LinkedIn
  url: https://www.linkedin.com/company/tigerbeetle
- type: Website
  url: https://tigerbeetle.com/
- type: Documentation
  url: https://docs.tigerbeetle.com/
- type: Plans
  url: plans/tigerbeetle-plans-pricing.yml
- type: FinOps
  url: finops/tigerbeetle-finops.yml
- url: https://tigerbeetle.com/blog/atom.xml
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/tigerbeetle"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/tigerbeetle/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/tigerbeetle/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.