PDF Operations Toolkit avatar

PDF Operations Toolkit

Pricing

from $33.50 / 1,000 pdf operations toolkit verdicts

Go to Apify Store
PDF Operations Toolkit

PDF Operations Toolkit

Runs split / merge / reorder / compress / rasterize on supplied PDFs and returns a per-operation manifest reconciling every input page to an output page (no silent page loss), with per-artifact SHA-256, byte-size delta, and warnings. Artifacts written to the run key-value store.

Pricing

from $33.50 / 1,000 pdf operations toolkit verdicts

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Runs split / merge / reorder / compress / rasterize on supplied PDFs and returns, per operation, a manifest that RECONCILES every input page to an output page (no silent page loss) plus per-artifact SHA-256, a byte-size delta, and warnings. Output artifacts are written to the run key-value store.

What you submit

operations — pdf operations. Each operation is an object: {op, inputs, params}. op is split | merge | reorder | compress | rasterize. inputs is a list of PDFs, each a base64 string (optionally a data: URL) or a key naming an entry in the run key-value store. Every completed operation emits a manifest that RECONCILES input pages to output pages (no silent page loss), with per-artifact SHA-256, byte-size delta, and warnings; output artifacts are written to the run key-value store. Untrusted-file guards: byte-size and page ceilings, a decompression-bomb guard, encrypted/corrupted inputs rejected loudly, and embedded JavaScript / auto-actions reported as warnings, never executed. One charge per completed, reconciled operation.

Untrusted-file guards

Every input PDF is treated as untrusted: a per-file byte-size cap and a page cap reject oversized inputs before work, a decompression-bomb guard applies, encrypted and corrupted PDFs are rejected loudly, and embedded JavaScript / auto-actions (/JavaScript, /JS, /OpenAction, /Launch, /AA) are reported as warnings, never executed.

Output & billing

One row per operation. An operation bills once if it completes AND its page map fully reconciles input pages to output (no silent loss). A guard rejection (oversized / encrypted / corrupted / bad op) or an operation that would drop pages is delivered as an unbilled rejected status. Push-then-charge: every row is delivered before its charge, so a billing hiccup can only ever undercharge.

Pricing

EventPriceWhen
apify-actor-start$0.02once when the run starts (reserved; never charged in code)
pdf_operation_check$0.05once per completed, page-reconciled operation (rejected / non-reconciling operations never bill)

Volume tiers reduce the per-verdict price as usage grows: $0.05 → $0.045 → $0.04 → $0.0335.

Why this and not the obvious alternative

split / merge / reorder / compress / rasterize with a page-map that reconciles every input page to an output page (no silent loss) plus per-artifact hashes and a size-delta ledger — an evidence-grade PDF operations toolkit, not a black-box converter.