BiGapiguides
POST /v1/pdf/pdfa → 200 application/pdf · 5¢

PDF/A conversion API — archive-ready documents

Converts any PDF to PDF/A-2b: fonts embedded, colours normalised, ready for long-term storage and compliance workflows (GoBD, tax, legal).

Quick start (curl)

Get a key first – no signup: curl -X POST https://api.bigapi.dev/v1/keys (100 free operations, 7 days).

curl -X POST https://api.bigapi.dev/v1/pdf/pdfa -H 'Authorization: Bearer $KEY' -F 'file=@in.pdf' -o archive.pdf

Give it to your agent (MCP)

Add BiGapi to Claude Desktop, Cursor or any MCP client – the server fetches its own key on first use:

{
  "mcpServers": {
    "bigapi": { "command": "npx", "args": ["-y", "@bigapi/mcp"] }
  }
}

Then simply ask: “Convert this invoice PDF to PDF/A for archiving.” – the model calls the pdf_to_pdfa tool.

When your agent needs this

Parameters

ParamTypeRequiredNotes
filefileyes

Pricing

5¢ per operation
First 100 operations free (per key, 7 days) · failed calls (4xx/5xx) cost $0 · repeats with Idempotency-Key are free · prepaid credit from $5, never expires.

Every response carries X-BigAPI-Cost, X-BigAPI-Balance and X-BigAPI-Free-Ops – your agent can budget on its own.

Errors your agent can handle

StatusMeaningAgent action
401missing/invalid keyPOST /v1/keys for a fresh one
402credit exhaustedshow the upgrade_url from the response to a human
413file too largesplit the input (limit 100 MB)
422conversion failedcheck the detail field – costs $0
429rate limitedwait retry_after seconds

FAQ

Which PDF/A level?

PDF/A-2b – the pragmatic archive standard authorities and DMS systems accept.

Does it change how the document looks?

No – content is preserved; fonts get embedded and colours normalised to sRGB.

Typical pipeline?

render or ocr first, then pdfa as the last step before storage.