Docusign CLI Docs Agreement CLI Developer Center

The Anatomy of a Trustworthy Agreement Layer

Four capabilities that turn agreements from documents into infrastructure agents can act on · Bengaluru Meetup Workshop · Docusign IAM

Capability 1 of 4 · Data

What does the agent actually know?

The gap every agentic platform hits The agent reasons well until the generic ends and the agreement begins. Without the actual terms, it applies generic actions to specifically negotiated relationships. Stage 1 and 2 close that gap for Fontara's procurement team.

Define procurement agreement types and fields as code, bulk-ingest a pharma-medtech vendor repository with the Docusign CLI, and watch Iris extract renewal dates, payment terms, and liability caps from every PDF.

Capability 2 of 4 · Integration

Where does the agent plug in?

The integration pattern that travels Structured data is inert if it's siloed. The MCP connection you build in Stage 3 is the same pattern that reaches Copilot Studio, Teams, or whatever your customers are already running.

Wire the Docusign MCP Server into Copilot Studio and query Fontara's entire vendor corpus in plain English: auto-renewals in 90 days, vendors on off-standard payment terms, MSAs missing a price-increase cap.

Capability 3 of 4 · Guardrails

Who decides what runs without a human?

Agentic action without guardrails is liability Not every agreement decision should fire automatically. Workflow Builder lets you encode exactly which renewals require sign-off before signature — so the agent escalates with full context instead of acting blind.

Trigger a pharma supply renewal from one prompt: the agent calculates the deal, routes it through Workflow Builder approval, fires Agreement Prep to the vendor signer, and tracks status back — all without a human touching the toolchain.

Capability 4 of 4 · Reach

Where does the result go?

The reusable asset you hand to every client What you build today is version-controlled, CLI-deployable, and portable across customer accounts. The MCP endpoint it exposes is reachable from Teams, Copilot, or any AI surface your customers are already running.

Deploy the prebuilt Procurement Agent in Agent Studio: it surfaces renewals, off-standard terms, and obligations across the vendor corpus, and reaches the teams that act on them through any MCP-compatible AI client.

The pattern · ingest once → extract with AI → expose via MCP → deploy agents everywhere

Docusign CLIDefines agreement types as code and bulk-ingests a legacy repository at scale — the foundation everything else runs on.
Iris AI extractionTurns flat PDFs into structured, queryable intelligence: parties, dates, payment terms, liability caps, clauses.
Docusign MCP + Copilot StudioExposes that intelligence to any AI client in plain English, with Workflow Builder routing high-stakes decisions to a human first.
Agent StudioShips the whole stack as a Procurement Agent that reaches teams through Teams, Copilot, or any MCP-compatible surface.

Session references

Lab

Hands-on Lab

Step-by-step: AI extraction → MCP via Copilot Studio → Agent Studio, with copy-paste prompts.

Open lab →
For questions or feedback: amrit.prakash@docusign.com