DOCUMENT INFRASTRUCTURE FOR AI AGENTS

Your agent just shipped a contract. Now prove it held up.

One tool call to render, sign with PAdES-grade cryptography, and return a public verify URL that survives an audit. The same primitive in reverse — POST a PDF the agent received, get back structured JSON your agent can prove it actually read. The MCP server puts all 59 tools in your agent's hands.

WHAT YOU SHIP

A sealed PDF. A public verify URL. Nothing else to wire up.

THE PDF
acme.kamy.dev/invoices/INV-0042.pdf
Sample invoice rendered by KamyInvoice#INV-0042BILL TOAcme Robotics Inc.120 Mission StreetSan Francisco · CA 94105ISSUEDMay 15, 2026DUE June 14, 2026API renders — May25,000$49.00E-signatures — May47$8.14Webhook deliveries12,308incl.TOTAL DUE$57.14PAdES B-LT · SEALEDkamy.dev/verify/0x9a3f…b21c
THE VERIFY REPORT
kamy.dev/verify/0x9a3f4dc8b21c
Sample public verify report on kamy.devSignature verifiedPAdES B-LT seal · cert chain reaches a trusted rootDOCUMENT HASH9a3f4dc8b21c…e7SIGNED ATMay 15, 2026 · 14:22 UTCSIGNER[email protected]CERT CHAINAcme Root → Intermediate → SignerTSA TIMESTAMPDigiCert TSA · RFC 3161ARCHIVEPDF/A-3b · stored ✓

Works with the stack you already use

AnthropicCursorOpenAIVercelSupabaseStripeTwilioResendLinearGitHubFly.ioCloudflare
DEMO · ONE API CALL

DEMO

Three lines.
One signed PDF.
Verifiable forever.

One API call returns the PDF, the hash, and a verify URL your customers can hit without an account. The cryptography does the trusting — no portal, no take our word for it.

live · runs against production
// What your agent calls
await kamy.documents.signAndVerify({
  template: "nda",
  data: { signer: "[email protected]", terms },
});

// What you get back
{
  documentId: "doc_abc123",
  verifyUrl: "https://kamy.dev/verify/abc123",
  padesSealed: true,
}
live · runs against production
// What your agent calls
await kamy.documents.extract({
  template: "invoice",
  source: { url: "https://vendor.com/inv-042.pdf" },
});

// What you get back
{
  id: "8f3a...",
  extraction: { invoice_number: "INV-042", total: { amount: 1234.56, currency: "USD" }, ... },
  verifyUrl: "https://kamy.dev/extract/8f3a...",
  sourceSha256: "abc...",
  extractionSha256: "def...",
}

INGEST — DEMO

Or in reverse.
POST a PDF.
Get verifiable JSON.

When the agent has to read the document instead of producing it. Five templates, structured output, and a verify URL anyone can re-check against the source.

THE PIPELINE

One API call. Every step audited.

From the SDK call to the public verify URL — each stage emits a webhook, persists to S3, and lands a cryptographic seal that an auditor can replay six years later.

Kamy render pipeline: code → API → render → sign → archive → verify URLFIG. 01 · KAMY RENDER PIPELINESCALE 1:1 · SHEET 1 OF 2YOUR CODEPOST /v1/render01API GATEWAYauth · scope02RENDERHandlebars · Chromium03SIGNPAdES B-LT04ARCHIVEPDF/A · S305VERIFY URLpublic, forever06tamper-evident from here onno portal, no account
CONSOLIDATION

CONSOLIDATION

Stop stitching five vendors for one document workflow.

TODAY

  • 1.PDF rendering — DocRaptor / PDFShift API
  • 2.E-signature — DocuSign / Dropbox Sign API
  • 3.Cryptographic seal — DIY OpenSSL + cert chain
  • 4.PDF extraction — Reducto / LlamaParse / Mistral OCR
  • 5.Verifiable extraction — nobody — until now
  • 6.Public verify — host your own /verify page
  • 7.Agent tooling — build your own MCP server
  • 8.Audit evidence — Vanta / homegrown trail

6 vendors · 6 contracts · 6 audit boundaries · 6 places it can break

WITH KAMY

  • 1.Kamy — One MCP server · Render · Sign · Extract · Verify (both ways) · Audit trail · Free tier

1 vendor · 1 API · 1 audit boundary · cryptographically provable

Triggered from your code, a Vercel cron, a hosted form, a webhook, or an MCP-connected agent. Same API, same audit trail.

Built on PAdES B-LT. PDF/A conformance gated in CI. Public verify page anyone can use.

USE CASES

USE CASES

Built for the things AI software actually does.

AI AGENTS — THE WEDGE

Give your agent commitments that hold up.

Your agent issued a refund, signed a contract, approved a release. One MCP tool call returns a tamper-evident PAdES-sealed PDF and a public verify URL. When the customer disputes, when the auditor asks, when the regulator knocks — you have cryptographic evidence, not log files.

Wire in 30 seconds. The MCP server at mcp.kamy.dev exposes 59 tools — render and convert, e-signature and PAdES sealing, document extraction, and a signed provenance ledger — to Claude, ChatGPT Apps, or Cursor.

