SoapBox for AI Agents

Why connect to SoapBox

Connect your agent

The server speaks MCP over Streamable HTTP (JSON-RPC 2.0). Free read tools — including ask_ora, verify_scripture, and browse_catalog — need no API key; just point your client at the endpoint. A key is required only for buying sermons or acting on a user's behalf (prayer, giving).

Claude Desktop / Claude Code (remote MCP)

{
  "mcpServers": {
    "soapbox-faith": {
      "type": "http",
      "url": "https://foyekanoxpnkydoibaas.supabase.co/functions/v1/faith-mcp"
    }
  }
}

With Claude Code you can also add it in one line:

claude mcp add --transport http soapbox-faith \
  https://foyekanoxpnkydoibaas.supabase.co/functions/v1/faith-mcp

To use key-gated tools (purchases, prayer, giving), add an Authorization header with your SoapBox key: "headers": { "Authorization": "Bearer <your-key>" }.

Any MCP client (raw JSON-RPC)

curl -X POST https://foyekanoxpnkydoibaas.supabase.co/functions/v1/faith-mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"ask_ora",
                 "arguments":{"question":"What does the Bible say about hope?"}}}'

Tools

FREE = no key needed   KEY = needs a SoapBox key

Resources

The server also exposes the catalog as an MCP resource for clients that browse resources directly:

Buying content & "agent orders"

Free content is readable directly. Paid sermons return a preview, a price, and a web_url; an agent unlocks full access either by purchasing with prepaid marketplace credits (via purchase_sermon / purchase_bundle, which needs a key) or by sending the user to the web_url to complete the purchase on the web. SoapBox is the Merchant of Record on content sales; the pastor keeps 70% of net revenue. Donations are always passthrough — 100% to the church, no cut.

Pay programmatically with x402 (USDC on Base)

For agents that have no SoapBox account and no prepaid credits, SoapBox speaks x402 — Coinbase's open HTTP-402 + USDC payment protocol (docs.cdp.coinbase.com/x402). Pay per-call in USDC on Base, get the content back in the same exchange. Same economics as every other content sale: the church keeps 70% of net, SoapBox 30%; donations are always separate and 100% passthrough.

How it works (two steps, per the x402 spec)

1. Request the resource with no payment → you get back an HTTP 402 with the standard x402 accepts requirements (amount in USDC atomic units, the asset, network: "base", and SoapBox's payTo receive address):

curl -i -X POST https://foyekanoxpnkydoibaas.supabase.co/functions/v1/x402-faith \
  -H "Content-Type: application/json" \
  -d '{"sermon_id":"<SERMON_ID>"}'

HTTP/1.1 402 Payment Required
{
  "x402Version": 1,
  "accepts": [{
    "scheme": "exact",
    "network": "base",
    "maxAmountRequired": "990000",        // USDC atomic units (6 decimals) — $0.99
    "asset": "0x833589fcD6eDb6E08f4c7C32D4f71b54bdA02913",   // native USDC on Base
    "payTo": "0x…",                        // SoapBox's Base receive address
    "resource": "https://…/x402-faith?sermon_id=<SERMON_ID>",
    "description": "SoapBox sermon transcript: …",
    "maxTimeoutSeconds": 300
  }],
  "error": "X-PAYMENT header required"
}

2. Pay the USDC on Base, then retry with the X-PAYMENT header (a base64-encoded JSON payload carrying your broadcast Base tx hash). SoapBox verifies the on-chain transfer to its receive address, grants access, records the sale, and returns the transcript plus an X-PAYMENT-RESPONSE settlement receipt:

curl -i -X POST https://foyekanoxpnkydoibaas.supabase.co/functions/v1/x402-faith \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: $(echo -n '{"txHash":"0x…"}' | base64)" \
  -d '{"sermon_id":"<SERMON_ID>"}'

HTTP/1.1 200 OK
X-PAYMENT-RESPONSE: <base64 settlement receipt>
{ "sermon_id": "…", "transcript": "…", "paid": true }

Works for both sermons (sermon_id) and bundles (bundle_id). Gasless EIP-3009 "exact" payments via an x402 facilitator are also accepted. Over MCP, the pay_with_x402 tool wraps this exact flow. One on-chain transaction settles one purchase (replay-safe).

Scripture served is public-domain KJV only; licensed translations are never returned. Pastor content is owner-consented. ORA is a study aid, not a substitute for a pastor, counselor, or medical professional.