Reference & Lookup Data · Integration
BigDataCloud
Add BigDataCloud to your product for your customers, and give your AI agents governed access to it.
BigDataCloud serves its APIs from api-bdc.net rather than the marketing domain, which is the first thing that catches implementers out, and the key is passed as a query parameter on each request. The catalogue is a set of independent read-only lookups rather than one resource tree: IP geolocation with confidence areas, reverse geocoding to a locality, network and ASN details, hazard and timezone data, and phone number validation. The reverse geocoding client endpoints are designed to be called from the browser with a referrer restriction instead of a secret, so a customer may hold two different key types and only one of them is safe to use server side. Responses are structured but vary widely between products, so each lookup needs its own mapping rather than a shared parser, and free tiers apply per product rather than to the account as a whole. There are no writes, no webhooks and no stored state, so results should be cached against your own records to keep call volume down. fastn holds each customer's key, keeps the per-product quotas separate and maintains the connection.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own BigDataCloud account so IP lookups in your app run on their quota and their terms
Resolve a signup IP to a country and network to drive a customer's own fraud rules
Reverse geocode coordinates captured by a mobile app into a readable locality for reporting
Validate and normalise phone numbers on a customer's inbound lead forms before they reach the CRM
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to classify a batch of login IPs by country and network type for one tenant
Have an agent check which submitted phone numbers fail validation and summarise the pattern
Let an agent enrich records with locality data, with each lookup audited per tenant against that tenant's own key
Example prompt
Where did the sign-ups from this list of IP addresses come from, and are any on hosting networks?
Set up BigDataCloud in 4 steps
- 01Enable the BigDataCloud connector from your fastn dashboard.
- 02Have each customer authorise their own BigDataCloud account, so calls run under their credentials rather than a shared key.
- 03Decide which lookups, results and reports 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 BigDataCloud integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BigDataCloud integration without building it. Your customers connect their own BigDataCloud account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a BigDataCloud update is not your on-call problem.
- One integration serves your product and your agents. The same governed BigDataCloud connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Clearbit
APIVoidOften used alongside
Tools the same teams tend to run next to BigDataCloud, across other categories.
Salesforce
HubSpot
Notion
SnowflakeBigDataCloud integration FAQ
How do I add a BigDataCloud integration to my product?
Enable the BigDataCloud connector in your fastn dashboard, then let each customer authenticate their own BigDataCloud account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BigDataCloud client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BigDataCloud account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BigDataCloud account and only ever sees their own lookups, results and reports. 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 BigDataCloud integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to classify a batch of login IPs by country and network type for one tenant
Who maintains the BigDataCloud integration?
fastn does. When BigDataCloud 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 credentials does a BigDataCloud lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should BigDataCloud results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. BigDataCloud is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the BigDataCloud integration?
A common starting point: let a customer connect their own BigDataCloud account so IP lookups in your app run on their quota and their terms. 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 BigDataCloud integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BigDataCloud does not change your per-connector cost. You can start free with 3 connected accounts.
Add BigDataCloud to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.