Chronosphere
Chronosphere is a cloud-native observability platform for controlling the cost and volume of telemetry data at scale, spanning metrics, logs, traces and change events. It ships an Observability Platform (dashboards, monitors, SLOs, differential diagnosis, PromQL querying and metrics shaping) and a Telemetry Pipeline built on Fluent Bit, acquired with Calyptia. Its APIs are per-tenant HTTP/JSON: a Config API for resources as code, a Data API for events, logs and traces, and a State API for usage and rule health, with Prometheus-compatible query endpoints, an open-source MCP server, a Terraform provider and the Chronoctl CLI. Palo Alto Networks completed its acquisition of Chronosphere in 2026.
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 Chronosphere the way a machine reads it — 80 machine-readable artifacts across 3 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 — Chronosphere scores 51.2/100 (developing), with a separate agent-readiness read of 55/100 (agent native). 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-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Chronosphere'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/chronosphere/"
title="Chronosphere on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/chronosphere.svg"
alt="Chronosphere Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/chronosphere/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/chronosphere/"
title="Chronosphere on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/chronosphere/card.svg"
alt="Chronosphere 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 Chronosphere
Each block below is one kind of artifact we hold for Chronosphere. 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 35
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.
Chronosphere
The Chronosphere HTTP/JSON API surface for Observability Platform, served from a per-customer subdomain. The Config V1 API alone carries 183 operations across 39 resource types,...
Chronosphere Bucket API
The Bucket API from Chronosphere — 2 operation(s) for bucket.
Chronosphere ClassicDashboard API
The ClassicDashboard API from Chronosphere — 2 operation(s) for classicdashboard.
Chronosphere Collection API
The Collection API from Chronosphere — 2 operation(s) for collection.
Chronosphere Dashboard API
The Dashboard API from Chronosphere — 2 operation(s) for dashboard.
Chronosphere Dataset API
The Dataset API from Chronosphere — 2 operation(s) for dataset.
Chronosphere DerivedLabel API
The DerivedLabel API from Chronosphere — 2 operation(s) for derivedlabel.
Chronosphere DerivedMetric API
The DerivedMetric API from Chronosphere — 2 operation(s) for derivedmetric.
Chronosphere DropRule API
The DropRule API from Chronosphere — 2 operation(s) for droprule.
Chronosphere GcpMetricsIntegration API
The GcpMetricsIntegration API from Chronosphere — 2 operation(s) for gcpmetricsintegration.
Chronosphere GrafanaDashboard API
The GrafanaDashboard API from Chronosphere — 2 operation(s) for grafanadashboard.
Chronosphere LogAllocationConfig API
The LogAllocationConfig API from Chronosphere — 1 operation(s) for logallocationconfig.
Chronosphere LogIngestConfig API
The LogIngestConfig API from Chronosphere — 1 operation(s) for logingestconfig.
Chronosphere LogScaleAction API
The LogScaleAction API from Chronosphere — 2 operation(s) for logscaleaction.
Chronosphere LogScaleAlert API
The LogScaleAlert API from Chronosphere — 2 operation(s) for logscalealert.
Chronosphere MappingRule API
The MappingRule API from Chronosphere — 2 operation(s) for mappingrule.
Chronosphere Monitor API
The Monitor API from Chronosphere — 2 operation(s) for monitor.
Chronosphere MutingRule API
The MutingRule API from Chronosphere — 2 operation(s) for mutingrule.
Chronosphere NotificationPolicy API
The NotificationPolicy API from Chronosphere — 2 operation(s) for notificationpolicy.
Chronosphere Notifier API
The Notifier API from Chronosphere — 2 operation(s) for notifier.
Chronosphere OtelMetricsIngestion API
The OtelMetricsIngestion API from Chronosphere — 1 operation(s) for otelmetricsingestion.
Chronosphere RecordingRule API
The RecordingRule API from Chronosphere — 2 operation(s) for recordingrule.
Chronosphere ResourcePools API
The ResourcePools API from Chronosphere — 1 operation(s) for resourcepools.
Chronosphere RollupRule API
The RollupRule API from Chronosphere — 2 operation(s) for rolluprule.
Chronosphere Service API
The Service API from Chronosphere — 1 operation(s) for service.
Chronosphere ServiceAccount API
The ServiceAccount API from Chronosphere — 2 operation(s) for serviceaccount.
Chronosphere SLO API
The SLO API from Chronosphere — 2 operation(s) for slo.
Chronosphere Team API
The Team API from Chronosphere — 2 operation(s) for team.
Chronosphere TraceBehavior API
The TraceBehavior API from Chronosphere — 2 operation(s) for tracebehavior.
Chronosphere TraceBehaviorConfig API
The TraceBehaviorConfig API from Chronosphere — 1 operation(s) for tracebehaviorconfig.
Chronosphere TraceJaegerRemoteSamplingStrategy API
The TraceJaegerRemoteSamplingStrategy API from Chronosphere — 2 operation(s) for tracejaegerremotesamplingstrategy.
Chronosphere TraceMetricsRule API
The TraceMetricsRule API from Chronosphere — 2 operation(s) for tracemetricsrule.
Chronosphere TraceTailSamplingRules API
The TraceTailSamplingRules API from Chronosphere — 1 operation(s) for tracetailsamplingrules.
Chronosphere Data V1 API
The Data API from Chronosphere - 9 operations for querying and writing telemetry: change events, log range queries, trace listing, metric metadata and dashboard panel annotations.
Chronosphere State V1 API
The State API from Chronosphere - 3 read-only operations exposing derived state: metric usage by metric name, metric usage by label name, and rule evaluation health. The cost an...
Scroll within the panel for all 35 ·
Open Collections 34
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).
API Collection
OPEN COLLECTIONConfig V1 Bucket API
OPEN COLLECTIONConfig V1 Bucket ClassicDashboard API
OPEN COLLECTIONConfig V1 Bucket Collection API
OPEN COLLECTIONConfig V1 Bucket Dashboard API
OPEN COLLECTIONConfig V1 Bucket Dataset API
OPEN COLLECTIONConfig V1 Bucket DerivedLabel API
OPEN COLLECTIONConfig V1 Bucket DerivedMetric API
OPEN COLLECTIONConfig V1 Bucket DropRule API
OPEN COLLECTIONConfig V1 Bucket GcpMetricsIntegration API
OPEN COLLECTIONConfig V1 Bucket GrafanaDashboard API
OPEN COLLECTIONConfig V1 Bucket LogAllocationConfig API
OPEN COLLECTIONConfig V1 Bucket LogIngestConfig API
OPEN COLLECTIONConfig V1 Bucket LogScaleAction API
OPEN COLLECTIONConfig V1 Bucket LogScaleAlert API
OPEN COLLECTIONConfig V1 Bucket MappingRule API
OPEN COLLECTIONConfig V1 Bucket Monitor API
OPEN COLLECTIONConfig V1 Bucket MutingRule API
OPEN COLLECTIONConfig V1 Bucket NotificationPolicy API
OPEN COLLECTIONConfig V1 Bucket Notifier API
OPEN COLLECTIONConfig V1 Bucket OtelMetricsIngestion API
OPEN COLLECTIONConfig V1 Bucket RecordingRule API
OPEN COLLECTIONConfig V1 Bucket ResourcePools API
OPEN COLLECTIONConfig V1 Bucket RollupRule API
OPEN COLLECTIONConfig V1 Bucket Service API
OPEN COLLECTIONConfig V1 Bucket ServiceAccount API
OPEN COLLECTIONConfig V1 Bucket SLO API
OPEN COLLECTIONConfig V1 Bucket Team API
OPEN COLLECTIONConfig V1 Bucket TraceBehavior API
OPEN COLLECTIONConfig V1 Bucket TraceBehaviorConfig API
OPEN COLLECTIONConfig V1 Bucket TraceJaegerRemoteSamplingStrategy API
OPEN COLLECTIONConfig V1 Bucket TraceMetricsRule API
OPEN COLLECTIONConfig V1 Bucket TraceTailSamplingRules API
OPEN COLLECTIONConfig V1 API
OPEN COLLECTIONScroll within the panel for all 34 ·
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.
Chronosphere MCP server
Chronosphere ships two Model Context Protocol surfaces. The product MCP server exposes the Observability Platform itself — metrics, logs, traces, events, monitor status and the ...
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.
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.
Chronosphere 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.
Chronosphere Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Chronosphere Webhooks
ASYNCAPIJSON Schema 1
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.
Chronosphere Dashboard
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.
Chronosphere Trust Center
SOC 2, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA, FedRAMP, GDPR, CSA STAR
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Chronosphere — 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 6
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/chronosphere · machine-readable index on apis.io
This is an independent, third-party profile of Chronosphere, 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.