TimescaleDB / Tiger Data
TimescaleDB (now part of Tiger Data) is a PostgreSQL-native time-series database featuring hypertables, columnstore (Hypercore), continuous aggregates, retention policies and hyperfunctions. The managed Tiger Cloud platform exposes a public REST API for managing projects, services, VPCs, peering and read replicas, while the database itself is consumed via standard PostgreSQL wire protocol.
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.
API Evangelist profiles TimescaleDB / Tiger Data the way a machine reads it — 43 machine-readable artifacts across 6 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 — TimescaleDB / Tiger Data scores 51.3/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 TimescaleDB / Tiger Data
Each block below is one kind of artifact we hold for TimescaleDB / Tiger Data. 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 6
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.
TimescaleDB PostgreSQL Wire Interface
The database itself is accessed via the PostgreSQL wire protocol (port 5432), with TimescaleDB SQL functions for hypertable management, compression, continuous aggregates and hy...
TimescaleDB / Tiger Data Analytics API
Track analytics events.
TimescaleDB / Tiger Data Auth API
Authentication and authorization information.
TimescaleDB / Tiger Data Read Replica Sets API
The Read Replica Sets API from TimescaleDB / Tiger Data — 6 operation(s) for read replica sets.
TimescaleDB / Tiger Data Services API
Manage services, read replicas, and their associated actions.
TimescaleDB / Tiger Data VPCs API
Manage VPCs and their peering connections.
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).
Tiger Cloud 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.
Timescaledb 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.
Timescaledb Finops
FINOPSSpectral 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.
TimescaleDB / Tiger Data API Rules
SPECTRALJSON Schema 27
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.
AuthInfo
JSON SCHEMAConnectionPooler
JSON SCHEMADeployStatus
JSON SCHEMAEndpoint
JSON SCHEMAEnvironmentTag
JSON SCHEMAError
JSON SCHEMAForkServiceCreate
JSON SCHEMAForkSpec
JSON SCHEMAForkStrategy
JSON SCHEMAHAReplica
JSON SCHEMAPeering
JSON SCHEMAPeeringCreate
JSON SCHEMAReadReplicaSet
JSON SCHEMAReadReplicaSetCreate
JSON SCHEMAResizeInput
JSON SCHEMAService
JSON SCHEMAServiceCreate
JSON SCHEMAServiceLogEntry
JSON SCHEMAServiceLogs
JSON SCHEMAServiceType
JSON SCHEMAServiceVPCInput
JSON SCHEMASetEnvironmentInput
JSON SCHEMASetHAReplicaInput
JSON SCHEMAUpdatePasswordInput
JSON SCHEMAVPC
JSON SCHEMAVPCCreate
JSON SCHEMAVPCRename
JSON SCHEMAScroll within the panel for all 27 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Timescaledb Structure
JSON STRUCTURESecurity 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 TimescaleDB / Tiger Data — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/timescaledb · machine-readable index on apis.io