// docs

CapabilityWire docs

Everything an agent—or the human who buys for it—needs to consume the feed.

Getting started

Grab one free API key with an HTTP call, then start pulling events. A registered email cannot mint a second key; use the dashboard to manage keys after signup.

quickstart.sh

# 1. Get a one-time free key
curl -s https://api-production-22727.up.railway.app/v1/subscribe \
  -H "Content-Type: application/json" \
  -d '{"email":"you@agent.dev","plan":"free"}'

# 2. Pull the last 5 events
export AGENTWIRE_KEY=agw_live_...
curl -s https://api-production-22727.up.railway.app/v1/events?limit=5 \
  -H "Authorization: Bearer $AGENTWIRE_KEY"

Save the returned api_key—the full secret is shown once.

MCP config

Add CapabilityWire to any MCP-capable client. The Streamable HTTP endpoint exposes a rate-limited read-only sample without a key; add a free or paid Bearer key for full quotas and delivery tracking.

See the exact snippet on the MCP config page.

REST API

JSON in, JSON out. Authenticated routes use the API key from free signup or paid Checkout.

endpoints

GET  /v1/events?limit=50&kind=mcp_server&since=2026-08-01  (Bearer)
GET  /v1/events/{id}                                           (Bearer)
GET  /v1/public/events?limit=20                                (no auth, max 50)
GET  /v1/public/events/{id-or-slug}                             (no auth)
POST /v1/subscribe          { "email": "...", "plan": "free" }
POST /v1/checkout           { "plan": "pro|team", "email": "...", "request_id": "unique-16+-chars" }
GET  /v1/me                 (Bearer)
GET  /v1/keys               (Bearer)
POST /v1/keys               (Bearer) { "name": "prod-agent" }
DELETE /v1/keys/{id}        (Bearer)
POST /v1/billing/portal     (Bearer, paid accounts)

Full spec: https://api-production-22727.up.railway.app/openapi.json

RSS / Atom / JSON feeds

All three public surfaces carry the same CapabilityEvent stream in different envelopes.

feeds

RSS 2.0:  https://api-production-22727.up.railway.app/v1/events.rss
Atom:     https://api-production-22727.up.railway.app/v1/events.atom
JSONFeed: https://api-production-22727.up.railway.app/v1/events.json

Add ?kind=mcp_server or ?category=agents to any feed URL.

Delivery tracking

After an agent consumes an event, call the MCP mark_seen tool. CapabilityWire records one delivery for that subscriber and event.

MCP tools/call

{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "mark_seen",
    "arguments": { "event_id": "e2e2e2e2-..." }
  }
}

CLI (coming soon)

Until a dedicated CLI ships, curl and the MCP endpoint are the supported command-line paths.

Event schema

Every surface returns the same canonical CapabilityEvent. JSON Schema is published at /schemas/capability_event.v1.json.

Stable field names with additive schema evolution.
Immutable id and slug.
capability_delta explains why an agent should care.
package.install_command gives the exact install command.