Paperclip & OpenClaw Integration
Use Kite as the real-time event bus for agents running inside Paperclip or OpenClaw. Agents subscribe to webhook streams without standing up any server infrastructure.
Feature in progress
Full Paperclip and OpenClaw integration is actively being built. This page describes the intended architecture and will be updated as implementation progresses.
The problem
AI agent frameworks like Paperclip and OpenClaw orchestrate agents across tasks, but agents typically have no way to receive real-time external events without polling an API or running a server. Kite fills that gap: it delivers webhook events as a reliable, filterable, CloudEvents-formatted stream that any agent can consume with a single CLI command or SDK call.
How it fits together
- An external system (GitHub, Stripe, CI) sends a webhook to your Kite endpoint.
- Kite normalizes it to CloudEvents v1.0 and relays it in real time.
- A Paperclip or OpenClaw agent running
kite streamreceives the event and reacts — no polling, no server. - The agent can filter by source, event type, or manifest rules before processing, keeping downstream noise low.
[ architecture diagram — coming soon ]
Agent quickstart (x402 bootstrap)
Agents can onboard without a browser using the x402 payment protocol. No Clerk session, no dashboard visit.
# Bootstrap credentials programmatically curl -X POST https://getkite.sh/api/v1/bootstrap/x402 \ -H "payment-signature: <x402-payload>" # Returns: team_id, api_key, endpoint, hook_token
See the x402 Bootstrap guide for the full flow including payment payload construction.
Kite as a Paperclip skill
The kite skill for Paperclip lets agents install a GitHub webhook listener, authenticate via gh auth, and start streaming events — all from within a heartbeat run.
# In your agent's desired skills "local/9bf7bc02a1/kite" # Install a GitHub webhook and stream events kite install github --repo owner/repo kite stream --source github --event push
Full guide: Paperclip Integration