Kamy

Kamy — the document layer for AI-native software

Tagline: Generate, sign, prove. One API.

Kamy is one developer-first MCP for the full document chain: generate, sign, edit, verify, audit. Render PDFs from templates, sign them with PAdES B-LT cryptographic signatures (own CA + RFC 3161 timestamps + embedded CRL), edit / fill / redact existing PDFs, and produce a tamper-evident audit trail anyone can verify at https://kamy.dev/verify — no Kamy account required.

Replaces the typical stitched stack of DocuSign + a PDF generation API + a homegrown audit logger with one vendor, one API, one audit boundary.

Tools exposed

Install

For Claude Code:

claude mcp add --transport http kamy https://mcp.kamy.dev/mcp
For Cursor, add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "kamy": {
      "url": "https://mcp.kamy.dev/mcp",
      "transport": "streamable-http",
      "env": {
        "KAMY_API_KEY": "<YOUR_KAMY_API_KEY>"
      }
    }
  }
}
Get a free API key at kamy.dev/dashboard/api-keys (no credit card, 100 renders/month included).

Canonical flow: generate → sign → prove
import { kamy } from "@kamydev/sdk";

// 1. Generate
const doc = await kamy.documents.render({
  template: "invoice",
  data: { invoiceNumber: "INV-001", lineItems: [...] },
});

// 2. Sign with PAdES B-LT (recipient-verifiable, audit-trailed)
const signed = await kamy.signatures.signWithPki({ renderId: doc.id });

// 3. Anyone verifies the document independently — no Kamy account
console.log(signed.verify_url);
// → https://kamy.dev/verify/<sha256>
Use cases
AI agents that produce documents. Your agent issued a refund, signed a contract, approved a release. Every action gets a tamper-evident, third-party-verifiable receipt. When the customer disputes, when the auditor asks, when the regulator knocks — you have evidence, not log files.

Compliance-grade SaaS. Your fintech / healthtech / regtech app needs PDFs that pass legal review without a separate post-processor. Render PDF/A, sign with cryptographic certs, archive with hash anchoring, retrieve on demand. SOC 2 evidence on autopilot.

Embedded document workflows. Your customers need contracts, invoices, receipts inside your product. Embed them. White-label brand kits, customer-owned audit trails, embeddable verify widgets.

What makes the verify path different
Every signed Kamy document is independently verifiable forever, by anyone, without trusting Kamy. The PAdES signature chains to a CA, the timestamp chains to FreeTSA, the audit row chains to a public hash. We're a layer; we shouldn't be a single point of trust.

Try the verify widget at https://kamy.dev/verify — drag any signed Kamy PDF in.

System templates included
invoice · receipt · quote · contract · agreement · certificate · shipping-label · report

Plus country-compliant tax variants: UAE FTA, KSA ZATCA Phase 1/2, EU VAT, US 1099-NEC.

Pricing
Tier	Price	What you get
Free	$0	100 renders / month · 10 e-signatures / month · PAdES B-LT signing · PDF/A · public verify page · MCP server
Starter	$19/mo	5,000 renders/month · watermark-free · email support
Pro	$49/mo	25,000 renders/month · country-compliant tax templates · webhooks
Business	$149/mo	100,000 renders/month · 5 seats · priority queue
Scale	$0.002/render	Pay-as-you-go · no monthly minimum · undercuts every PAYG competitor
Full tiers + metering details: kamy.dev/pricing

Links
Homepage: kamy.dev
Docs: kamy.dev/docs
Try verify: kamy.dev/verify
Pricing: kamy.dev/pricing
GitHub (plugin): github.com/Kamy-Development/kamy-plugin
NPM SDK: @kamydev/sdk
PyPI SDK: kamy-sdk
OpenAPI spec: kamy.dev/openapi.json
Agent manifest: kamy.dev/.well-known/agent.json
llms.txt: kamy.dev/llms.txt