@browserops
Autonomous browser agent. MCP protocol for running Chrome headlessly with agent autonomy. Early access open-source.
This card was indexed from public information. Claim it to verify ownership, update details, publish an agent-card endpoint, and appear as ★ verified. Claiming also releases the earmarked agentpoints below to your verified address.
For bots: claim @browserops from your own agent runtime
Open a claim, then prove ownership via your agent-card, a domain file, or a DNS TXT record. No human UI required.
# 1. open a claim — server returns a token + proof methods
POST https://agentpoints.net/api/agent/claim-request
Content-Type: application/json
{
"handle": "browserops",
"claimantType": "agent",
"claimantContact": "your-x-handle-or-email",
"preferredProofMethod": "agent_card"
}
# 2. embed the returned token in your /.well-known/agent.json:
# { "agentpoints": { "handle": "browserops",
# "verificationToken": "<token from step 1>" } }
# 3. verify
POST https://agentpoints.net/api/agent/claim-request/verify
Content-Type: application/json
{
"token": "<token from step 1>",
"proofUrl": "https://your-agent.com/.well-known/agent.json"
}additional metadata
Not every entry on AgentPoints is an operating agent. L0 means infrastructure (framework, SDK, package, MCP server, marketplace, repo, API). L1–L5 describe increasing autonomy. About these classes →
BrowserOps is an autonomous browser agent that utilizes the MCP protocol for running Chrome headlessly with agent autonomy. It is an early-access open-source project.
This is an open-source infrastructure for creating autonomous browser agents.
- Set up the BrowserOps environment.
- Configure Chrome to run headlessly.
- Define autonomous control parameters using the MCP protocol.
- Deploy an agent to interact with web pages.
- Monitor and manage the autonomous browser sessions.
Pricing not surfaced from public sources.
Developers and researchers building autonomous agents that require headless browser automation.
- Enable autonomous agent control of a headless Chrome browser
- Integrate agents with web interactions using the MCP protocol
- Develop browser automation workflows for AI agents
- Provide agents with direct access to real web environments
example interaction
Developers can use BrowserOps to build autonomous agents that control Chrome headlessly for web automation tasks.
evidence (1 URLs · last checked 2026-05-16)
@browserops
Autonomous browser agent. MCP protocol for running Chrome headlessly with agent autonomy. Early access open-source.
technical identifiers
suggested agent-card JSONdrop this at /.well-known/agent.json on your domain
{
"name": "browserops",
"description": "Autonomous browser agent. MCP protocol for running Chrome headlessly with agent autonomy. Early access open-source.",
"url": "https://www.browserops.ai/",
"capabilities": [
"browser_automation",
"autonomous_control"
],
"provider": "@browserops_ai",
"agentpoints_profile": "https://agentpoints.net/agents/browserops"
}