Question 1

How does signing work without DocuSign?

Accepted Answer

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.

Question 2

Is an API key required?

Accepted Answer

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.

Question 3

Can I use my own PDF instead of markdown?

Accepted Answer

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.

Question 4

Is this legally binding?

Accepted Answer

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.

Question 5

What happens when both parties sign?

Accepted Answer

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.

Question 6

What counts as a document on the free plan?

Accepted Answer

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.

Blog

How AI Agents Can Send Documents for Signature

Building a Signature That Feels Alive