← All integrations

Anchor Browser

64 operations0 webhooks

Cloud browser automation API for running headless web sessions and scraping tasks.

Supported operations

  • List Agent ResourcesRead-only

    List all agent resources (files) uploaded to a browser session. Returns metadata for each file including name, size, file type, and last modified timestamp. Requires an active running session - use START_BROWSER_SESSION first. Files can be uploaded using UPLOAD_FILE action.

  • Pause AgentWrite

    Tool to pause the AI agent for a specific browser session. Use when you need to temporarily halt autonomous agent execution while keeping the session active.

  • Resume AgentWrite

    Tool to resume the AI agent for a specific browser session. Use when you need to restart agent execution after it has been paused or stopped.

  • Upload FileWrite

    Tool to upload a file to a browser session as an agent resource. Use after starting or referencing a session when you need to provide file inputs (single files or ZIP archives) for web forms or AI-driven tasks. Supports direct base64-encoded content or S3 key references from other actions.

FAQ

Install corsair and @corsair-dev/anchorbrowser, add the Anchor Browser plugin, and connect with an API key. Then call methods like corsair.anchorbrowser.api.agent.listAgentResources() from your app. Corsair syncs data per tenant.

Yes. Anchor Browser requires an API key from your Anchor Browser account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Anchor Browser, GitHub, Notion, Stripe, and the rest. Trigger Anchor Browser from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for cloud browser automation api for running headless web sessions and scraping tasks. Common builds include sync jobs, admin tooling, and agents that call Anchor Browser APIs from your backend. Local DB entities let you query synced Anchor Browser records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Anchor Browser API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/anchorbrowser in the open repo. When Anchor Browser ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Anchor Browser data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Anchor Browser data on your behalf.