What it does
An agent creates a feed once: pick an endpoint, a schedule or a trigger, and a delivery path. BitFeed watches the live data (sharing the same cache as on-demand calls) and delivers only when it is due or when the condition hits, then deducts the endpoint's usual price from a prepaid balance. Trigger checks themselves are free.
Scheduled and trigger feeds
Schedules run hourly or daily (15-minute minimum). Triggers fire when the data moves:
Alert when Bitcoin moves a set percent inside a window, e.g. 3% within an hour.
Alert when the price crosses above or below a USD level. Fires once per crossing, not on every tick while it stays past the line.
Push when a new 8-K, 10-Q or 10-K appears for a US ticker. Evaluating the trigger is free; you pay the stock_filings price per delivery.
Push when a new National Weather Service alert appears for a location.
Push when FAA delays at an airport pass a set number of minutes, or when a ground stop or closure is published.
Pricing
There is no extra BitFeed fee. Each successful delivery (webhook or mailbox) costs the same as calling that endpoint once. Examples at current prices: btc_price 10 sats · $0.01 USDC, btc_price_fresh 30 sats · $0.025 USDC, weather_alerts 10 sats · $0.01 USDC, airport_delays 10 sats · $0.01 USDC. Top up with a Lightning invoice (100 sats minimum) or with USDC on Base over x402 ($0.10 minimum). The two balances are separate: a delivery is charged in sats when your sats cover it, otherwise in USDC at the endpoint's USDC price. The feed pauses when neither balance can cover the next delivery, and resumes when you top up.
Webhooks and mailbox
A webhook is an HTTPS POST, signed with HMAC-SHA256 and a per-feed secret that is shown only once. Headers include X-BitFeed-Signature, X-BitFeed-Timestamp, X-BitFeed-Event-Id and X-BitFeed-Idempotency-Key. Failed deliveries retry with backoff. Agents without a public URL can use the mailbox and poll or acknowledge items, which are kept for 72 hours. Private or internal webhook addresses are rejected.
curl
The first create without a token opens the account and returns a btf_ token. Store it; it is not shown again.
# Create a BTC 3% move feed (new account)
curl -sS -X POST https://api.bittuitive.ai/api/v1/feeds \
-H 'Content-Type: application/json' \
-d '{"endpoint":"btc_price","mode":"trigger",
"trigger":{"type":"btc_move","percent":3,"window_seconds":3600},
"mailbox":true}'
# Top up (pay the invoice, then GET the check_url)
curl -sS -X POST https://api.bittuitive.ai/api/v1/feeds/topup \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{"amount_sats":100}'
# Top up with USDC on Base (x402): the first call returns 402 with the payment
# requirements; sign accepts[0], then repeat the call with PAYMENT-SIGNATURE (or X-PAYMENT)
curl -sS -X POST https://api.bittuitive.ai/api/v1/feeds/topup \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{"amount_usd":"1.00"}'
# Mailbox
curl -sS -H "Authorization: Bearer $TOKEN" \
https://api.bittuitive.ai/api/v1/feeds/mailbox
MCP
Add https://api.bittuitive.ai/mcp as a remote MCP server. BitFeed tools: create_feed, list_feeds, get_feed, update_feed, pause_feed, resume_feed, delete_feed, get_balance, topup, get_mailbox, ack_mailbox. Pass bitfeed_token after the first create_feed.
# tools/call create_feed (no token → new account)
{
"endpoint": "btc_price",
"mode": "schedule",
"interval": "hourly",
"mailbox": true
}
# tools/call create_feed — threshold alert
{
"bitfeed_token": "btf_…",
"endpoint": "btc_price",
"mode": "trigger",
"trigger": {"type": "btc_threshold", "above": 120000, "below": 90000},
"webhook_url": "https://agent.example/hooks/bitfeed"
}