CLI & MCP

Buy a report carries the complete flow — CLI, MCP, and raw HTTP — on one page. This page expands the CLI and MCP routes.

The CLI is the default route for an agent purchase. @xintel/agent is one package that runs as both a CLI and an MCP server, and it carries the entire payment step — no x402/viem install, no ESM/CJS mismatch, no 0x-prefix or x402Version-1-vs-2 handling. Where Node is available, the CLI is the correct route: it is the quickest, and it removes every failure mode the raw route exposes. The raw HTTP flow is the fallback for environments that cannot run Node.

The three routes, in order

Route	Setup	When to use it
1. CLI (`npx`) — the default	One command; nothing to install. Set `XINTEL_AGENT_KEY` in env.	Almost every agent — anything that can shell out.
2. MCP server	One-time `mcp.json` entry + restart, then call tools directly.	Persistent hosted agents (Cursor, Claude Desktop).
3. Raw HTTP + x402/viem — fallback	Install libs, sign EIP-3009 yourself, mind the version gotcha.	Only when you cannot run Node. See the raw HTTP flow.

Buys shared report bodies only — never profile, posts, or edges. Same product and pricing as the HTTP API ($0.01 USDC per report on Base).

CLI (npx)

Nothing to install — npx fetches and caches it:

# free browsing (no wallet)
npx @xintel/agent list
npx @xintel/agent menu --username AskVenice

# paid ($0.01 USDC per report on Base)
export XINTEL_AGENT_KEY=0x<base-wallet-private-key-funded-with-usdc>
npx @xintel/agent buy --username AskVenice --select all
npx @xintel/agent buy --username AskVenice --select range --ids <id1>,<id2>

# range also accepts a createdAt window (ISO strings), on its own or with --ids
npx @xintel/agent buy --username AskVenice --select range --from 2026-07-01T00:00:00.000Z --to 2026-07-31T23:59:59.999Z

Add --json to any command for the raw response. The buy command runs the full 402 → sign → retry loop and prints the delivered reports.

MCP server

Add Xintel to any MCP-aware host (Cursor, Claude Desktop) — the same package, started with the mcp subcommand:

{
  "mcpServers": {
    "xintel": {
      "command": "npx",
      "args": ["-y", "@xintel/agent", "mcp"],
      "env": { "XINTEL_AGENT_KEY": "0x<base-wallet-private-key>" }
    }
  }
}

Tools exposed:

Tool	Paid?	Purpose
`xintel_list`	free	list usernames with shared reports
`xintel_menu`	free	list a username’s report menu (ids, dates, model)
`xintel_purchase`	`$0.01`/report	buy report bodies — handles the 402/sign/retry loop internally

Environment

Variable	Required for	Description
`XINTEL_AGENT_KEY`	`buy` / `xintel_purchase`	Base wallet private key funded with USDC. Read from env only — never a CLI flag. The client runs locally; your key never touches Xintel’s servers.
`XINTEL_BASE_URL`	optional	Override the API base (default `https://xintel.aispace.bot`).

When to use what

CLI (npx) — the default. Best for scripts, cron, or agent frameworks (LangChain, CrewAI) that shell out. Zero setup per run.
MCP — for persistent hosted agents (Cursor, Claude Desktop). One-time mcp.json entry, then the agent calls tools directly.
Raw HTTP — the fallback, for environments that can’t run Node. See the raw HTTP flow.

All three hit the same endpoints and the same $0.01/report pricing.

Overview

Using the app

Agent API

Access models

Reference

The three routes, in order

CLI (npx)

MCP server

Environment

When to use what

​The three routes, in order

​CLI (npx)

​MCP server

​Environment

​When to use what

The three routes, in order

CLI (npx)

MCP server

Environment

When to use what