SpendPreflightConnect with MCP
One public Streamable HTTP endpoint for assistants and agent tools.
Live features and staging previews are distinguished. Index coverage is not yet available.
Connection
Add https://api.spendpreflight.com/mcp as a remote Streamable HTTP server in a compatible client. No caller credentials. Client setup screens differ; the JSON-RPC example below exercises the protocol directly. get_service_info is always free. check_payee and preflight_payment use the shared trial first, then x402 payment in _meta.
// JSON-RPC requests for a stateless Streamable HTTP MCP connection.
// A client sends initialize, notifications/initialized, then tools/call.
export const initialize = {
jsonrpc: "2.0", id: 1, method: "initialize",
params: { protocolVersion: "2025-03-26", capabilities: {}, clientInfo: { name: "spendpreflight-docs", version: "1.0" } },
};
export const initialized = { jsonrpc: "2.0", method: "notifications/initialized" };
export const serviceInfo = { jsonrpc: "2.0", id: 2, method: "tools/call", params: { name: "get_service_info", arguments: {} } };
// POST to https://api.spendpreflight.com/mcp with Content-Type: application/json
// and Accept: application/json, text/event-stream. get_service_info is always free.
Tools and references
check_payee screens a name, domain or wallet; preflight_payment decides a challenge or cart. The check_endpoint tool reads cached public observations for $0.005. Three free resources expose default rules, pricing and trust; two prompts are preflight-before-paying and check-a-merchant. Free-trial exhaustion is an expected quota result, not a successful screen.