h receive the final document with a SHA-256 signing certificate — timestamps, IP addresses, and a tamper-proof integrity hash.

Three ways to connect: • REST API — just HTTP + JSON, no SDK needed • MCP Server — works with Claude Desktop, Cursor, Windsurf (npm: signbee-mcp) • Direct curl — no account needed, sender verifies via email OTP

Why it exists: I was building AI agent workflows that could draft contracts, negotiate terms, and manage deals — but every flow broke at the signature step. DocuSign's API requires OAuth, templates, and multi-step envelope configuration. An autonomous agent needs none of that. So I built Signbee: markdown in, signed PDF out.

Legally binding under the UK Electronic Communications Act 2000, US ESIGN Act, and EU eIDAS Regulation. Free tier: 5 documents/month, no credit card required.

🔗 signb.ee

20:T5d0,

Signbee is a document signing API built specifically for AI agents. Traditional e-signature tools like DocuSign were designed for human workflows — templates, OAuth, envelope management, webhooks. Signbee strips all of that away.

One API call. Your agent sends markdown (or a PDF URL) along with sender and recipient details. Signbee generates the PDF, emails the recipient a signing link, and handles the entire ceremony. Both parties sign, both receive the final document with a SHA-256 signing certificate — timestamps, IP addresses, and a tamper-proof integrity hash.

Three ways to connect: • REST API — just HTTP + JSON, no SDK needed • MCP Server — works with Claude Desktop, Cursor, Windsurf (npm: signbee-mcp) • Direct curl — no account needed, sender verifies via email OTP

Why it exists: I was building AI agent workflows that could draft contracts, negotiate terms, and manage deals — but every flow broke at t

Signbee

About