Ask chat or your IDE for a geo-filtered proxy endpoint or a usage number β without pasting dashboard passwords into Slack. OpenClaw and MCP are read-only.
This page is AI tooling. It does not replace rotating residential or Web Scraping API. Those stay the products that actually fetch or egress.
Expose extract/balance tools to internal agents.
Skip the admin UI for a country endpoint.
Demo integrations with MCP.
Tool calls instead of copy-paste.
Skill and MCP will not choose residential vs API. You still pick the product. AI only operates the account you already have, read-only.
IDE β dashboard β Slack.
Incident waiting to happen.
Undocumented extract params.
Slows sprints.
Never let an agent purchase.
'How do I get a DE endpoint?'
Recommended: OpenClaw Skill for chat; AI MCP for IDE. Optional: Web Scraping API fetch tools if the agent must return HTML. Do not enable purchase tools.
| Product | Billing | Use it when⦠|
|---|---|---|
| OpenClaw Skill Recommended | Included with proxy account | Recommended for chat β natural-language endpoints and balance. |
| AI MCP | Free MCP server tools | Recommended for Cursor/VS Code/Claude Desktop β typed tools. |
Chat-native teams.
Integration sprints.
OpenClaw Skill and AI MCP are the products. Web Scraping API and proxy IP remain separate purchases.
Natural-language endpoint generation and balance checks β read-only.
OpenClaw Skill βNo β Skill and MCP are read-only.
No.
Yes, fetch tools β still a separate credit pack.
CS is live chat help. MCP is structured tools.
Cursor, VS Code, Claude Desktop β see product docs.
Free to connect. You still pay for the proxy or API usage the tools observe.