Thanos
Open-source, highly available Prometheus setup with long-term storage capabilities that provides a global query view across multiple Prometheus servers.
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 Thanos the way a machine reads it — 52 machine-readable artifacts across 10 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 — Thanos scores 48.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 Thanos
Each block below is one kind of artifact we hold for Thanos. 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 10
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.
Thanos Alerts API
Endpoints for querying currently active alerts.
Thanos Blocks API
Block metadata inspection and compaction status endpoints.
Thanos Health API
Liveness and readiness probes for the Compactor.
Thanos Metadata API
The Metadata API from Thanos — 3 operation(s) for metadata.
Thanos Metrics API
Prometheus metrics for monitoring Compactor performance.
Thanos Query API
The Query API from Thanos — 2 operation(s) for query.
Thanos Remote Write API
Prometheus Remote Write ingestion endpoint.
Thanos Rules API
The Rules API from Thanos — 2 operation(s) for rules.
Thanos Stores API
The Stores API from Thanos — 1 operation(s) for stores.
Thanos Targets API
The Targets API from Thanos — 1 operation(s) for targets.
Scroll within the panel for all 10 ·
Open Collections 6
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).
Thanos Compact API
OPEN COLLECTIONThanos Query API
OPEN COLLECTIONThanos Receive API
OPEN COLLECTIONThanos Ruler API
OPEN COLLECTIONThanos Sidecar API
OPEN COLLECTIONThanos Store Gateway 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.
Thanos Plans Pricing
PLANSRate 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.
Thanos 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.
Thanos Finops
FINOPSSemantic 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.
Thanos Context
JSON-LDSpectral Rules 2
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.
Thanos API Rules
SPECTRALThanos API Rules
SPECTRALJSON Schema 23
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.
Thanos Query Response
JSON SCHEMAThanos Store Info
JSON SCHEMAActiveTarget
JSON SCHEMAAlert
JSON SCHEMAAlertingRule
JSON SCHEMAAlertsResponse
JSON SCHEMABlockMeta
JSON SCHEMABlocksResponse
JSON SCHEMADroppedTarget
JSON SCHEMAErrorResponse
JSON SCHEMALabelsResponse
JSON SCHEMALabelValuesResponse
JSON SCHEMAMatrixResult
JSON SCHEMAQueryResponse
JSON SCHEMARecordingRule
JSON SCHEMARuleGroup
JSON SCHEMARulesResponse
JSON SCHEMAScalarResult
JSON SCHEMASeriesResponse
JSON SCHEMAStoreInfo
JSON SCHEMAStoresResponse
JSON SCHEMATargetsResponse
JSON SCHEMAVectorResult
JSON SCHEMAScroll within the panel for all 23 ·
JSON Structure 2
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.
Thanos Query Structure
JSON STRUCTUREThanos Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
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 Thanos — 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 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/thanos · machine-readable index on apis.io