# Backblaze — API Agent Score

> Score: 82/100 (Grade: A) | Domain: backblaze.com | Rubric: 1.0.0 | Checked: October 2, 2026

Backblaze scored 82/100 (A), classified "ai-ready".

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

## Summary

- Overall: 82/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 86/100 (A)
- Developer Experience: 65/100 (C)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 88/100 (A)
- Agent Usability: 76/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 354/355 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 42%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.0") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 88%, docs 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [warn] Auth declared & discoverable — The spec declares no authentication scheme, so an agent can't tell how to authenticate a request. Investigated: spec 50%, docs 50%.
- [pass] Example coverage — 100% of parameters and responses (23 of 23) include example values, grounding an agent in real payload shapes. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup available at https://www.backblaze.com/sign-up/cloud-backup, with a free tier or sandbox documented — an agent can onboard without contacting sales. Investigated: docs 100%.
- [pass] Description completeness — Only 63% of operations and parameters have substantive descriptions (29 of 35 ops, 10 of 23 params; target 90%+). Investigated: spec 100%, sdk 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://www.backblaze.com/get-started (1 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 18 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms.txt is present at llms.txt. Investigated: sdk 100%, docs 50%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/backblaze_apidocs, 962 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown); 49 rate-limited (HTTP 429). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap has lastmod on only 100% of entries, or its newest entry is over 90 days old. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "B2Error" with 99 subclasses. Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Operation purpose clarity — 100% of operations (35 of 35) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%, sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 75%.
- [pass] Agent instructions file (AGENTS.md) — Agent context file present: agents.md (AGENTS.md). Investigated: sdk 100%, wellknown 0%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 2 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 11% (threshold 35% for full credit).

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 50%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Backblaze's API program shows genuine strength in discoverability, contract quality, and documentation structure — partners and agents can find and parse the API surface without friction. The two areas that need immediate attention are change communication and onboarding speed: there is no published changelog anywhere in the spec or docs, meaning partners and their agents have no way to anticipate breaking changes, and zero code samples across 18 sampled documentation pages means a developer or coding agent must reverse-engineer every integration from scratch. Prioritize making changes visible and hands-on time instant — those two fixes will have the most direct impact on partner retention and integration success.