Data & Storage · Integration
Bright Data
Add Bright Data to your product for your customers, and give your AI agents governed access to it.
Bright Data is how teams collect public web data at scale, and an embedded Bright Data integration means your product can trigger that collection rather than asking a customer to run it and upload a file. You work with proxy zones, scrapers, collection jobs and the datasets a job produces, plus a delivery target such as a bucket the customer owns. The shape that surprises people is that collection is a job, not a request: you start it, it takes as long as the target site takes, and results arrive later through a snapshot or a delivery, so none of this belongs behind a synchronous call in your interface. fastn keeps each account's credentials and keeps pace with API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer use their own Bright Data account, so collection volume and cost land with the team that asked for it.
Start a collection job from an event in your product and pick the results up once the snapshot is ready.
Deliver scraped output straight into the customer's own storage bucket so large results never sit in your app.
Read job status and errors so a customer can see why a run returned less than they expected.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent starts an approved collection job and says what it returned once the run completes.
An agent reads a finished dataset to answer a question, with the job it drew from recorded.
An agent explains why a run came back partial by reading that job's own error detail.
Example prompt
Did last night's collection job finish, and how many records did the dataset come back with?
Set up Bright Data in 4 steps
- 01Enable the Bright Data connector from your fastn dashboard.
- 02Have each customer authorise their own Bright Data account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Bright Data integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Bright Data integration without building it. Your customers connect their own Bright Data account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Bright Data update is not your on-call problem.
- One integration serves your product and your agents. The same governed Bright Data connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
ParseHubWorks well with
Skyvern
SemrushOften used alongside
Tools the same teams tend to run next to Bright Data, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceBright Data integration FAQ
How do I add a Bright Data integration to my product?
Enable the Bright Data connector in your fastn dashboard, then let each customer authenticate their own Bright Data account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Bright Data client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Bright Data account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Bright Data account and only ever sees their own records, datasets and fields. 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 Bright Data 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 starts an approved collection job and says what it returned once the run completes.
Who maintains the Bright Data integration?
fastn does. When Bright Data 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.
Does the Bright Data integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Bright Data reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Bright Data integration?
A common starting point: let each customer use their own Bright Data account, so collection volume and cost land with the team that asked for it. 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 Bright Data integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Bright Data does not change your per-connector cost. You can start free with 3 connected accounts.
Add Bright Data to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.