AGENT-DRIVEN OPS

Your agent runs invoicing. Your agent files the contract.

Once one agent can ship a contract, the rest of your back office turns into agent surface area. Monthly invoices, quarterly statements, contract renewals — your agent calls one tool, the recipient gets a sealed PDF with a verify URL, and the audit trail builds itself.

Cron-driven and event-driven renders both flow through the same tool surface — no agent retraining when the trigger changes.

COMPLIANCE-GRADE OUTPUTS

Documents that survive an audit by default.

Fintech, healthtech, regtech — when your agent produces a customer-facing PDF, it needs to pass legal review without a post-processor. PDF/A archival, PAdES B-LT signatures, hash anchoring on the public verify URL, and a downloadable audit certificate per document.

Replaces your homegrown PDF stack + DocuSign API + the Vanta evidence collector.

EMBEDDED IN YOUR PRODUCT

Ship your customers' agents the same surface.

Building a vertical AI product? Your customers' agents need documents too. White-label brand kits, customer-owned audit trails, per-tenant API keys. The same MCP server your team uses, embeddable in your product.

Stripe-shaped pricing. Stripe-shaped docs. No revenue share, no per-signer fees.

INGEST — DOCUMENTS COMING IN

Your agent reads a vendor PDF. Now you can prove what it read.

Inbound invoices, claim forms, government documents, supplier contracts. Your agent extracts the fields with Claude vision, your downstream system acts on the JSON, and the vendor disputes it six weeks later. Today: nobody can replay the extraction. Tomorrow: every Kamy Ingest call returns a public verify URL anchored to a SHA-256 of the source and the canonical extraction, bound by an Ed25519 signature. The disagreement becomes a fact question instead of a model-replay argument.

Five templates ship in v0 — invoice, receipt, contract, ID document, generic form. POST a PDF, get JSON + a verify URL recipients can re-check offline with our public key.

VERIFICATION

THE PART NOBODY ELSE DOES

Drag a signed PDF here. We re-hash it, walk the cert chain, verify the timestamp, and show you the audit trail.

No upload, no account — runs in your browser. Every Kamy-signed document carries this verification capability for the life of the document. Recipients don't need to trust you. The cryptography does.

Trust ladder: signature bytes → cert chain → TSA timestamp → hash anchor → verify URLFIG. 02TRUST LADDERTOP — VISIBLEBASE — BYTES05VERIFY URLpublic, no auth — recipient pastes the URLanyone can validate04HASH ANCHORSHA-256 of the signed PDFtamper-evident03TSA TIMESTAMPRFC 3161 — third-party time proofwhen, by whom02CERT CHAINX.509 path to a trusted rootidentity01SIGNATURE BYTESPKCS#7 inside the PDF (PAdES B-LT)the seal
INSTALL

INSTALL

Pick your runtime. Ship in 10 minutes.

Node / TypeScript

npm install @kamydev/sdk

Python

pip install kamy

MCP (Claude Code, Cursor, agents)

claude mcp add --transport http kamy https://mcp.kamy.dev/mcp

CLI

npm install -g @kamydev/cli

Also available: REST API, OpenAPI spec, Go SDK, Ruby SDK. SDKs are open-source on GitHub.

PRICING

PRICING

Transparent. Metered. Cheap until you're not.

Pay for what you use. No per-call markup. No surprise overages. No “contact sales” walls — every tier is metered transparently and Scale runs pure pay-as-you-go.

Free

Wire to your agent today. No credit card.

$0forever
  • 100 watermark-free renders / month
  • 10 e-signatures / month
  • 50 Ingest extractions / month
  • MCP server — wire to ChatGPT, Claude, Cursor
  • PAdES B-LT signing
  • Public verify URL on every signed doc and extraction
Start free

MOST POPULAR

Pro

Production workloads for solo devs and small teams.

$49/ month
  • 25,000 renders / month
  • Watermark-free on every render
  • 10 e-signatures / month included
  • Then $0.22 per signature
  • Brand kits + custom fonts
  • Webhooks
  • Email support
Start Pro

Scale

No monthly minimum. Pure metered pricing for variable workloads.

Pay as you go
  • No monthly minimum
  • Per-render metered pricing
  • 10 e-signatures / month included
  • Watermark-free on every render
  • Volume discounts auto-applied
  • Same API, same SLAs as Pro
Start Scale

HOW METERING WORKS

  • One render, one sign, one edit = one document. Verify calls are free, forever.
  • Above your tier's allowance, every additional render is metered transparently. No surprise overages, no $1,400 surprise bills, no contracts to negotiate.
  • Signatures with TSA timestamping are billed at the same rate — no PAdES surcharge, no per-signer fee.
  • Need higher volume than the published tiers? Drop us a note — we'll quote you a transparent per-render price. No sales motion.
See full tier comparison (Starter · Pro · Business · Scale)

Generate, sign, prove.
One API.

Free tier. No credit card. Ten minutes to your first signed, verifiable PDF.

Kamy — Document infrastructure for AI agents.