Standardized API calls
Create, launch, close, and manage browser profiles through unified API calls so automation tasks stay predictable, repeatable, and easier to support across teams.
Local API
AdsPower Local API gives developers, technical teams, and AI agent projects a more reliable way to launch, control, query, and orchestrate browser profiles. Connect isolated profile environments with Selenium, Puppeteer, Playwright, MCP, internal task systems, and automation workflows from one local interface.
Create, launch, close, and manage browser profiles through unified API calls so automation tasks stay predictable, repeatable, and easier to support across teams.
Connect browser profiles with MCP-enabled AI tools so agents can call real browser environments, execute page actions, and complete workflow steps through structured control.
Built for projects that handle many accounts, profiles, and browser tasks, helping teams coordinate bulk profile control, data workflows, and long-running automation.
Local API is not just a browser launch endpoint. It is a control layer that connects browser profiles, automation frameworks, AI agents, enterprise data processes, and migration workflows into a more scalable technical system.
During account creation, profile maintenance, permission assignment, and bulk data operations, Local API helps analytics teams, operations teams, and technical projects manage large-scale browser environments more efficiently.
AdsPower Local API can be connected with Selenium, Puppeteer, Playwright, and similar frameworks. Developers can control isolated browser profiles through API calls and complete page interaction, browser testing, data processing, and automated tasks.
With AdsPower Local API MCP Server, AI tools can call browser profiles as execution environments. In tools that support MCP, natural language can trigger profile launch, configuration creation, task execution, and browser interaction.
AdsPower supports migration from selected mainstream fingerprint browser tools, helping teams move historical browser profile assets, reduce reconfiguration work, and rebuild automation workflows faster.
Local API is best for teams that need engineering-friendly browser control rather than manual profile operation. It is especially useful for automation development, AI agent control, browser-based data workflows, and enterprise account management.
Ideal for engineering teams that need to start, control, and close browser profiles through code, or embed browser capabilities into internal tools, task queues, dashboards, and backend automation systems.
Run browser-based research, page interaction, data processing, and task rotation in isolated profile environments at scale.
Allow MCP-enabled AI tools to launch and control AdsPower browser profiles through structured or natural-language workflows.
Fit teams that need unified management of account assets, permissions, profile data, automation scripts, and browser execution environments.
API calls
Local API gives developers a practical way to connect AdsPower browser profiles with existing automation systems. Whether you need to launch profiles, retrieve WebDriver information, manage execution endpoints, or connect server-side task flows, the API-based model fits technical workflows more naturally.
fetch('http://local.adspower/api/v1/browser/start', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ user_id: 'profile_001' })
})
.then((res) => res.json())
.then((data) => console.log(data.ws, data.webdriver));
AdsPower Local API can fit into everyday development stacks instead of acting as an isolated feature. Developers can use familiar frameworks for browser control, while AI workflows can use MCP to call browser profiles as execution environments.
Suitable for mature automation testing flows, WebDriver-based projects, backend task scheduling, and integration into existing enterprise development pipelines.
Suitable for Node.js browser control, page interaction, scripted workflows, account task execution, and browser-based automation projects.
Suitable for teams that need modern browser control, concurrent task execution, complex page interaction, and multi-scenario automation.
Suitable for attaching browser execution capabilities to AI agents, copilots, workflow orchestration systems, and conversational task control.
When an AI tool needs to perform browser-based work, Local API can act as the execution layer between AI instructions and isolated browser profiles. The AI understands the goal, MCP translates the action, Local API launches the environment, and the browser completes the task.
Pass goals through conversation, task systems, or agent workflows.
Parse instructions and map them into executable browser actions.
Launch profiles, inject configuration, and return control endpoints.
Complete page interaction, browser automation, and data workflows.
AdsPower Local API is best suited for automation developers, data teams, AI agent builders, enterprise account operations, and technical teams that need to launch, close, query, and orchestrate browser profiles through code.
Local API can be used with common browser automation frameworks such as Selenium, Puppeteer, and Playwright. It can also connect with custom scripts, server-side task flows, internal tools, and automation platforms.
Yes. Through MCP Server and related workflows, AI tools that support MCP can call AdsPower browser profiles as execution environments for page interaction, task scheduling, data processing, and browser automation.
Window Synchronizer is better for visual, human-led bulk actions across multiple windows. Local API is better for developers who need code-based browser profile control, automation integration, AI agent workflows, and internal system orchestration.
AdsPower supports migration from selected mainstream fingerprint browser tools, helping teams move historical profile assets, reduce repeated configuration work, and rebuild browser automation workflows more efficiently.
AdsPower
Download AdsPower to connect browser profiles with Local API, Selenium, Puppeteer, Playwright, MCP, AI agents, and scalable automation workflows.