AI & Models · Integration
DX Suite
Add DX Suite to your product for your customers, and give your AI agents governed access to it.
Embed a DX Suite integration so your customers can submit their own documents for recognition and read the extracted data back inside your product, using their own account. Access runs through each customer's own grant, so their content stays theirs and your product cannot read a document the connected account could not read itself. fastn handles per-customer authentication and API upkeep, so a customer with different document layouts is configuration rather than a release on your side.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers submit their own documents for recognition from inside your product.
Read extracted values back and write them onto the right record in your app automatically.
Keep each customer's own document types and output fields mapped as configuration, not code.
Trigger your product when a recognition job finishes so the next step runs immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads extracted document data before answering a question grounded in the customer's paperwork.
An agent submits a document for recognition within governed permissions, with the action audited.
An agent reacts to a completed job and files the extracted values where your workflow expects them.
Example prompt
List documents processed this week where a required field came back empty, grouped by document type.
Set up DX Suite in 4 steps
- 01Open the DX Suite connector from your fastn dashboard.
- 02Have each customer authenticate their own DX Suite account.
- 03Map the document types and output fields your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the DX Suite integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DX Suite integration without building it. Your customers connect their own DX Suite 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 DX Suite update is not your on-call problem.
- One integration serves your product and your agents. The same governed DX Suite 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
DocparserWorks well with
Box
DropboxOften used alongside
Tools the same teams tend to run next to DX Suite, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeDX Suite integration FAQ
How do I add a DX Suite integration to my product?
Enable the DX Suite connector in your fastn dashboard, then let each customer authenticate their own DX Suite account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DX Suite client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DX Suite account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DX Suite 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 DX Suite 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 extracted document data before answering a question grounded in the customer's paperwork.
Who maintains the DX Suite integration?
fastn does. When DX Suite 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 DX Suite API key and quota does each call use?
Each customer authorises their own DX Suite 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 DX Suite integration?
A common starting point: submit their own documents for recognition from inside your product. 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 DX Suite integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DX Suite does not change your per-connector cost. You can start free with 3 connected accounts.
Add DX Suite to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.