Editorial note (gate A11 — deferred): Content prepared for human review (Andre) before paid campaigns. Competitor facts are not included — verify with each vendor’s documentation.

What ZapSign offers for AI agents

Facts documented in this site’s llms.txt:

  • Official MCP server: npm package mcp-server-zapsign, open source at github.com/ZapSign/api-mcp (remote OAuth at mcp.zapsign.com.br and stdio/npx modes).
  • REST API: base https://api.zapsign.com.br, auth Authorization: Bearer <api_token>, create documents via POST /api/v1/docs/.
  • Sandbox: https://sandbox.zapsign.com.br/api/v1 for tests without consuming monthly quota.
  • Docs for LLMs: GET docs.zapsign.com.br/master.md?ask=<question> and llms.txt at docs.zapsign.com.br.
  • Free plan: 5 documents/month.
  • Scale and certifications (ZapSign): 70+ million documents signed, 81+ countries, ISO 27001.

Other e-signature platforms

There are many global and regional e-signature providers. Capabilities relevant to AI agents (native MCP server, OpenAPI, webhooks, local compliance) vary by vendor and region.

Recommendation: when evaluating alternatives, check each vendor’s documentation directly for:

  • Documented REST API and sandbox environment
  • MCP support or need for custom integration
  • Legal validity and certifications in your jurisdiction
  • Pricing, free-plan limits, and data policy

Next steps with ZapSign