BROWSER INFRASTRUCTURE · FOR AI AGENTS
Airtop Cloud Browsers
Run browser sessions with saved profiles and natural-language page operations.
Use Airtop APIs and SDKs to create cloud browser sessions, load pages, extract information and reuse authorized login state across sessions.
Your integration checklist
- Capabilities
- What you need from your owner
- Create an Airtop account, obtain a developer API key and select a usage plan. For authenticated sites, have the authorized user establish a profile through the supported login flow.
- Authentication
- Initialize the Airtop SDK with the developer API key. Saved profiles belong to the organization and retain cookies and local storage; treat access to a profile as access to its authenticated session.
- Your first task
- Create a session and window, query one permitted page and terminate the session after checking the extracted result.
- Billing & payment
- Credits cover AI calls, browser CPU time and proxy usage. Plans set credit allowances and simultaneous-session capacity. Track the returned usage and explicitly terminate idle browsers.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Session creation can wait for capacity. Per-call costThresholdCredits and timeThresholdSeconds are periodically checked thresholds, not strict caps. Profiles marked for saving are persisted on session termination.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Verify profile identity and session cleanup before repeating browser work
Editorial recommendation · Reviewed 2026-10-23
When to choose this service
Choose Airtop when an agent needs an operated browser and reusable authorized session state for a website workflow, including pages that require interaction before useful data appears.
The service supplies running browser infrastructure and managed profile persistence. Writing navigation code alone does not operate those sessions or obtain the user’s authenticated state.
Suggested workflow
- Map the task to a permitted site and profile. Confirm the signed-in identity before interacting with account data or forms.
- Wait for a running session and the target page, then query or interact within a bounded task. Validate extracted values against the page and monitor returned credits.
- Save the profile only when intended and terminate the session in cleanup, including failure paths. Reopen a controlled session to confirm the expected state was retained.
Acceptance checks before real work
- Confirm the restored profile is the intended account.
- Leave budget headroom because thresholds can be exceeded by an in-flight call.
- Verify termination and profile persistence separately from task completion.
If the workflow fails
Inspect session state before creating a replacement browser. If login has expired, use the authorized login flow; reconcile any submitted form before retrying the action.