Kamy Ingest — v0
POST a PDF.
Get structured data your agent can prove it actually read.
Every extraction comes with a public verify URL anchored to a SHA-256 of the source PDF and the canonicalised JSON, bound by a Kamy Ed25519 signature. Recipients can re-verify offline. Auditors can audit. Disputes don't become "the agent hallucinated this" arguments.
Free tier: 50 extractions / month, no credit card.
One call. Five templates. Verifiable output.
What goes in, what comes out.
Request
curl -X POST https://kamy.dev/api/v1/extract \
-H "Authorization: Bearer ${KAMY_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"template": "invoice",
"source": { "url": "https://example.com/invoice.pdf" }
}'Response
{
"id": "8f3a...",
"extraction": {
"invoice_number": "INV-2026-0042",
"vendor": { "name": "ACME Corp", "tax_id": "US-XX-..." },
"line_items": [...],
"total": { "amount": 1234.56, "currency": "USD" }
},
"verify_url": "https://kamy.dev/extract/8f3a...",
"source_sha256": "abc...",
"extraction_sha256": "def...",
"signed_at": "2026-06-10T12:00:00Z"
}v0 templates
Five schemas. Coverage for ~80% of the docs an agent reads.
invoice
Invoice
Line items, totals, due dates, payment terms.
receipt
Receipt
POS, expense, transaction receipts.
contract
Contract
Parties, key terms, governing law, signatures.
id_document
ID document
Passport, national ID, driver's licence, residence permit.
generic_form
Generic form
Fallback for any labelled form — every visible field.
Custom JSON Schemas land in v1. Pass your own template, get your own shape back.
Why the verify URL
An extraction nobody can verify is an extraction nobody should act on.
Disputes that never start
Six weeks after an agent processed an invoice, a vendor disputes the line items. The verify URL renders the source PDF and the JSON side by side. The disagreement ends.
Audit trails that survive your stack
Recipients re-verify with the public key and a 16-line script. The chain holds even if Kamy goes down — the proof is in the bytes, not the server.
Court-admissible evidence
Under E-SIGN, UETA, and eIDAS, a cryptographic chain on top of a signed extraction is the kind of evidence judges accept on the first hearing.
Compliance signal in RFPs
Enterprise procurement is already asking AI vendors for AIBOMs and output-logging. Verifiable extraction puts a tick in the box before your buyer asks.
Pricing
Free to try. Pay only when your agent ships.
Free tier: 50 extractions / month, no credit card, no watermark, public verify URL works forever. Paid tiers track the same plans as renders and signatures.