Tembo
Tembo (tembo.io) is a cloud platform for running AI coding agents (Claude Code, Codex, Cursor, Amp, OpenCode and others) in isolated, shareable sandbox environments connected to repositories, issue trackers, observability tools and databases, with a self-hosted Enterprise option. It publishes a public REST API (OpenAPI 3.1, 152 operations at api.tembo.io), TypeScript and Python SDKs, and an official remote MCP server at mcp.tembo.io. Surfaced by the databases-postgres market-gap harvest: Tembo was previously known for its managed Postgres platform, but its current site, docs and API describe the agent platform only, and the former tembo-io GitHub organization lists 0 public repositories (checked 2026-10-13).
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Tembo the way a machine reads it — 33 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 — Tembo scores 69.6/100 (exemplar), 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. 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
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Tembo'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/tembo/"
title="Tembo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tembo.svg"
alt="Tembo Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/tembo/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/tembo/"
title="Tembo on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/tembo/card.svg"
alt="Tembo Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Tembo
Each block below is one kind of artifact we hold for Tembo. 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 19
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.
Tembo Agents API
The Agents API from Tembo — 13 operation(s) for agents.
Tembo API Keys API
The API Keys API from Tembo — 2 operation(s) for api keys.
Tembo Artifacts API
The Artifacts API from Tembo — 2 operation(s) for artifacts.
Tembo Authentication API
The Authentication API from Tembo — 1 operation(s) for authentication.
Tembo Billing API
The Billing API from Tembo — 2 operation(s) for billing.
Tembo Insights API
The Insights API from Tembo — 3 operation(s) for insights.
Tembo Integrations API
The Integrations API from Tembo — 13 operation(s) for integrations.
Tembo MCP Connections API
The MCP Connections API from Tembo — 4 operation(s) for mcp connections.
Tembo Messages API
The Messages API from Tembo — 3 operation(s) for messages.
Tembo Models API
The Models API from Tembo — 2 operation(s) for models.
Tembo OAuth API
The OAuth API from Tembo — 1 operation(s) for oauth.
Tembo Organizations API
The Organizations API from Tembo — 10 operation(s) for organizations.
Tembo Projects API
The Projects API from Tembo — 12 operation(s) for projects.
Tembo Pull requests API
The Pull requests API from Tembo — 2 operation(s) for pull requests.
Tembo Repositories API
The Repositories API from Tembo — 2 operation(s) for repositories.
Tembo Runtimes API
The Runtimes API from Tembo — 1 operation(s) for runtimes.
Tembo Sessions API
The Sessions API from Tembo — 10 operation(s) for sessions.
Tembo Skills API
The Skills API from Tembo — 4 operation(s) for skills.
Tembo Users API
The Users API from Tembo — 8 operation(s) for users.
Scroll within the panel for all 19 ·
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.
Tembo MCP Server
Official Tembo MCP server. Per the docs, its tools are generated from the same OpenAPI schema as the Tembo API reference and TypeScript SDK, and it can perform the same API oper...
MCP SERVERPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Tembo Plans Pricing
PLANSSemantic 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.
Tembo Context
JSON-LDSpectral 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.
Tembo API Rules
SPECTRALJSON Schema 6
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.
AgentOptionsInput
JSON SCHEMAAgentOptions
JSON SCHEMAAgentState
JSON SCHEMASessionEventData
JSON SCHEMATipTapDocument
JSON SCHEMATriggerFilters
JSON SCHEMASecurity 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.
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 Tembo — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tembo · machine-readable index on apis.io
This is an independent, third-party profile of Tembo, 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.