Developer Tools · Integration
Airtop
Add Airtop to your product for your customers, and give your AI agents governed access to it.
Airtop runs hosted cloud browsers that agents drive over a REST API at api.airtop.ai/api/v1. The object model is sessions first, then one or more windows inside a session created at /api/v1/sessions/{sessionId}/windows, each with its own screenResolution (default 1280x720) and a waitUntil of load or domcontentloaded. Page content is pulled with natural-language extract and query calls against a window rather than by writing CSS selectors, so the shape of what comes back depends on the schema you ask for. The detail that catches implementers out is profiles: cookies and signed-in state only survive a session if you save a profile explicitly and attach it to the next session, otherwise every run starts logged out. Sessions are billed while they stay alive, so orphaned sessions from failed runs are a real cost, not just untidy state. The category nouns here are services rather than builds or deployments; the useful objects are sessions, windows and profiles. fastn holds each customer's Airtop key, keeps the connection current and scopes what an agent may do with it.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Airtop account so your product runs browser tasks under their credentials and profiles.
Capture data from a customer's logged-in supplier or bank portal by attaching a saved profile to a fresh session.
Give support staff a one-click way to open a live Airtop window against a customer's web account and read the current page state.
Run scheduled extractions from sites with no API and write the structured output back into your own records.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent create a session, load a named URL in a window and return structured extracted fields, with every session start and terminate audited per tenant.
Have an agent reuse a saved profile to check whether a customer's login is still valid before a scheduled job runs.
Allow an agent to terminate idle sessions it opened, without permission to delete stored profiles.
Example prompt
Open my supplier portal with the saved profile and pull this month's order lines.
Set up Airtop in 4 steps
- 01Enable the Airtop connector from your fastn dashboard.
- 02Have each customer authorise their own Airtop account, so calls run under their credentials rather than a shared key.
- 03Decide which services, builds and deployments 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 Airtop integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Airtop integration without building it. Your customers connect their own Airtop account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Airtop update is not your on-call problem.
- One integration serves your product and your agents. The same governed Airtop connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHub
Azure DevOps
Google CloudOften used alongside
Tools the same teams tend to run next to Airtop, across other categories.
Slack
Snowflake
Airtable
PostgreSQLAirtop integration FAQ
How do I add an Airtop integration to my product?
Enable the Airtop connector in your fastn dashboard, then let each customer authenticate their own Airtop account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Airtop client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Airtop account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Airtop account and only ever sees their own services, builds and deployments. 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 Airtop 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 create a session, load a named URL in a window and return structured extracted fields, with every session start and terminate audited per tenant.
Who maintains the Airtop integration?
fastn does. When Airtop 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.
Can I react to Airtop events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in Airtop?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the Airtop integration?
A common starting point: let a customer connect their own Airtop account so your product runs browser tasks under their credentials and profiles. 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 Airtop integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Airtop does not change your per-connector cost. You can start free with 3 connected accounts.
Add Airtop to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.