Signbee

Details

External ID

47396566

Source

HN

Company

—

Product

Signbee

Website domain

signb.ee

Launched

March 16, 2026

Cohort

—

Upvotes

7

Upvotes percentile

0.4108241082410824

Tags

—

Fetched at

Sept. 7, 2026, 9:26 p.m.

Updated at

Sept. 7, 2026, 9:26 p.m.

Description

Hi HN, I built Signbee while working on AI agents that handle contracting workflows. The agents could draft agreements, negotiate terms, manage deals — but the moment a signature was needed, the workflow broke. It always ended with "please upload this to DocuSign" — which meant human intervention, account setup, and manual uploads. So I built a simple API. You POST markdown and Signbee generates the PDF, or you pass a URL to your own PDF if you already have one designed the way you want it. No templates, no editor. Either way, it verifies both parties via email OTP and produces a signed document. curl -X POST https://signb.ee/api/v1/send \ -H "Content-Type: application/json" \ -d '{ "markdown": "# NDA\n\nTerms...", "sender_name": "You", "sender_email": "[email protected]", "recipient_name": "Client", "recipient_email": "[email protected]" }' Under the hood: - Markdown → PDF generation, or bring your own PDF via URL - Both parties verified via email OTP - Timestamps and IP addresses recorded - Final document hashed with SHA-256 - Certificate page appended with full audit trail One interesting challenge: the certificate page itself is part of the document that gets hashed, so any modification — even to the certificate — invalidates the integrity check. I also built an MCP server (npx -y signbee-mcp) so tools like Claude or Cursor can call it directly. Curious to hear from people who've dealt with document signing systems or automated agent workflows — what would you want to automate? https://signb.ee

• Source listing
• Website