# Sendcloud — API Agent Score

> Score: 78/100 (Grade: B) | Domain: sendcloud.com | Rubric: 1.0.0 | Checked: November 4, 2026

Sendcloud scored 78/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 93/100 (A+)
- Developer Experience: 74/100 (B)
- Agent Discovery: 99/100 (A+)
- Agent Understanding: 90/100 (A+)
- Agent Usability: 48/100 (F)

## 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] 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%, wellknown 0%.
- [warn] Schema coverage & depth — Only 83% of the 6 operations document both request and response schemas (target 95%+), so an agent can't reliably call the rest. Investigated: spec 69%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — Only 47% of parameters and responses (9 of 19) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, docs 0%, sdk 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup available at https://account.sendcloud.com/signup/?_gl=1*5g7jxx*_gcl_au*MzgwMTE5MTQ5LjE3ODY1Mzg0NzY.*FPAU*MzgwMTE5MTQ5LjE3ODY1Mzg0NzY.*_ga*NTEzMjUyMzMyLjE3ODY1Mzg0NzY.*_ga_G20N49N1GG*czE3ODY1Mzg0NzYkbzEkZzAkdDE3ODY1Mzg0NzYkajYwJGwwJGgxNjM1OTY4Mzk0*_fplc*YnprQ2FaRDNsNEF0WnVLeXpGUGNXWDM1QkhrUzlzdFE5Wnh5UWM0SFdKd21IRzVndUUzcTZ6SWFrVCUyRml1QzAzRG95dUMlMkJkTU8lMkJqWWYya0M1OHA1akZPTU84WWVWMFdPSlNJRER6U3JOd1ptUVRic1VtRjdociUyQlBwams1NkElM0QlM0Q.*_ga_TBXEGHJ1GL*czE3ODY1Mzg0NzYkbzEkZzAkdDE3ODY1Mzg0NzYkajYwJGwwJGgw&ajs_aid=44c439a1-0a1a-4dd5-baab-6e4cd564f2bf, with a free tier or sandbox documented — an agent can onboard without contacting sales. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://sendcloud.dev/docs/getting-started/api-version-guide includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations and parameters carry substantive descriptions (12 of 12 ops, 3 of 3 params), the main semantic cue an agent relies on. Investigated: spec 100%.
- [fail] Code samples in docs — No code samples detected across 20 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] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — Same-origin links point to HTML and no markdown alternatives detected. Investigated: docs 95%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/sendcloud_dev, 604 snippets). Investigated: docs 100%, sdk 88%, 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) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations (6 of 6) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 3 of 50 sampled pages convert to over 100K chars (max 814K HTML → 282K markdown (85% boilerplate)). Investigated: docs 99%.
- [pass] Docs structured data — Machine-readable JSON-LD Article markup on 20 of 20 assessed pages (100%), with dateModified present. 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] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 3% (threshold 35% for full credit).

### Agent Usability

- [pass] Pagination documented & consistent — Pagination parameters are present on the 2 list endpoint(s), so an agent can page through results. Investigated: docs 100%, spec 88%.
- [warn] Runnable collection with test scripts — No test scripts found in the workspace's public collections, so an agent can't use them to verify API behavior. Investigated: platform 50%, sdk 0%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 3) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [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%.
- [fail] Sandbox separation — None of the 1 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.

## Executive Summary

Sendcloud's API program shows real strength in documentation quality, schema design, and agent discoverability — partners and their agents can find and read the surface reliably. The two areas that need urgent attention are safe integration and operational reliability: there is no sandbox environment, no idempotency guidance, and no rate-limit signaling, meaning any agent-driven automation runs directly against production with no guardrails against duplicates or throttling. Fixing these gaps — alongside adding a changelog and code samples — will give partners the confidence to automate shipping workflows without fear of costly mistakes.