Give your agent the whole document layer.

Render a PDF from a Kamy template and data, and wait for it.

Render an editable Word (.docx) document from a Kamy template and data.

Build a PowerPoint (.pptx) deck from a slide spec: an ordered array of slides, each tagged with one of five fixed layouts (title, bullets, two-column, table, quote).

Build an Excel (.xlsx) workbook from a sheet spec: columns with keys, row objects keyed to those columns, optional Excel number formats and a formula-aware total row (bare 'SUM' / 'AVG' / 'COUNT' / 'MIN' / 'MAX' expands into a real formula over the column's data range).

Compile a Kamy template — or raw Handlebars source you pass inline — against a data payload and get the rendered HTML string back.

Convert a file you already hold — .docx, .xlsx or .csv — into a PDF, preserving its existing content.

Concatenate 2–20 existing renders into a single new PDF, in exactly the order the ids are given.

Extract page ranges from one existing render into separate new PDFs — the inverse of merge_pdfs.

Modify an existing PDF: fill AcroForm fields by name, stamp text at absolute coordinates, or paint opaque boxes over regions.

Store an image, font or PDF in the account's asset bucket and get back a `kamy://asset/<id>` reference you can drop anywhere inside a render_pdf / render_html data payload — Kamy swaps it for a fresh signed URL at render time.

Look up a stored asset by its upload id: filename, contentType, sizeBytes, status, its `kamy://asset/<id>` reference, and a freshly signed downloadUrl valid for one hour once the bytes exist.

Queue one PDF render and return immediately with { jobId, status: 'queued' } instead of waiting for the document.

Render up to 100 documents in a single blocking call, each from its own template, HTML or URL, and get every result back in one response.

Read everything about the authenticated Kamy account in one call: profile, plan and plan status, the plan's limits (renders per month, API keys, seats, custom templates, overage pricing, priority queue), month-to-date render usage, and whether documents rendered on this plan carry Kamy's own watermark.

List the documents this account has already produced, newest first.

Fetch one previously produced document by its render id, with a freshly signed download URL valid for the next hour.

Rasterise every page of an existing render to a PNG image and return one signed 1-hour URL per page, with pixel width and height.

Poll an asynchronous render job started by render_async.

Set up a recurring render: a cron expression, a template, and where each document goes.

List this account's recurring render schedules, newest first, with the id needed to delete one.

Permanently delete a recurring schedule so it stops firing.

Register an HTTPS endpoint that Kamy POSTs to when work finishes, so a long render or an e-signature does not have to be polled.

List the webhook endpoints registered on this account, with the id needed to test one.

Send a real test.ping event to a registered webhook endpoint — an actual outbound HTTP POST to whatever URL the user configured, signed like a genuine delivery.

Send a previously rendered PDF to a signer for e-signature when a Kamy API key is configured.

Send a single PDF to 2–10 signers as one envelope.

List signature requests created by the configured Kamy account, newest first.

Returns the authenticated download URL for a signature request's Certificate of Completion PDF — the process audit trail (invite → opened → consent → signed, with IP / user-agent) that legal teams expect.

Fetch one signature request by id, with the detail list_signature_requests leaves out: the placed_fields layout, signed_at plus signed_ip and signed_user_agent, last_reminded_at, cc_emails, and envelope_id + recipient_order when it is part of an envelope.

Fetch one multi-signer envelope with every recipient in signing order — each with a live sign_url, status, recipient_order, expires_at and last_reminded_at — plus the envelope's own status and routing.

Resend the signature invitation email.

Fan one already-rendered PDF out to up to 100 independent signers in a single call — the 'send this NDA to everyone on the list' path.

Check a placedFields layout against a real render's page geometry before anything is sent: no signature request is created, no email goes out, and no signature quota is spent.

List this account's reusable e-signature presets — saved field placements, default invite message, default link lifetime and CC list — newest first.

Fetch one e-signature preset in full, including the placed_fields array and position that list_signature_templates omits.

Cryptographically sign an existing render with PAdES when a Kamy API key is configured.

Turn PDF bytes you are holding into their SHA-256 digest and the matching kamy.dev/verify/{sha256} page URL.

Dry-run a render payload against a template's schema WITHOUT producing a PDF or using quota.

Extract structured data from a PDF (invoice, receipt, contract, ID document, or any form).

Read the text or the form fields back out of a document this account already rendered, without uploading anything.

Cryptographically sign an output your agent produced — a PDF, report, code patch, dataset, email — so a third party can later confirm those exact bytes are the ones that were recorded, unmodified.

Ask Kamy whether a SHA-256 digest has an attestation on record — the tool that actually returns a verdict.

Append one signed tool_call -> tool_result pair to a tamper-evident ledger.

Replay everything recorded under one run_id — artifacts from attest_artifact and calls from record_agent_action — in order, with each record's link to its parent hash.

Record one LLM call — prompt, output, provider, model, tokens, latency — into Kamy Trace, a signed retention ledger.

Write up to 100 Kamy Trace records in one call.

Query this account's Kamy Trace records, newest first, filtered by feature, status, provider, tag, or time window.

Detect when an MCP server changes its tool manifest after you adopted it — the 'rug pull' case, where a server you already trusted silently rewrites a tool's description or input schema.

Heuristic pattern scan of MCP tool description text for prompt-injection tells — instructions addressed at the reading model, data-exfiltration hints, attempts to override your system prompt or hide content.

Create a new custom PDF template owned by this account: a name, a unique slug, a Handlebars/HTML body, and optional CSS and JSON Schema.

Edit an existing custom template's DRAFT — name, html, css, schema, tags, visibility — addressed by UUID or slug.

Make a template version live for rendering.

Revert a template after a bad release: repoints published_version at the version you name, so every subsequent render immediately serves that snapshot again.

List a template's immutable version snapshots, newest first, as { id, version, createdAt }.

Fetch one template version snapshot in full — html, css, schema, createdBy, createdAt — exactly as it was frozen when that version was cut.

List Kamy's public system PDF templates.

Fetch the JSON Schema (exact data shape) and a copy-pasteable sample payload for a Kamy system template by slug.

Ask Kamy Brain a question about Kamy usage, templates, plans, or errors.

Everything needed to go from nothing to a rendered document in one call: the steps to create an API key in the dashboard, and — when you name a `framework` — the install command for the Kamy SDK, the environment variable it reads, and the client-setup snippet for that stack.