# Grafana — API Agent Score

> Score: 72/100 (Grade: B) | Domain: grafana.com | Rubric: 1.0.0 | Checked: July 24, 2026

Grafana scored 72/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/grafana)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 72/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 56/100 (D)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 79/100 (B)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 1/3 parameters are deeply nested or free-form maps. Investigated: sdk 93%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="0.0.1" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://grafana.com/auth/sign-up (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Changelog published — changelog documented in the docs site at https://grafana.com/whats-new/. Investigated: spec 100%, docs 100%, sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Description completeness — 56% description completeness. Investigated: spec 0%, sdk 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/grafana, 89376 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — Only 40/50 same-origin sampled links resolve (80%); 10 broken. Investigated: docs 75%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 64% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 11 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 93% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 18 of 50 sampled pages convert to over 100K chars (max 814K HTML → 259K markdown (79% boilerplate)). Investigated: docs 80%.
- [warn] Docs structured data — OpenGraph/meta tags only across 1 assessed pages — no JSON-LD for answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 4% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 52 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Grafana's API program is a clear strength in discoverability and contract design — partners and agents can find and read the API surface without friction. The two areas that most undermine partner outcomes today are developer experience and agent usability: partners lack the hands-on onboarding materials to reach a first successful call quickly, and agents lack the runnable, annotated context they need to integrate reliably. Closing these gaps — starting with richer descriptions and quickstart content, then adding executable collections and operational reliability signals — will meaningfully shorten partner time to value and reduce integration support load.