# Brevo — API Agent Score

> Score: 93/100 (Grade: A+) | Domain: brevo.com | Rubric: 1.0.0 | Checked: September 24, 2026

Brevo scored 93/100 (A+), classified "ai-ready".

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

## Summary

- Overall: 93/100 (A+)
- Classification: ai-ready

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 76/100 (B)
- Agent Discovery: 99/100 (A+)
- Agent Understanding: 87/100 (A)
- Agent Usability: 100/100 (A+)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "3.0.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Schema coverage & depth — 5958/5958 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.
- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — Docs show code samples in 3 language(s) (top: typescript, curl, shell), and 2 of 20 sampled pages offer ≥ 2 languages side by side. Investigated: docs 100%, sdk 100%, spec 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://developers.brevo.com/docs/quickstart includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Code samples in docs — Docs show code samples in 3 language(s) (top: typescript, curl, shell), and 2 of 20 sampled pages offer ≥ 2 languages side by side. Investigated: docs 100%.
- [pass] Description completeness — 93% of operations and parameters carry substantive descriptions (262 of 290 ops, 525 of 551 params), the main semantic cue an agent relies on. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog is documented on the docs site at https://developers.brevo.com/changelog, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 2 pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://developers.brevo.com/docs/getting-started/llms.txt: No H1 heading found. Investigated: docs 96%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/developers_brevo, 8589 snippets). Investigated: docs 100%, sdk 92%, cli 0%, mcp 0%, wellknown 0%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 15 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (camelCase). Investigated: sdk 100%, spec 50%.
- [pass] Agent-navigable, token-efficient docs — All 2 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Docs structured data — JSON-LD Article markup covers 20 of 20 assessed pages (100%), but no page carries dateModified, so answer engines can't tell how current the docs are. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 4% (threshold 35% for full credit).

### Agent Usability

- [pass] Idempotency documented — idempotency is documented on the docs site at https://developers.brevo.com/docs/heterogenous-versions-batch-emails, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Rate-limit signaling — rate-limit behavior is documented on the docs site at https://developers.brevo.com/docs/api-limits, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — Pagination parameters are present on the 19 list endpoint(s), so an agent can page through results. Investigated: spec 100%, docs 100%, sdk 57%.
- [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%.

## Executive Summary

Brevo's API program performs well on agent discoverability and agent understanding — partners and their agents can find and parse your API surface without friction. The most meaningful gap is in developer onboarding: there is no detectable self-service signup path, which means partners cannot get hands-on without a manual touchpoint. Closing that onboarding gap and reinforcing the already-strong agent-readiness layer with richer executable context should be the immediate priority to accelerate partner activation.