Start here: /v1/extract + Residential · Rotating

Automation & Scripting Solution

Cron, bots, and CI should call the extract API for a fresh endpoint — not a human clicking Generate. Pair it with rotating residential unless the session must stick.

This is machine-to-machine proxy ops. OpenClaw is for chat. Web Scraping API is for page HTML. Do not confuse the three.

API Center Purchase rotating traffic
Who it's for

Jobs that must mint IPs without a dashboard

SRE

Geo health-checks from cron.

RPA

Feed proxies into desktop automation.

QA nightlies

Non-office egress on a schedule.

Pipeline owners

Secrets in a manager, not a wiki.

Pain Points

Unbounded bots burn GB

Automation without caps is how packs empty overnight. Static/custom is only for bots that must keep cookies.

🔄

Stale cached endpoints

Bots reuse dead IPs.

💸

No concurrency cap

Parallelism × rotate = empty balance.

🔐

Tokens in git

Rotate immediately.

⚙️

Rotate mid-checkout

Cart bots need static, not this page’s default.

📋

Humans in the loop

Ops clicking Generate 50 times.

🤖

Letting MCP purchase

Keep write ops human.

What to buy

Extract API drives rotating residential

Recommended: /v1/extract plus rotating residential. Alternative: static/custom ports when the bot must hold a session. MCP is optional for pre-flight balance checks.

Product Billing Use it when…
Residential · Rotating Recommended for this workflow Pay per GB Recommended — independent requests, cron-friendly, pay per GB.
AI MCP Free MCP server tools Alternative helper — read-only balance/extract from CI, not a traffic SKU.
Recommended path

How to start (one recommended path)

Path A — Extract API + rotating (recommended)

Classic M2M.

  1. Store the API token in a secrets manager.
  2. Cron calls /v1/extract with geo filters.
  3. Inject proxy URL into the job.
  4. Alert on low balance; cap workers.
API Center →

Path B — Sticky bots on static ports

When rotation breaks the flow.

  1. If the bot checks out or stays logged in, stop using rotating.
  2. Lease static or custom ports.
  3. One port per worker ID.
  4. See Account / Browser solutions for session rules.
Static proxies →
Decision guide

Pick one — do not mix these on the same job

Use extract + rotating when

  • Each request is independent.
  • You control concurrency.
  • Targets allow automated access.

Use static/custom when

  • Cookies must survive.
  • The cart binds to IP.
  • You run fewer, warmer bots.
AI tools

Optional: MCP as a pre-flight

AI MCP can check balance before a large job. It is not the traffic product.

OpenClaw Skill

Natural-language endpoint generation and balance checks — read-only.

OpenClaw Skill →

AI MCP

IDE tools for extract, usage, and balance — Cursor, VS Code, Claude.

AI MCP →
Getting started

First-week checklist

FAQ

Common questions

Extract vs /v1/fetch?

Extract returns a proxy endpoint. Fetch returns page content (Web Scraping API).

Same as AI Integration?

That page is chat/IDE. This page is cron.

OpenClaw in cron?

Prefer extract API. Skill is for humans in chat.

Datacenter bots?

Only on permissive hosts — see Datacenter Crawling.

Purchase via API?

Keep purchases human-approved.

Resources

Go deeper

API Center Residential rotating AI integration Help Center

Point cron at /v1/extract, not the dashboard

Rotating residential for independent jobs. Static only if the bot must stay logged in.

API Center Purchase rotating traffic