Raw HTTP (fallback)

This is the fallback route. The default is the CLI: npx @xintel/agent buy --username <handle> --select all buys a report in one command and runs the whole 402 → sign → retry loop, with no x402/viem to install. Use the raw HTTP flow below only where Node is unavailable. When the raw route fails in a given environment, the CLI is the resolution.

The three routes, in order

Route	Setup	When to use it
1. CLI (`npx`) — the default	One command; nothing to install. See CLI & MCP.	Almost every agent.
2. MCP server	One-time `mcp.json` entry, then call tools. See CLI & MCP.	Persistent hosted agents (Cursor, Claude Desktop).
3. Raw HTTP (this page) — fallback	Implement `list → menu → 402 → sign → retry` yourself.	Environments that can’t run Node.

The Agent API is plain HTTP with one payment header. Browsing is free; you pay only when you request report bodies. Requirements: a wallet funded with USDC on Base to settle payments. Browsing is free and needs no wallet. Base URL: https://xintel.aispace.bot.

GET /api/intel/list                        → handles with shared reports (free)
GET /api/intel/reports?username=AskVenice   → report menu: ids + dates (free)
GET …&select=all                            → 402 with a payment challenge
Retry with X-402-Payment (settled)          → IntelReportSnapshot[]

List available handles

curl -sS "https://xintel.aispace.bot/api/intel/list"

{
  "configured": true,
  "entries": [
    {
      "username": "AskVenice",
      "displayName": "…",
      "followers": 12345,
      "postCount": 40,
      "reportCount": 3,
      "gatheredAt": "2026-07-20T12:00:00.000Z"
    }
  ]
}

Pick a handle by username. reportCount tells you how many reports it has.

Read the free menu

Request a handle with no select to get report metadata only — no bodies, no charge.

curl -sS "https://xintel.aispace.bot/api/intel/reports?username=AskVenice"

{
  "username": "AskVenice",
  "reportCount": 2,
  "reports": [
    {
      "id": "rpt_…",
      "createdAt": "2026-07-20T12:00:00.000Z",
      "model": "…",
      "postCount": 40,
      "dateRange": { "from": "…", "to": "…" }
    }
  ]
}

Request bodies and receive a 402

Add select=all (or select=range). Without a payment header the response is 402 with an x402 challenge — accepts describes the payment, extensions gives unitPriceUsd, reportCount, and select.

curl -sS -i \
  "https://xintel.aispace.bot/api/intel/reports?username=AskVenice&select=all"

Settle and retry

Turn the challenge into a payload and resend the same URL with it attached:

curl -sS \
  -H "X-402-Payment: $PAYMENT" \
  "https://xintel.aispace.bot/api/intel/reports?username=AskVenice&select=all"

Point a standard x402 client at a funded Base USDC wallet and it produces $PAYMENT from the 402 for you. See How to pay for the exact call.Success returns { username, select, reportCount, chargedUsd, reports: IntelReportSnapshot[] }. (X-Payment is accepted as a fallback header.)

Buy a subset with range

Use select=range to buy part of a handle’s history — by id, or by a createdAt window (ISO strings, compared lexicographically):

# By ids
curl -sS -i \
  "https://xintel.aispace.bot/api/intel/reports?username=AskVenice&select=range&ids=rpt_a,rpt_b"

# By createdAt window
curl -sS -i \
  "https://xintel.aispace.bot/api/intel/reports?username=AskVenice&select=range&from=2026-01-01T00:00:00.000Z&to=2026-12-31T23:59:59.999Z"

The charge is $0.01 × N for the N matching reports.

Buy a report — the complete flow on one page
CLI & MCP — the default route: one command instead of all of the above
Auth and payment — the 402 challenge and payment headers
Reports — every parameter and the snapshot schema
Errors — status codes and error strings

Overview

Using the app

Agent API

Access models

Reference

Raw HTTP (fallback)

The three routes, in order

Next

​The three routes, in order

​Next

The three routes, in order

Next