Report access

This page carries the entire agent purchase flow: three routes, the payment handshake, the response shape, and the errors. No other page is required to complete a transaction. Base URL: https://xintel.aispace.bot OpenAPI: https://xintel.aispace.bot/openapi.json — machine catalog of this API (what Xintel reports are, paths, pricing handshake). Paste into an x402 marketplace import or codegen tool. Product: shared report bodies only — never profile, posts, or edges. Price: $0.01 USDC × N reports on Base (chain 8453). The live unit price is extensions.unitPriceUsd in the 402. Paid steps require a Base wallet funded with USDC. Browsing is free.

Routes

Three routes reach the same endpoints at the same $0.01/report price. Use the first one the environment supports.

Route	Environment	Setup
1. CLI — default	Can run Node	One `npx` command; nothing to install
2. MCP	Persistent hosted agent (Cursor, Claude Desktop)	One `mcp.json` entry, then call tools
3. Raw HTTP — fallback	Cannot run Node	Implement the payment loop directly

The CLI is the default: it runs the full payment loop and removes the failure modes of the raw route — no x402/viem install, no ESM/CJS mismatch, no 0x-prefix or x402Version handling. When the raw route fails in a given environment, the CLI is the resolution, not a workaround.

Route 1 — CLI (default)

One command buys a report. npx fetches and caches the package; nothing is installed. The CLI runs the entire 402 → sign → retry loop.

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

# 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 <handle> --select all

# buy a subset by id
npx @xintel/agent buy --username <handle> --select range --ids <id1>,<id2>

# buy a subset by createdAt window (ISO strings)
npx @xintel/agent buy --username <handle> --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. XINTEL_AGENT_KEY is read from the environment only, never a flag. The client runs locally; the key never reaches Xintel’s servers. This is the complete flow. The sections below cover the other two routes and the shared reference detail.

Route 2 — MCP

For persistent hosted agents, add the same package as an MCP server. One-time setup, then call the tools directly:

{
  "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

Route 3 — Raw HTTP (fallback)

For environments that cannot run Node. Same endpoints and price as the CLI, with the 402 → sign → retry loop implemented directly.

Steps

GET /api/intel/list — pick a username (free, no auth).
GET /api/intel/reports?username={u} — read the menu: id, createdAt, model, dateRange (free, no auth).
Choose a selection:
- All: …&select=all
- Range: …&select=range&ids=a,b and/or from= / to= (ISO, compared against createdAt).
On the 402: read accepts[0] — network (eip155:8453), asset (USDC), amount (base units, 6dp), payTo.
Pay, then resend the identical URL with X-402-Payment: <payload> (or X-Payment).
On 200: use reports[] — each is an IntelReportSnapshot. Body: { username, select, reportCount, chargedUsd, reports }.

The 402 challenge

{
  "x402Version": 2,
  "error": "Payment required",
  "accepts": [
    {
      "protocol": "x402",
      "version": 2,
      "network": "eip155:8453",
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "amount": "10000",
      "payTo": "0x…"
    }
  ],
  "extensions": {
    "chainId": 8453,
    "tokenDecimals": 6,
    "unitPriceUsd": 0.01,
    "reportCount": 1,
    "select": "all",
    "resource": "/api/intel/reports?username=…"
  }
}

amount is USDC base units (6 decimals — 10000 = $0.01). The asset is USDC on Base (chain 8453). payTo is the deployment’s receiver wallet.

Paying (step 5)

Use a standard x402 client with a funded Base USDC wallet. It reads accepts[0], signs, and produces the header. The underlying instrument is an EIP-3009 TransferWithAuthorization for USDC on Base (USDC only — no gas).

npm install x402 viem

import { createPaymentHeader } from 'x402/client'
import { privateKeyToAccount } from 'viem/accounts'

// challenge = the parsed 402 JSON body; url = the same URL that returned it
const accept = challenge.accepts[0]
const signer = privateKeyToAccount(process.env.AGENT_PRIVATE_KEY)

// NOTE: the 402 challenge envelope is x402Version 2, but the payment *payload*
// must be built as x402Version 1 — pass 1 as the second argument here.
// Sending a v2 payload is rejected with 402 `Invalid input` on x402Version.
const payment = await createPaymentHeader(signer, 1, {
  scheme: 'exact',
  network: 'base',
  maxAmountRequired: accept.amount,      // USDC base units (6dp)
  resource: challenge.extensions.resource,
  description: 'Xintel report bodies',
  mimeType: 'application/json',
  payTo: accept.payTo,
  maxTimeoutSeconds: 300,
  asset: accept.asset,
  extra: { name: 'USD Coin', version: '2' },
})

const res = await fetch(url, { headers: { 'X-402-Payment': payment } })
const body = await res.json()
// { username, select, reportCount, chargedUsd, reports: IntelReportSnapshot[] }

Build the payment from the latest 402 response — never hardcode amount, payTo, or asset.

Response shape (all routes)

A successful purchase returns:

{
  "username": "AskVenice",
  "select": "all",
  "reportCount": 2,
  "chargedUsd": 0.02,
  "reports": [ /* IntelReportSnapshot[] */ ]
}

chargedUsd is the required amount (unit × N), not the settled amount — overpayment is not reflected here. Each IntelReportSnapshot carries id, createdAt, model, synthesisSettings, meta, computed analytics, AI narrative, an optional changeSummary, and previousReportId. Treat unknown fields as forward-compatible.

Constraints

These routes never return bundle/corpus fields (profile, posts, edges).
Do not reuse a nonce / payment id (409 payment_already_used).
Send the payment on the identical URL that returned the 402.

Errors

400 bad query · 402 pay and retry (or insufficient_payment) · 404 unknown handle or empty range · 409 payment reused · 501 settlement not configured · 502 upstream/storage failure · 503 store not configured. A bare 402 with no settled retry is the normal payment handshake, not an error — read accepts and extensions, pay, then retry.

Reference

The pages above complete a purchase. These expand individual areas:

CLI & MCP — additional CLI and MCP options
Raw HTTP — the fallback flow, step by step
Auth and payment · Reports schema · Errors · Pricing

Machine index

Use the site’s /llms.txt, /llms-full.txt, and per-page .md exports. Agent rules are also injected via markdown.instructions in docs.json.

Overview

Using the app

Agent API

Access models

Reference

Routes

Route 1 — CLI (default)

Route 2 — MCP

Route 3 — Raw HTTP (fallback)

Steps

The 402 challenge

Paying (step 5)

Response shape (all routes)

Constraints

Errors

Reference

Machine index

​Routes

​Route 1 — CLI (default)

​Route 2 — MCP

​Route 3 — Raw HTTP (fallback)

​Steps

​The 402 challenge

​Paying (step 5)

​Response shape (all routes)

​Constraints

​Errors

​Reference

​Machine index

Routes

Route 1 — CLI (default)

Route 2 — MCP

Route 3 — Raw HTTP (fallback)

Steps

The 402 challenge

Paying (step 5)

Response shape (all routes)

Constraints

Errors

Reference

Machine index