Docs

Connect an agent to Clawifi in four steps.

Connect an AI agent to Clawifi in four steps, MCP first: get a key, install, add it to Claude Code, Codex, Cursor or any MCP client, and make the first call.

MCP first

Quickstart.

  1. 1. Get a key

    Create an account at /signup. The Free plan includes 1,000 credits a month. Verify your email, then copy the API key the console shows you. It is shown once.

    https://clawifi.dev/signup
  2. 2. Install

    One package installs the MCP server (clawifi-mcp) and the CLI. It needs Python 3.11 or newer.

    pip install clawifi
  3. 3. Add to your client

    Add Clawifi to your agent with your key. Choose your client below; each line is all it needs.

  4. 4. First call

    Ask your agent to search or read a page (for example "search the web for the Model Context Protocol spec"), or check the key from a terminal first.

    CLAWIFI_API_KEY=your_key clawifi quicktest --url https://example.com

Install

Clients.

Claude Code

claude mcp add clawifi -e CLAWIFI_API_KEY=your_key -- clawifi-mcp

Codex

codex mcp add clawifi --env CLAWIFI_API_KEY=your_key -- clawifi-mcp

Cursor

{ "mcpServers": { "clawifi": { "command": "clawifi-mcp", "env": { "CLAWIFI_API_KEY": "your_key" } } } }

Claude Desktop

{ "mcpServers": { "clawifi": { "command": "clawifi-mcp", "env": { "CLAWIFI_API_KEY": "your_key" } } } }

Hermes

CLAWIFI_API_KEY=your_key clawifi mcp config

Any MCP client

CLAWIFI_API_KEY=your_key clawifi mcp config

HTTP

Errors.

401 Unauthorized

The key or session is missing, wrong or expired ("Invalid API key", "API key has expired"). Create a new key in the console.

402 Not enough credits

The balance does not cover the call's minimum. The message names both: "Insufficient Clawifi credits: needed 6, balance 2". Nothing is charged. Send the same call with "dry_run": true to check before you run it.

403 Account suspended

The account is suspended while a payment dispute is open. Keys stop working; you can still sign in and read the console. Email [email protected].

403 plan_required

The feature needs a higher plan, for example hosted browser render (Pro or Scale) or brute-force subdomains (any paid plan). error.code is plan_required.

409 Conflict

Something already exists or changed: a second plan checkout ("you already have a plan, change it instead"), a plan change that cannot apply yet, or an email that already has an account.

429 Too many requests

Too many calls at once for your plan, or a monthly cap (hosted render minutes) is used up. Wait the seconds in the Retry-After header and retry; a monthly cap says when it resets.

Pricing

Credits per operation.

search: 1 per call

search, plain fetch/scrape, article extract, package/dataset/code/archive/academic lookup, single OSINT lookup, social reads

browser_render: 3 per call

browser render, or a fetch/scrape that escalates to the browser; a Reddit thread the browser could not open and the Wayback Machine copy answered counts as rendered (the renders ran), while a page reached in the archive without a render costs the base call

pdf: 2 per started 50 pages

in place of the base call: 2 for 1-50 pages, 4 for 51-100

llm_extract: 4 per call

an extract that runs a language model; hosted extraction is deterministic today

map: 1 per started 10 URLs returned

at least 1

crawl: 1 per page

+2 per page that needed JS rendering; at least 1

monitor_check: 1 per check

3 with the browser

osint_recon_bundle: 5 per call

domain recon, email recon, username sweep

research: 30 per call

5 per source searched + 10 per page read, at least 30, at most 300

research_plan: 5 per call

cloud_render: 6 per started browser-minute

Pro and Scale plans (500 and 2,500 minutes a month); at least 6. Renders JavaScript-heavy pages in a hosted browser. It does not bypass bot protection or CAPTCHAs.

passages: 0 per call

query/top_k on fetch, scrape and browse add nothing

playground: 0 per call

Read these docs as Markdown