RXed AI News

AI to the bone.
LatestMethodologyUpcoming & requests
SCORE 7/10 10/10 criteria · Strong Assessed 2026-08-30 · ARI rubric v1.0

Docusign — can an agent use it?

Visit docusign.com
“The #1 e-signature and Intelligent Agreement Management platform, trusted by 1.7M customers. eSignature, CLM, Agreement Manager, Workflow Builder, and AI-powered Agents for drafting, reviewing, and orchestrating agreements. Plans from €9/mo (Personal) to Enterprise. Developer API tiers from $600/yr (Starter) to custom Enterprise.” — the vendor’s own words

Docusign is strongly agent-ready thanks to an official MCP server (open beta) covering envelope creation, status checking, and workflow automation, plus a comprehensive REST API surface across eSignature, CLM, and Agreement Manager. OAuth 2.0, self-serve sandbox, and SDKs in 7 languages lower the integration barrier. The main gaps: no agent payment protocol support, mediocre recent uptime (91% over 30 days), and a ToS that technically prohibits 'robots' while simultaneously marketing an official MCP server to AI agents. Adding an llms.txt and adopting any agent payment protocol would move the score.

Service
www.docusign.com
Category
E-signature
Agent protocol
Official
Agent payment rails
None published
Site Scan
C (74/100) · crawl-level, 30/08

FIND & RETRIEVE · 7.2

Sf7
Machine-readable surface
Iq6.5
Information retrieval quality
Dx8
Documentation for machines

ACT & TRANSACT · 6.5

Ac8.5
Action coverage
Pt8.5
Agent protocol support
Au7.5
Access & auth friction
Py2
Agent payment capability
Cf6
Cost & rate fairness

TRUST & DURABILITY · 6.2

Ts6.5
Permission & ToS stance
Rl6
Reliability & continuity
Tap or hover any criterion to see why it scored that.
FIND & RETRIEVE7.2/10Can an agent get correct information?

Machine-readable surface7/10

Sitemap index present and referenced in robots.txt (multi-locale, blog + main + PDF sitemaps but no lastmod). Schema.org JSON-LD (Organization, WebSite, ContactPoint) on the homepage. 2,035 words of real text in raw HTML visible without JS. No llms.txt, no markdown negotiation, no .well-known/mcp.json. Robots.txt has no AI-specific rules (neither blocks nor welcomes AI crawlers — policy is accidental). AI crawlers (GPTBot, ClaudeBot) receive HTTP 200. source

Information retrieval quality6.5/10

eSignature pricing is public and specific across three retail tiers (€9/€23/€38 per user/mo annual) plus Advanced plans requiring sales contact. Feature comparison matrix published. Developer API pricing is harder to find: $600–$5,760/yr across four tiers (Starter, Intermediate, Advanced, Enterprise), documented in third-party sources but not prominently on the main site. Enterprise and IAM pricing is 'contact sales.' No Offer/Product schema markup on pricing pages. source

Documentation for machines8/10

developers.docusign.com provides REST API reference (v2.1), OAuth 2.0 guides (Authorization Code, JWT, Implicit Grant), SDKs in 7 languages (Java, .NET, Python, Node, PHP, C++, Ruby), upgrade guide from v2.0 to v2.1, and a developer changelog tracking all API changes. Rate limits documented (1,000 calls/min per org, burst to 5,000; envelope quotas per plan). Error codes and status responses are structured. However, the docs site is built with Gatsby and requires JS to render — a non-browser agent cannot read the docs directly. source

ACT & TRANSACT6.5/10Can an agent do the job?

Action coverage8.5/10

The eSignature REST API v2.1 covers the full lifecycle: create envelopes (from scratch or templates), send for signature, embed signing ceremonies, check status, download signed documents, void/correct envelopes, bulk send (up to 100 recipients), and manage recipients. CLM API automates contract lifecycle. Agreement Manager API provides search and retrieval of agreement data. Admin API for account management. Connect (webhooks) for real-time notifications. Sandbox mirrors production for testing. The core action — sending a document for signature and tracking it — is fully API-accessible. source

