AI & Models · Integration
PDF.co
Add PDF.co to your product for your customers, and give your AI agents governed access to it.
PDF.co is a document processing API rather than a place documents live. You hand it a file, it does one thing well to that file, and it hands you back the result: a PDF turned into text or a table, a scanned page put through OCR so it becomes searchable, fields read out of an invoice against a parsing template, pages split or merged, a form filled, a barcode read. Two operational details decide how you build on it. Work is metered in credits against the key that made the call, so whose key runs a job is a billing decision and not just a configuration one, and larger jobs run asynchronously, which means your product takes a job identifier and gets the result when it is ready rather than blocking on the response. fastn keeps each customer's key per tenant, and every call is logged, so a field pulled out of a document can be tied back to the file and the job behind it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own PDF.co key so conversion and OCR credits are spent from their balance rather than yours.
Turn an uploaded scan into searchable text, so a document a customer photographed becomes something your product can read.
Extract fields from invoices, statements or forms against a template, instead of asking a person to retype them.
Split, merge or fill a PDF as a step in your own workflow, and hand the finished file back to the customer.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a scanned contract and answers a question about a clause, citing the page it came from.
An agent extracts the line items from an uploaded invoice and checks them against the order in your product.
An agent reports which document jobs failed for a customer this week and what the errors said.
Example prompt
Read this scanned invoice, pull out the supplier, total and due date, and tell me whether it matches our purchase order.
Set up PDF.co in 4 steps
- 01Enable the PDF.co connector in your fastn dashboard.
- 02Have each customer supply their own API key, so credit usage lands on the account that caused it.
- 03Choose the operations your product exposes and map the outputs you keep, including how asynchronous jobs are collected.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the PDF.co integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a PDF.co integration without building it. Your customers connect their own PDF.co account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a PDF.co update is not your on-call problem.
- One integration serves your product and your agents. The same governed PDF.co connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
Docparser
Rossum
CloudConvertOften used alongside
Tools the same teams tend to run next to PDF.co, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudePDF.co integration FAQ
How do I add a PDF.co integration to my product?
Enable the PDF.co connector in your fastn dashboard, then let each customer authenticate their own PDF.co account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no PDF.co client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own PDF.co account?
Yes. Every connection is scoped to the individual customer, so each authorises their own PDF.co account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this PDF.co integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a scanned contract and answers a question about a clause, citing the page it came from.
Who maintains the PDF.co integration?
fastn does. When PDF.co changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose PDF.co API key and quota does each call use?
Each customer authorises their own PDF.co account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the PDF.co integration?
A common starting point: let each customer connect their own PDF.co key so conversion and OCR credits are spent from their balance rather than yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the PDF.co integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding PDF.co does not change your per-connector cost. You can start free with 3 connected accounts.
Add PDF.co to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.