# Dropbox Sign — API Agent Score

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

Dropbox Sign scored 74/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

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

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="1.0.0") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://developers.hellosign.com/docs/guides/o-auth/overview. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 94% of operations have documented schemas (target 95%+). Investigated: spec 67%, sdk 64%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — Code samples in 4 language(s) across docs (top: shell, csharp, java); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 50%, spec 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://developers.hellosign.com/api/api-quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 4 language(s) across docs (top: shell, csharp, java); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Description completeness — 95% of operations + parameters have substantive descriptions. Investigated: spec 100%, sdk 25%.
- [pass] Changelog published — changelog documented in the docs site at https://developers.hellosign.com/changelog. Investigated: spec 100%, docs 100%, sdk 100%.
- [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%.

### 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 — llms.txt covers 0/45 sitemap doc pages (0%); 45 missing; 8 nested indexes omitted (150 sitemap pages excluded); 985 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap). Investigated: docs 88%, sdk 0%.
- [warn] Registry & SDK presence — 3/4 registry-metadata components present; missing: keywords. Investigated: sdk 92%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 96% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 29 of 50 pages have substantive content differences between markdown and HTML (avg 42% missing). Investigated: docs 60%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 8% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Sandbox separation — Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [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] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Dropboxsign's API program shows real strength in API design and discovery, giving partners a solid foundation to find and evaluate your APIs. However, two areas are holding back partner program outcomes: agents and AI coding tools cannot reliably understand or act on your API without guessing (missing machine-readable context, structured docs, and idempotency/rate-limit guidance), and partners cannot validate integrations against runnable, tested workflows before going live. Prioritize closing the agent-readability and operational-reliability gaps first, then sharpen the self-service onboarding surface to compress the time from first look to first successful call.