Agent protocol support8.5/10

Official Docusign MCP server in open beta (announced Momentum 2026). Covers core eSignature actions: create and send envelopes, check envelope status, bulk actions (resend, correct, void), and workflow automation. Available as a Claude connector, and compatible with Gemini, Microsoft Copilot, GitHub Copilot, and any MCP-capable client. OAuth-based security with the same access controls as direct API calls. Agreement Manager via MCP is currently read-only. Maintained by Docusign, not community. source

Access & auth friction7.5/10

OAuth 2.0 with three grant types (Authorization Code, Implicit, JWT). Free developer sandbox available with 25 envelopes/quarter — self-serve signup, no sales call required. SDKs handle OAuth flows in 7 languages. Scoped permissions per integration. Legacy basic auth (X-Docusign-Authentication header) being deprecated with a deadline of September 30, 2026. Production API access requires a paid plan (minimum $600/yr Starter or Business Pro eSignature plan). MCP server uses the same OAuth flows. source

Agent payment capability2/10

Docusign is a service agents pay for via subscription billing — no programmatic agent payment path exists. No evidence of ACP, AP2, MPP, or x402 support. An agent can create and send envelopes via API, but paying for the Docusign subscription itself requires a standard web checkout or enterprise contract. The MCP server does not expose any payment or billing actions. source

Cost & rate fairness6/10

Free developer sandbox (25 envelopes/quarter) for testing. Production API starts at $600/yr (Starter, ~40 envelopes/mo) scaling to $5,760/yr (Advanced). Rate limits are documented: 1,000 calls/min per org with burst to 5,000, and Enterprise can negotiate higher. Per-envelope costs range from $1.50–25 depending on contract and features. No agent-specific price discrimination detected. However, the minimum $600/yr floor and metered envelope model mean cost is not trivial for high-volume agent use cases. source

TRUST & DURABILITY6.2/10Will it still work next quarter?

Permission & ToS stance6.5/10

Contradiction between legal text and engineering stance. Developer Terms prohibit 'robots, spiders, scrapers' from accessing Docusign products beyond what is allowed, and the Sites & Services Terms prohibit 'screen scraping, database scraping.' But Docusign simultaneously publishes an official MCP server, comprehensive developer APIs, OAuth flows, and partner connectors for AI agents (Claude, Gemini, Copilot) — actively marketing agentic use at Momentum 2026. The anti-scraping clause targets unauthorized data extraction, not legitimate API/MCP use. No hostile enforcement history against legitimate API consumers. source

Reliability & continuity6/10

Status page at status.docusign.com tracks 48 components across 8 groups (PROD, EU11, AU, NA11, NA21, JP1, FedRAMP, Akamai GTM). However, 30-day uptime measured at 91.34% with 14 incidents in that window, and 29 incidents in 90 days (3 major, 26 minor, median resolution 1h40m) — below enterprise SaaS norms. API versioning is conservative: v2.0 entered maintenance in Feb 2022 but remains functional; v2.1 has been stable since introduction with regular sub-version releases. Deprecation timelines are generous (legacy auth deadline extended to Sept 2026). SDK changelogs are active. source

Sources

Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.

RELATED ON RXED
AI AUDIT Docebo — audited 5.6/10 The most transparent AI stack we have scored in this category, with every model provider named, three vendor guardrail layers switched on an AI AUDIT HeyGen — audited 6.1/10 The most complete avatar-video stack for small teams — real API, MCP and consent guardrails — as long as you budget for the credit meter, no AI AUDIT OpenAI AgentKit — audited 5.8/10 Eight months from launch to deprecation notice. Agent Builder and the Evals platform both shut down on 30/11/2026, the export is lossy by Op