# Segment — API Agent Score

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

Segment scored 73/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 99/100 (A+)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 46/100 (F)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 12/13 (92%) spec-enum params are realized as constrained types (not bare strings). Investigated: sdk 99%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://app.segment.com/signup; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.twilio.com/en-us/errors/404 with a runnable first-call sample. Investigated: docs 100%.
- [warn] Description completeness — 19/20 operations carry a description. Investigated: sdk 95%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Content negotiation partially supported: 10 correct type, 0 wrong type, 40 HTML only. Investigated: docs 88%.
- [warn] Registry & SDK presence — 3/4 registry-metadata components present; missing: keywords. Investigated: sdk 92%, cli 50%, docs 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 774/4794 sitemap doc pages (16%); 4020 missing; 963 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap). Investigated: docs 56%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 100% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 10 of 50 pages have substantive content differences between markdown and HTML (avg 9% missing). Investigated: docs 60%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Segment's API program shows strong fundamentals in design, discovery, and developer experience — partners can find and evaluate the APIs without friction. The two areas that need urgent attention are agent understanding and runnable usability: errors are not machine-readable so AI agents cannot self-recover from failures, there is no agent instructions file to guide automated consumers, and the absence of a runnable collection with test scripts means partners and their agents have no authoritative, executable reference to build against confidently. Closing these gaps will unlock self-serve partner integration at scale and make Segment's APIs genuinely agent-ready.