ohmywrap
Get an API key

§ PDF API

PDF API. 17 endpoints, $0.001 a call.

Merge, split, extract, stamp, encrypt, inspect, and chain PDFs over plain HTTP. Runs on pdfcpu. Every endpoint is one POST, every result comes back on the same connection, and a 3,000-page file costs exactly what a one-page memo costs.

Example · POST /pdf/info
curl -sS --fail-with-body \
  -H "Authorization: Bearer $OHMYWRAP_KEY" \
  -F "file=@contract.pdf" \
  https://api.ohmywrap.com/pdf/info

Page count is where document APIs make their money.

Almost every PDF service bills by the page on page-wise operations, so the invoice for stamping a 300-page policy looks nothing like the invoice for stamping a cover sheet. We bill the call. A pipeline of eight steps against a 3,000-page document is still one call, and still $0.001.

Bytes per file
20 MB
Bytes per request
60 MB
Files per request
20
Pages per request
3,000
Split output documents
100
Pipeline steps
8
Job time budget
30s
Price per call
$0.001

Anything over a limit is refused immediately, and refusals are not billed.

§ The inventory

Every pdf endpoint.

Each is a POST with your file attached, each returns the result on the same connection, and each costs $0.001. Follow any of them for parameters, limits, and a request you can paste.

Send a protected document and you get a protected document back, encrypted with the same password — that holds for every transform, so nothing here can quietly downgrade a file's security. The one exception is extract-images, whose output is images and cannot carry PDF encryption. Two things are deliberately absent: page rasterisation, which needs a rendering engine far larger than pdfcpu, and custom TTF fonts, which need a writable font cache this service does not have.

Your first pdf call takes one line of curl.

No plan to choose. No credits to model. No storage to configure.

10,000 calls for $10. No subscription, no expiry.