# Alloy — API Agent Score

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

Alloy scored 70/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 92/100 (A+)
- Developer Experience: 59/100 (D)
- Agent Discovery: 88/100 (A)
- Agent Understanding: 70/100 (B)
- Agent Usability: 49/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — authentication documented in the docs site at https://developer.alloy.com/public/docs/account-level-api-keys. Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Schema coverage & depth — Only 0% of operations have documented schemas. Investigated: spec 83%, sdk 0%.
- [warn] Machine-readable, versioned contract — info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 80%, docs 60%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — Code samples present on 2/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, spec 0%, sdk 0%.

### Developer Experience

- [pass] Code samples in docs — Code samples present on 2/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Description completeness — 50% description completeness. Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 87 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms.txt found at https://developer.alloy.com/llms.txt. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (grafana/alloy, 5319 snippets). Investigated: docs 100%, sdk 100%, mcp 100%, cli 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — error codes documented in the docs site at https://developer.alloy.com/public/docs/_errors. Investigated: docs 100%, spec 50%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Docs structured data — JSON-LD Article markup on 16/16 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [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%.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — sandbox documented in the docs site at https://developer.alloy.com/public/docs/sandbox-vs-production. Investigated: spec 100%, docs 100%.
- [warn] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 33%, docs 33%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 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

Alloy's API program stands out for its machine-readable contract and schema quality, giving partners and agents a solid foundation to build against. However, two areas put partner adoption at risk: agents and coding assistants lack the operational context (clear operation semantics, idempotency, rate-limit signaling, and an AGENTS.md) to integrate reliably without guessing, and partners have no self-serve path — no developer portal, no quickstart, and no runnable collection — to go from discovery to a working call without a sales conversation. Closing these gaps should be the immediate priority to unlock self-serve partner growth and safe, autonomous agent workflows.