Reference & Lookup Data · Integration
urlscan.io
Add urlscan.io to your product for your customers, and give your AI agents governed access to it.
urlscan.io renders a URL in a sandboxed browser and records what happened: the requests the page made, the domains and addresses it touched, the resulting DOM, a screenshot and a verdict on whether any of it looked malicious. That makes it a read source with an unusual rhythm. A submission is asynchronous, so your product posts a URL, gets back a scan id and polls until the result exists rather than waiting on a single call, and every submission carries a visibility choice, because a public scan is searchable by anyone while an unlisted or private one is not. Search runs over scans already in the corpus and answers plenty of questions without submitting anything new. Quota is counted against the key that made the call, which is why each customer supplies their own. fastn holds those keys per tenant and tracks the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer supply their own urlscan.io key so scan quota is metered against the tenant that triggered it.
Submit a suspicious link from your product, poll the scan id, and show the verdict and screenshot beside the message it arrived in.
Search the existing corpus for a domain before submitting anything, since a scan somebody already ran answers the question without spending a call.
Set the visibility on every submission deliberately, because a public scan of a customer's internal URL is a disclosure you cannot take back.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent submits a URL, waits for the scan to finish and explains what the page actually loaded.
An agent searches previous scans of a domain and reports what has been seen there before, with the query logged.
An agent quotes the verdict and the observed requests rather than pronouncing a link safe on its own judgement.
Example prompt
Scan this link and tell me which domains it contacted and whether urlscan.io flagged any of them.
Set up urlscan.io in 4 steps
- 01Enable the urlscan.io connector in your fastn dashboard.
- 02Have each customer supply their own urlscan.io API key, so scan quota and cost land on them rather than on a shared key.
- 03Decide which submissions your product makes, what visibility each one carries, and how long a result or a search is cached before you scan again.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the urlscan.io integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a urlscan.io integration without building it. Your customers connect their own urlscan.io 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 urlscan.io update is not your on-call problem.
- One integration serves your product and your agents. The same governed urlscan.io 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
AbuseIPDB
Google Safe Browsing
APIVoidOften used alongside
Tools the same teams tend to run next to urlscan.io, across other categories.
Salesforce
HubSpot
Notion
Snowflakeurlscan.io integration FAQ
How do I add a urlscan.io integration to my product?
Enable the urlscan.io connector in your fastn dashboard, then let each customer authenticate their own urlscan.io account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no urlscan.io client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own urlscan.io account?
Yes. Every connection is scoped to the individual customer, so each authorises their own urlscan.io 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 urlscan.io 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 submits a URL, waits for the scan to finish and explains what the page actually loaded.
Who maintains the urlscan.io integration?
fastn does. When urlscan.io 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 urlscan.io 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 urlscan.io results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. urlscan.io 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 urlscan.io integration?
A common starting point: have each customer supply their own urlscan.io key so scan quota is metered against the tenant that triggered 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 urlscan.io integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding urlscan.io does not change your per-connector cost. You can start free with 3 connected accounts.
Add urlscan.io to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.