Reference & Lookup Data · Integration
Supadata
Add Supadata to your product for your customers, and give your AI agents governed access to it.
Supadata is a lookup API at api.supadata.ai/v1 authenticated with an x-api-key header, and it answers failures with structured JSON carrying an error code and a documentation URL rather than a bare status. The transcript endpoints take a video URL or ID and return either timestamped segments or plain text, with a language parameter that only works when that language actually exists on the source. Videos with transcripts disabled return an explicit error instead of an empty result, so any job that walks a channel has to treat missing transcripts as a normal outcome rather than a fault. Alongside transcripts it exposes video, channel and playlist metadata and generic web scraping, which is what makes it usable as one enrichment step instead of several services. fastn holds each customer's Supadata key in its own tenant and keeps quota and error handling in one place.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Supadata key so transcript lookups are billed and rate limited to them
Turn a pasted video link into a timestamped transcript your product can search and quote
Enrich a saved channel with its metadata so users see subscriber counts and recent uploads in your UI
Batch a playlist into transcripts for a customer's internal knowledge base, skipping videos with none available
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent pull a transcript and answer questions with timestamps it can cite, with every lookup counted per tenant for audit
Have an agent scrape a named page and extract only the fields a workflow asked for
Let an agent check whether a video already has a stored transcript before spending another lookup
Example prompt
Summarise this YouTube video and give me the timestamps where pricing is discussed.
Set up Supadata in 4 steps
- 01Enable the Supadata connector from your fastn dashboard.
- 02Have each customer authorise their own Supadata 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 Supadata integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Supadata integration without building it. Your customers connect their own Supadata 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 Supadata update is not your on-call problem.
- One integration serves your product and your agents. The same governed Supadata 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 Supadata, across other categories.
Salesforce
HubSpot
Notion
SnowflakeSupadata integration FAQ
How do I add a Supadata integration to my product?
Enable the Supadata connector in your fastn dashboard, then let each customer authenticate their own Supadata account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Supadata client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Supadata account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Supadata 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 Supadata integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent pull a transcript and answer questions with timestamps it can cite, with every lookup counted per tenant for audit
Who maintains the Supadata integration?
fastn does. When Supadata 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 Supadata 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 Supadata results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Supadata 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 Supadata integration?
A common starting point: let a customer connect their own Supadata key so transcript lookups are billed and rate limited to them. 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 Supadata integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Supadata does not change your per-connector cost. You can start free with 3 connected accounts.
Add Supadata to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.