Documentation

Pagentic exposes one customer-facing API surface (/v1/*) and a self-serve portal for managing keys, users, and viewing usage.

Quick start

Get an API key from your operator (or mint your own from the portal).
POST a PDF to /v1/extractions with agent=<agent_id>@<version>.
Either set webhook_url for an HMAC-signed callback, or poll GET /v1/extractions/{id}.
Fetch the structured envelope from GET /v1/extractions/{id}/result when status is succeeded.

# Submit
curl -H "Authorization: Bearer pa_test_..." \
     -F "agent=ltl_freight_invoice" \
     -F "document=@invoice.pdf" \
     -F "webhook_url=https://my-app/hook" \
     https://api/v1/extractions

# Poll
curl -H "Authorization: Bearer pa_test_..." \
     https://api/v1/extractions/ext_...

# Fetch result
curl -H "Authorization: Bearer pa_test_..." \
     https://api/v1/extractions/ext_.../result

Reference

Runtime API

Every endpoint, error code, the result envelope, version pinning rules.

Webhooks

HMAC signature verification. Retry/backoff schedule. Sample verifier in Python and Node.

Agent catalog

What agents look like, how versioning works, when to pin.

Rate limits

Per-key bucket sizes, headers we set, what 429 looks like.

Full reference and architecture diagrams ship in the project's /Docsfolder. We'll publish the rendered version here soon.