4Bots — Help & Documentation

Quick Start

Choose your integration method.

4Bots supports two complementary approaches. Use MCP for structured tool discovery, x402 for pay-per-request without authentication, or both together.

🔌 MCP — Model Context Protocol

Best for: Agents that need to discover tools dynamically. Works with Hermes, Claude Code, Cline, OpenHands, and any MCP-compatible client.

Step 1: Add the MCP server

# With Hermes
hermes mcp add 4bots-status --url https://status.4bots.ai/mcp

# With Claude Code
npx -y @modelcontextprotocol/cli add-server 4bots-status \
  --url https://status.4bots.ai/mcp

# Manual: Point at the endpoint
https://{product}.4bots.ai/.well-known/mcp.json

Step 2: Discover tools

curl https://status.4bots.ai/tools/list
# Returns: Available tools, parameters, and descriptions

Step 3: Invoke a tool

curl https://status.4bots.ai/tools/call \
  -H "Content-Type: application/json" \
  -d '{"tool": "provider_status", "args": {"provider": "anthropic"}}'

Authentication: Provide an API key via X-API-Key header for paid tiers. Free tiers work without auth.

💳 x402 — HTTP Micropayments

Best for: Pay-per-request without accounts, API keys, or subscriptions. Fully autonomous agent payments in USDC on Base.

Step 1: Set up a wallet

# Python
from eth_account import Account
wallet = Account.create()
print(f"Address: {wallet.address}")
# Fund with USDC on Base: https://bridge.base.org

Step 2: Make a request

curl https://whois.4bots.ai/v1/whois/example.com
# Returns 402 with payment instructions if over free tier

Step 3: Parse 402 response

{
  "x402": {
    "price": "$0.002",
    "asset": "USDC",
    "network": "base",
    "payTo": "0x...",
    "scheme": "exact"
  }
}

Step 4: Pay and retry

# Using x402 Python library
from x402 import x402ClientSync
client = x402ClientSync(wallet)
response = client.get("https://whois.4bots.ai/v1/whois/example.com")
print(response.json())

No account needed: Just a wallet with USDC. Pay per request from $0.001. Test free on Base Sepolia.

Products

All 11 services. All live.

Click any product for detailed documentation, API reference, and pricing.

REST endpoints.

All products expose REST APIs at /v1/{action}. Works with or without MCP.

Common Pattern

GET /v1/{product}/{action}

All REST requests follow this pattern. Replace {product} with the service name and {action} with the specific operation.

curl https://whois.4bots.ai/v1/whois/example.com
curl https://fx.4bots.ai/v1/rates/USD
curl https://cleaning.4bots.ai/v1/clean?url=https://example.com

Headers

x402-authorization: For x402 payments (auto-handled by x402 libraries)
X-API-Key: For API key authentication (optional, for paid tiers)
Content-Type: application/json: For POST requests

Product Endpoints

GET /v1/whois/:domain

Domain intelligence: WHOIS + DNS + SSL + tech stack.

curl "https://whois.4bots.ai/v1/whois/4bots.ai"

GET /v1/recon/:domain

Full recon bundle: WHOIS + DNS + SSL + Certificate Transparency logs.

curl "https://recon.4bots.ai/v1/recon/4bots.ai"

GET /v1/pkgs/:ecosystem/:name

Package registry lookup across npm, PyPI, crates.io, and more.

curl "https://pkgs.4bots.ai/v1/pkgs/pypi/requests"

GET /v1/docpack/{library}

Compressed library documentation. Optimized for agent context windows.

curl "https://docs.4bots.ai/v1/docpack/fastapi?version=0.115.0"

GET /v1/feedhub/{feed_name}

Summarized feed items from RSS, news, and filings.

curl "https://feeds.4bots.ai/v1/feedhub/tsx-v-mining?limit=10"

POST /v1/digests/compress

Document summarization with configurable token budgets.

curl -X POST "https://digests.4bots.ai/v1/digests/compress" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/report.pdf", "budget_tokens": 2000}'

POST /v1/extracts/structured

Extract structured data from unstructured text using custom schemas.

curl -X POST "https://extracts.4bots.ai/v1/extracts/structured" \
  -H "Content-Type: application/json" \
  -d '{"text": "...", "schema": "mining-press-release"}'

FAQ

Common questions.

Do I need an account?

No. Free tiers work with no signup — just send a request. Paid tiers need an EVM wallet with USDC on Base. No email, no credit card, no KYC.

What is x402?

x402 is the HTTP-native micropayment protocol. When you hit a paid endpoint, the server returns a 402 status with payment instructions. Your agent pays USDC on Base and retries the request. No subscriptions, no minimums, no accounts.

What MCP clients work?

Any MCP 2026-07-28 compliant client:

Hermes: hermes mcp add 4bots-{product} --url https://{product}.4bots.ai/mcp
Claude Code: npx -y @modelcontextprotocol/cli add-server ...
Cline: Built-in MCP support
OpenHands: MCP plugin system
Custom agents: Point at /.well-known/mcp.json

Can I test for free?

Yes. All services have free tiers with daily limits. You can also test the full x402 payment flow on Base Sepolia testnet using free testnet USDC from the Coinbase CDP faucet.

What wallets work?

Any EVM-compatible wallet. For agents, you typically generate a keypair programmatically:

# Python
from eth_account import Account
wallet = Account.create()

# Load existing wallet
wallet = Account.from_key("0x...")

The wallet just needs a small USDC balance on Base network.

How do pricing tiers work?

Each product has a free tier (e.g., 10 requests/day) and a paid tier. Free tier uses no payment. Paid tier triggers x402 payment flow — your agent pays per request in USDC, from $0.001 to $0.005 depending on the service.

I'm getting a 402 error. What now?

A 402 means you've exceeded the free tier and need to pay. The response body contains payment instructions. Use an x402 library to handle the payment automatically, or manually sign an EIP-3009 authorization and POST it with your request.

How do I contact you?

Email [email protected]. We read every message.

Help & Documentation

Choose your integration method.

🔌 MCP — Model Context Protocol

💳 x402 — HTTP Micropayments

All 11 services. All live.

STATUS

WHOIS

FX

CLEANING

PAPERS

RECON

PKGS

DOCS

FEEDS

DIGESTS

EXTRACTS

LAWS