Reference & Lookup Data · Integration
Linkup
Add Linkup to your product for your customers, and give your AI agents governed access to it.
Linkup is a web search API built for grounding language models, reached at api.linkup.so/v1 with a bearer API key. The main call is POST /v1/search, which takes a natural language query plus a depth of standard or deep and an outputType of sourcedAnswer, searchResults or structured. Deep searches cost considerably more credits and take much longer to return than standard ones, so treating them as interchangeable is the usual cause of both latency and billing surprises. When outputType is structured you must also supply a JSON schema in structuredOutput, and the response is validated against it rather than returned as free text. Credit consumption is per call and readable from the credits balance endpoint, which is worth polling if you resell searches to your own users. fastn keeps each customer's Linkup key isolated so their search spend and quota stay attributable to them.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Linkup key so web research in your product runs on their quota and their bill
Ground an in-app answer feature with sourced results that carry citations back to the original pages
Enrich a company or person record with fresh public information at the moment a user opens it
Show a customer their remaining Linkup credits and warn before a deep search burns through them
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent run a standard search freely but require approval before spending credits on a deep search
Have an agent return only sourced answers with citations so claims can be checked against the linked pages
Log every search query and its credit cost, audited per tenant, so spend can be attributed
Example prompt
Search the web for the latest pricing changes announced by our top three competitors.
Set up Linkup in 4 steps
- 01Enable the Linkup connector from your fastn dashboard.
- 02Have each customer authorise their own Linkup 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 Linkup integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Linkup integration without building it. Your customers connect their own Linkup 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 Linkup update is not your on-call problem.
- One integration serves your product and your agents. The same governed Linkup 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 Linkup, across other categories.
Salesforce
HubSpot
Notion
SnowflakeLinkup integration FAQ
How do I add a Linkup integration to my product?
Enable the Linkup connector in your fastn dashboard, then let each customer authenticate their own Linkup account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Linkup client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Linkup account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Linkup 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 Linkup 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 run a standard search freely but require approval before spending credits on a deep search
Who maintains the Linkup integration?
fastn does. When Linkup 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 Linkup 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 Linkup results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Linkup 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 Linkup integration?
A common starting point: let a customer connect their own Linkup key so web research in your product runs on their quota and their bill. 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 Linkup integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Linkup does not change your per-connector cost. You can start free with 3 connected accounts.
Add Linkup to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.