How does signing work without DocuSign?

Signbee generates a PDF from your markdown (or uses your own PDF), then handles the entire signing ceremony: sender verifies via OTP or API key, recipient gets an email with a signing link, and both parties choose a signature style. The final PDF includes a tamper-proof SHA-256 signing certificate with both signatures, timestamps, and IP addresses.

Is an API key required?

No. Without an API key, the sender simply verifies their email via a one-time code. With an API key, the sender is pre-verified and the recipient receives the signing link immediately — zero friction for your agent.

Can I use my own PDF instead of markdown?

Yes. Pass a pdf_url field in your request and Signbee will use your existing PDF directly. The signing flow, certificate, and email delivery work exactly the same way.

Is this legally binding?

Electronic signatures are legally recognised under the UK Electronic Communications Act 2000, the US ESIGN Act, and the EU eIDAS Regulation. Every Signbee document includes a SHA-256 hash, timestamps, and IP addresses for auditability.

What happens when both parties sign?

Both parties receive an email with the final signed PDF attached. The document includes a signing certificate page with both signatures, their timestamps, IP addresses, and a SHA-256 integrity hash.

What counts as a document on the free plan?

Each call to /api/v1/send that creates a new document counts as one. The free plan includes 5 per month — no credit card required.

How do I connect Signbee to Claude, Cursor, or Windsurf?

Install the Signbee MCP server by adding it to your MCP client configuration: npx -y signbee-mcp with your SIGNBEE_API_KEY environment variable. The agent then gets send_document and send_document_pdf tools automatically. Works with Claude Desktop, Cursor, Windsurf, and Hermes Agent.

What is an MCP server and why does Signbee have one?

MCP (Model Context Protocol) is Anthropic's standard for connecting AI agents to external tools. Signbee's MCP server wraps the signing API so any MCP-compatible agent can send documents for e-signing via natural language commands — no manual API calls needed.

How is Signbee different from DocuSign?

DocuSign is a visual template builder designed for humans. Signbee is an API-first signing primitive designed for developers and AI agents. You send markdown or a PDF URL, Signbee handles the entire signing ceremony and returns a SHA-256 certified signed PDF. No UI, no templates, no per-seat pricing.

How much does DocuSeal cost?

Free to self-host (open-source). Cloud API requires Pro plan at $20/month plus $0.20 per completed document. Free sandbox for testing.

Comparison

DocuSeal vs Signbee

DocuSeal is open-source and self-hostable. Signbee is the simplest API. Here’s how they compare.

Quick comparison

	DocuSeal	Signbee
Best for	Teams that need full control over document data and want to self-host their signing infrastructure for compliance or sovereignty reasons	Simplest API for developers + AI agents
Pricing	Free to self-host (open-source)	Free — 5 docs/month
Time to first doc	Minutes to hours	Under 60 seconds
Document input	Templates / PDF upload	Markdown or PDF URL
Auth	OAuth / API key	API key or none (OTP)
AI agent support	MCP server	MCP + Agent Skill + llms.txt

What is DocuSeal?

DocuSeal is an open-source document signing platform. You can self-host it on your own infrastructure or use their cloud version. Templates are created from PDFs using a visual editor, then the API sends documents based on those templates.

Best for: Teams that need full control over document data and want to self-host their signing infrastructure for compliance or sovereignty reasons.

→ docuseal.com

What is Signbee?

Signbee is an API-first document signing service built for developers and AI agents. You POST markdown or a PDF URL, specify sender and recipient, and Signbee handles everything: PDF generation, email verification, signature capture, and SHA-256 certificate delivery. One API call, no templates, no SDK.

Best for: Developers who want the shortest path from code to signed document, and AI agents that need to send contracts autonomously.

→ signb.ee

Where DocuSeal wins

Open-source — full visibility into the codebase
Self-hosting option for data sovereignty
MCP server available for AI agent integration
Template-based workflow for repeatable documents
Active development community

Where Signbee wins

One API call — No templates, no SDK, no webhook setup
Markdown documents — Write the contract in text, Signbee generates the PDF
No account required — Sender verifies via email OTP
AI-native — MCP server, Agent Skill, llms.txt
Free tier with real documents — 5 docs/month, no credit card
SHA-256 certificate — Tamper-proof audit trail on every document

DocuSeal limitations

Requires template setup before sending via API
Self-hosting means managing your own infrastructure
Per-document pricing on top of monthly subscription
More complex setup than cloud-only alternatives

Signbee limitations

Two-party signing only (no multi-signer routing)
No visual template builder (markdown or PDF URL only)
No field placement (no drag-and-drop signature boxes)
Smaller free tier than some competitors

The verdict

Choose DocuSeal if you need to self-host your signing infrastructure. Choose Signbee if you want the simplest possible API — one call, no templates, no infrastructure to manage.

Try Signbee — free, no credit card.

Read the docs Get started free