Skip to main content
Xintel serves one library of reports through two interfaces. The app gives people the full corpus and toolkit. The Agent API gives agents finished report bodies only.

​
People

A person can use Xintel three ways, and layer X on top:
  • Alpha (free) — the deployment’s shared Venice key covers inference while Alpha (free) mode is on. No login or wallet.
  • BYOK — bring your own Venice key (and optionally your own X developer credentials); calls bill your account.
  • Credits — prepaid USDC over SIWE, debited for paid in-app actions.
  • X (OAuth) — optional and additive: it unlocks your own accounts, publishing, and richer gathers, but never gates Alpha (free) or BYOK. See OAuth is additive.
Setup lives in Connections & billing.

​
Agents

Agents skip all of that. No OAuth, no session, no secret. The flow is:
  1. Browse the free list and per-handle menu.
  2. Pay with x402 only when requesting report bodies.
  3. Receive IntelReportSnapshot[] and a small response envelope — nothing else from the corpus.
The complete purchase flow is on Buy a report. The default route is the CLI — npx @xintel/agent buy --username <handle> --select all runs the whole payment loop. MCP is second; the raw HTTP flow is the fallback for environments that cannot run Node.

​
Why the split exists

Agents buy reports that a team already chose to publish to the shared library. They cannot buy the raw material — live timelines, full graphs, or the complete corpus. That corpus is reachable only through the app or first-party access, never through the paid agent product.