# BrowserAct vs XCrawl (slim)

> BrowserAct scores 46 (D) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/browseract-vs-xcrawl.md (~4,900 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/compare/browseract-vs-xcrawl.json · canonical https://www.anchorterminal.com/compare/browseract-vs-xcrawl
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

BrowserAct scores 46 (D) on agent readiness against XCrawl's 30.4 (F), and leads in 6 of 7 scored categories. XCrawl leads on agent ergonomics. Both do scraping.

- BrowserAct: D 46, rank #1264 of 1563 · https://www.anchorterminal.com/tools/browseract.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- BrowserAct, good for Teams that want no-code, prompt-built scrapers an agent can rerun on a schedule. Ahead on Reliability, 23 against 15; Schema & documentation, 76 against 35; Security & auth, 41 against 18; Payments & pricing, 38 against 30; Maintenance & community, 61 against 17.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints. Ahead on Agent ergonomics, 59 against 49. Also Runs on your own machine; Free to start without a card.

| Category | BrowserAct | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 23 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 76 | 35 |
| Agent ergonomics (13%) | 49 | 59 |
| Security & auth (14%) | 41 | 18 |
| Payments & pricing (10%) | 38 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 61 | 17 |
| Transparency & trust (7%) | 44 | 43 |

| Fact (where they differ) | BrowserAct | XCrawl |
| --- | --- | --- |
| Vendor | Hongkong Ziniao Technology Co., Limited | XCrawl |
| Hosted endpoint | `https://mcp.browseract.com/mcp/` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, stdio |
| Tools exposed | none | 7 |
| llms.txt | yes | no |
| Last release | 2026-11-05 | 2026-04-13 |
| Terms last updated | 2025-05-15 | no date given |
| Privacy policy last updated | 2025-05-15 | no date given |
| Terms restrict automated access | yes | not found in the text |

Why the edge:
- Maintenance & community, BrowserAct +44: BrowserAct 61 (browser-act-cli 1.6.2 on 5 November 2026, read from PyPI's release feed (30).); XCrawl 17 (The newest dated releases are the Python SDK 1.1.2 on PyPI and the last xcrawl-sdk commits, both 13 April 2026, 221 days ago (0 of 30).)
- Schema & documentation, BrowserAct +41: BrowserAct 76 (An OpenAPI 3.0.3 document behind the API reference (25).); XCrawl 35 (No OpenAPI or other machine-readable spec found, and the MCP package is closed source, so its tool schemas couldn't be read (0 of 25).)
- Security & auth, BrowserAct +23: BrowserAct 41 (One account-wide API key type, revocable and listed with last-used time, but without scopes or expiry (18).); XCrawl 18 (A plain bearer API key from the dashboard with no scopes, and the MCP guide says to reissue an invalid key there (20).)
- Agent ergonomics, XCrawl +10: BrowserAct 49 (Graded on the API, since the MCP tool list isn't published.); XCrawl 59 (7 MCP tools per the Claude Code guide, compact by name and description, though the definitions themselves couldn't be read (22 of 25).)
- Reliability, BrowserAct +8: BrowserAct 23 (Hosted reading.); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Payments & pricing, BrowserAct +8: BrowserAct 38 (No x402, MPP or L402 (0).); XCrawl 30 (No x402, MPP or L402 (0).)
