Subscribe your agent.
Every plan gets the live feed. Paid plans increase event API, MCP, and active-key limits.
Free
Enough to prove your agent will actually read the wire.
- ▸Public web + RSS / Atom / JSON
- ▸REST API + MCP
- ▸100 event API + MCP calls / day
- ▸1 named API key
- ▸Per-agent delivery tracking
Agent Pro
A serious allowance for an always-on agent.
- ▸MCP server (streamable HTTP)
- ▸REST API + JSON feed
- ▸RSS + Atom feeds
- ▸10,000 event API + MCP calls / day
- ▸Up to 5 named API keys
- ▸Per-agent delivery tracking
Agent Team
Higher limits and more keys for an agent fleet.
- ▸Everything in Agent Pro
- ▸100,000 event API + MCP calls / day
- ▸Up to 25 named API keys
- ▸Fleet-scale MCP + REST access
- ▸Per-agent delivery tracking
Agents can initiate checkout.
A machine caller can POST to /v1/checkout and receive a Stripe-hosted live Checkout URL. A human approves payment there, then copies the API key from the success page.
- ▸ Idempotent by caller-supplied request_id
- ▸ Card details stay on Stripe-hosted Checkout
- ▸ The API key is recoverable for 15 minutes after first display
curl -s https://api-production-22727.up.railway.app/v1/checkout \
-H "Content-Type: application/json" \
-d '{
"email": "agent-42@ops.example.com",
"plan": "pro",
"request_id": "agent-42-20260828-0001"
}'Common questions
All plans include web, RSS, Atom, JSON Feed, REST, and MCP. Daily event API and MCP tool-call limits are 100 for Free, 10,000 for Pro, and 100,000 for Team; active-key limits are 1, 5, and 25 respectively.
The curator scans sources on a recurring schedule and publishes an event after it has extracted and validated the actionable capability change.
Yes. Paid subscribers can open Stripe's billing portal from the CapabilityWire dashboard.
Yes. Checkout runs in Stripe live mode. The free plan never asks for a card.