# Braze — API Agent Score

> Score: 59/100 (Grade: D) | Domain: braze.com | Rubric: 1.0.0 | Checked: July 24, 2026

Braze scored 59/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 59/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 73/100 (B)
- Developer Experience: 75/100 (B)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 46/100 (F)
- Agent Usability: 42/100 (F)

## Check Results

### API Design

- [warn] Schema coverage & depth — 1 of 12 public signatures use loose types (anyTypeRatio=0.083). Investigated: sdk 92%, spec 67%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" 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 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.braze.com/get-started; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 88% description completeness (target 90%+). Investigated: spec 100%, sdk 75%.
- [pass] Changelog published — Newest official SDK activity 2 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (3 variants scanned starting at https://www.braze.com/docs/api/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/braze, 53145 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 50%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [warn] Docs structured data — JSON-LD on 9/20 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 9% (threshold 35% for full credit).
- [fail] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: spec 0%, docs 0%.
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.

### Agent Usability

- [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] Pagination documented & consistent — 2 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Braze's API program shows meaningful strengths in discovery and overall API design, but partners and their AI agents face serious friction where it matters most: understanding what operations do, how errors should be handled, and how to run reliable, repeatable workflows. The two areas demanding immediate attention are Agent Understanding — where missing machine-readable errors, unclear operation semantics, and absent agent instructions leave AI agents guessing — and Agent Usability, where undocumented idempotency, rate-limit signaling, and pagination force partners to reverse-engineer critical reliability behaviors. Fixing these gaps will unlock partner self-service and enable AI agents to integrate correctly without human intervention.