# DocuSign — API Agent Score

> Score: 65/100 (Grade: C) | Domain: docusign.com | Rubric: 1.0.0 | Checked: July 24, 2026

DocuSign scored 65/100 (C), classified "partially-ready".

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

## Summary

- Overall: 65/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 74/100 (B)
- Developer Experience: 81/100 (A)
- Agent Discovery: 60/100 (C)
- Agent Understanding: 86/100 (A)
- Agent Usability: 42/100 (F)

## Check Results

### API Design

- [warn] Auth declared & discoverable — Authentication applied on 16/390 operations (partial coverage). Investigated: spec 98%, docs 95%, wellknown 0%.
- [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%.
- [warn] Schema coverage & depth — Only 0% of operations have documented schemas. Investigated: spec 57%, sdk 0%.
- [pass] Example coverage — 100% example coverage across params + responses. Investigated: spec 100%, sdk 0%.
- [warn] Security & governance hygiene — 1 credential-shaped string detected in spec: private-key-pem. Investigated: spec 10%, wellknown 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.docusign.com/free-trial; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Description completeness — 46% description completeness. Investigated: spec 100%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developers_docusign_platform, 1135 snippets). Investigated: docs 100%, sdk 100%, wellknown 50%, cli 0%, mcp 0%.
- [warn] Crawlable / AEO — Sitemap present (64 entries) but carries no lastmod values. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No 4xx/5xx response codes (or default error response) documented anywhere in the spec. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Agent-navigable, token-efficient docs — 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 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Runnable collection with test scripts — No test scripts found in the workspace's collections. Investigated: platform 50%.
- [warn] Pagination documented & consistent — 2 list endpoint(s) exist but no pagination params found. Investigated: docs 20%, spec 15%.
- [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] Sandbox separation — No sandbox/test server declared across 2 server entries; no test-key prefixes documented. Investigated: spec 0%, docs 0%.

## Executive Summary

DocuSign's API program shows solid foundations in contract design, authentication, and security — areas where partners and their agents can build with confidence. However, the program has critical gaps in safe integration (no sandbox separation), operational reliability (missing idempotency and rate-limit guidance), and agent discoverability (no llms.txt or agent instruction file), all of which block partners from safely automating high-stakes document workflows. Prioritize establishing a sandboxed environment and reliable operational signals first, then close the discoverability and context gaps so AI agents can find, understand, and safely operate your APIs without manual intervention.