Airtop API

Name: Airtop API API
Brand: Airtop API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting Qabearer39 EndpointsREST

For Agents

Spin up cloud browser sessions, run automations against live websites, save authenticated profiles, and fill forms on behalf of an AI agent.

Quickstart

Get started with Airtop API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a cloud browser session"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Airtop API API.

Create, list, inspect, and end browser sessions via /v1/sessions endpoints

Save authenticated profiles on session termination so cookies and state persist for later runs

Create async automations that record a sequence of actions on a target site

Execute saved automations and form fillers against any session window

GET STARTED

Start building with Airtop API API

Explore with Jentic

View OpenAPI Document

Use for: I want to create a new cloud browser session for an agent, Save a logged-in profile so the next session reuses the cookies, Run a form-filler automation to fill an application form, Execute a saved automation against a fresh session window

Not supported: Does not provide LLM reasoning, native mobile automation, or local browser execution — use for cloud browser sessions, profiles, and automation execution only.

Jentic publishes the only available OpenAPI document for Airtop API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Airtop API, keeping it validated and agent-ready. Airtop is a cloud browser platform built for AI agents that need to operate the web with stateful sessions, persistent profiles, automations, and form filling. The 39 documented endpoints cover session lifecycle, window management, async automation creation and execution, form-filler automations, and profile saving on session termination. Authentication uses bearer tokens scoped per workspace.

Use Cases

Patterns agents use Airtop API API for, with concrete tasks.

★ Stateful Cloud Browser Sessions for Agents

Provision a browser in the cloud where an AI agent can navigate, click, and authenticate without managing local Chromium. POST /v1/sessions creates the session, /v1/sessions/{id} inspects it, and DELETE /v1/sessions/{id} ends it. Sessions retain cookies and storage so agents can complete multi-step flows like logging in, navigating menus, and submitting forms.

Create a session, navigate to a target URL, perform a click on the login button, and end the session

Profile Persistence Across Runs

Persist authenticated state by saving a session profile on termination via PUT /v1/sessions/{sessionId}/save-profile-on-termination/{profileName}. The next session can be launched with that profile so cookies, local storage, and logged-in state are restored — eliminating repeated login challenges and CAPTCHAs for agents.

Mark profile 'shopify-admin' to be saved on termination of session 'sess-123' and verify by listing profiles

Form-Filler Automations

Run a structured form-filler automation through POST /v1/async/sessions/{sessionId}/windows/{windowId}/fill-form to populate web forms with fields supplied by the agent. Combined with POST /v1/async/sessions/{sessionId}/windows/{windowId}/create-form-filler, agents can record a form once and replay it across many submissions.

Run form filler 'job-application-v2' on session 'sess-123', window 'win-1' with fields { 'name': 'Pat Doe', 'email': 'pat@example.com' }

Async Automation Recording and Execution

Record a sequence of browser interactions as an automation via POST /v1/async/sessions/{sessionId}/windows/{windowId}/create-automation, then replay it later with POST /v1/async/sessions/{sessionId}/windows/{windowId}/execute-automation. Useful for repetitive web flows such as exporting reports, checking dashboards, or scraping behind a login.

Create an automation that exports a CSV report from an admin dashboard and execute it weekly under a saved profile

Agent Web Operation via Jentic

An agent that needs to operate the web searches Jentic for the right Airtop session or automation operation, loads the schema, and executes under a bearer token managed by Jentic. Combines well with form-filler operations so the agent can move through a checkout or onboarding flow without owning browser state.

Search Jentic for 'create a cloud browser session', load the Airtop POST /v1/sessions operation, and execute it to start a session for the agent's task

Key Endpoints

39 endpoints — jentic publishes the only available openapi specification for airtop api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/sessions

Create a cloud browser session

GET

/v1/sessions

List active sessions

GET

/v1/sessions/{id}

Get info for a session

DELETE

/v1/sessions/{id}

End a session

PUT

/v1/sessions/{sessionId}/save-profile-on-termination/{profileName}

Save a profile on session termination

POST

/v1/async/sessions/{sessionId}/windows/{windowId}/create-automation

Create an automation

POST

/v1/async/sessions/{sessionId}/windows/{windowId}/execute-automation

Execute a saved automation

POST

/v1/async/sessions/{sessionId}/windows/{windowId}/fill-form

Run a form-filler automation

POST

/v1/sessions

Create a cloud browser session

GET

/v1/sessions

List active sessions

GET

/v1/sessions/{id}

Get info for a session

DELETE

/v1/sessions/{id}

End a session

PUT

/v1/sessions/{sessionId}/save-profile-on-termination/{profileName}

Save a profile on session termination

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Airtop bearer tokens are stored encrypted in the Jentic vault. Tokens are scoped per workspace and the Authorization header is injected at execution time so raw tokens never enter the agent's context.

Intent-based discovery

Agents search by intent ('create a cloud browser session', 'fill a web form') and Jentic returns the matching Airtop operation with its session, window, and body schema.

Time to first call

Direct Airtop integration: 1-3 days including session lifecycle, profile persistence, and async automation polling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Browserless

Cloud Chromium API focused on raw automation rather than agent-shaped session and profile primitives

Choose Browserless when you control automation logic in code (Puppeteer/Playwright); choose Airtop when sessions, profiles, and form fillers as first-class concepts speed up agent development

Alternative

Apify

Marketplace of pre-built scrapers and a general-purpose actor runtime

Use Apify when an off-the-shelf actor exists for the target site; use Airtop when an agent needs to drive an arbitrary stateful browser session

Complementary

OpenAI API

Pair OpenAI's reasoning with Airtop's browser to let an agent plan and act on the web

Add OpenAI (or Anthropic) to drive the planning loop while Airtop executes the browser steps

FAQs

Specific to using Airtop API API through Jentic.

Why is there no official OpenAPI spec for Airtop API?

Airtop does not publish a single canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Airtop API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Airtop API use?

Airtop uses HTTP bearer tokens scoped to a workspace. Pass the token via Authorization: Bearer <token> on every call. Through Jentic the token is stored encrypted and injected at execution time so the agent never sees the raw value.

Can I save a logged-in browser profile across sessions?

Yes. PUT /v1/sessions/{sessionId}/save-profile-on-termination/{profileName} marks the profile to persist when the session ends. Subsequent sessions can load that profile so cookies, storage, and login state come back without re-authenticating.

What are the rate limits for the Airtop API?

Airtop applies per-workspace concurrency limits on active sessions plus request-rate limits on the management endpoints. Exact thresholds are documented at docs.airtop.ai. Treat HTTP 429 as a backoff signal and check workspace concurrency before creating new sessions.

How do I create a cloud browser session through Jentic?

Install with pip install jentic, search for 'create a cloud browser session', load the Airtop POST /v1/sessions operation, and execute with any optional configuration (profile, locale). Jentic injects the bearer token automatically.

Can I run a form-filler automation against a specific window?

Yes. POST /v1/async/sessions/{sessionId}/windows/{windowId}/fill-form runs a previously created form filler against the given window with field values supplied as structured input. Pair with /create-form-filler to record the filler once and reuse it many times.