SpendPreflightCheck before your agent pays
A small, explicit decision between a payment quote and a signature.
Live features and staging previews are distinguished. Index coverage is not yet available.
Choose a starting point
Use HTTP for a direct screening call, MCP for an assistant tool, or the local SDK guard in the payment path. No SpendPreflight caller account, API key or OAuth is required. An agent still needs its own wallet and payment authorization to pay.
Three outcomes
Allow: proceed only within your policy. Hold: ask a human or explicit policy authority. Block: stop. A model deciding to call a screening tool does not enforce these outcomes; put the guard before signing.
Availability in this documentation
HTTP checks, signed preflight decisions, MCP and npm 0.2.0 are live. The Index interface and rules are deployed, but the crawler is disabled pending capacity checks: missing evidence stays unknown. Scout and Verified Seller remain staging previews. Python is not published on PyPI.
Public prices
| Route | Price | Purpose |
|---|---|---|
| GET /v1/check | $0.01 | Wallet/name screening and domain signals |
| POST /v1/preflight | $0.02 | Allow, hold or block plus reasons |
| GET /v1/endpoint | $0.005 · requires fresh indexed data | Cached unpaid endpoint observations |
| get_service_info / health / sample | Free | Reference and service state |