turbopuffer
turbopuffer is a serverless search engine that combines vector and full-text (BM25) search built from first principles directly on object storage. It exposes a single REST API organized around namespaces — each namespace stores documents with vector embeddings, attributes, and full-text indexes — and supports approximate nearest neighbor, full-text BM25, and hybrid query patterns with attribute filtering, ranking, and aggregation. The platform is used in production by Anthropic, Cursor, Notion, Linear, Superhuman, Pylon, Readwise, and Telus, and handles 4T+ documents, 10M+ writes/s, and 25k+ queries/s across customer fleets. Official client libraries ship for Python, TypeScript, Go, Java, Ruby, and C#, generated from a public OpenAPI 3.1 specification via Stainless. Pricing is tiered (Launch, Scale, Enterprise) with usage-based metering on storage, writes, and queries on top of monthly minimums.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles turbopuffer the way a machine reads it — 18 machine-readable artifacts across 11 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 — turbopuffer scores 41.4/100 (thin), 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 turbopuffer
Each block below is one kind of artifact we hold for turbopuffer. 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 11
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.
turbopuffer Write API
Endpoints for upserting, patching, and deleting documents within a namespace. Writes are batched into a per-namespace write-ahead log and become queryable once committed to obje...
turbopuffer Query API
Unified query endpoint that runs vector ANN, full-text BM25, and hybrid queries against a namespace, with attribute filters, top-k, aggregation groups, and ranking controls. Sup...
turbopuffer Namespaces API
Namespace lifecycle and metadata endpoints — list namespaces, read schema / dimensions / row count, warm the cache, export contents, branch_from (copy-on-write clones in constan...
turbopuffer Python SDK
Official Python client library for the turbopuffer REST API, Stainless-generated from the public OpenAPI spec.
turbopuffer TypeScript SDK
Official TypeScript / JavaScript client library for the turbopuffer REST API, Stainless-generated and published to npm.
turbopuffer Go SDK
Official Go client library for the turbopuffer REST API, Stainless-generated from the public OpenAPI spec.
turbopuffer Java SDK
Official Java / Kotlin client library for the turbopuffer REST API, Stainless-generated from the public OpenAPI spec.
turbopuffer Ruby SDK
Official Ruby client library for the turbopuffer REST API, Stainless-generated from the public OpenAPI spec.
turbopuffer C# SDK
Official C# / .NET client library for the turbopuffer REST API, Stainless-generated from the public OpenAPI spec.
tpuf-benchmark
Open-source general-purpose benchmarking tool for turbopuffer deployments. Useful for validating recall, latency, and throughput on a given workload.
turbopuffer Namespaces API
The Namespaces API from turbopuffer — 12 operation(s) for namespaces.
Scroll within the panel for all 11 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
turbopuffer API
OPEN COLLECTIONPricing 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.
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.
Turbopuffer 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.
Turbopuffer Finops
FINOPSSecurity 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.
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.
Resources
Every other property we hold for turbopuffer — 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
Access & Security 2
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/turbopuffer · machine-readable index on apis.io