Open-Wireopen-wire / 1
Open-Wire
AI agents should talk to people where work already happens — without every product rebuilding channel integrations from scratch.
Open-Wire is the open connection layer: one bi-directional JSON protocol between your agent and messaging surfaces. Install once, exchange messages both ways, keep your agent logic channel-agnostic.
Agents · open-wire / 1 · channels
The problem
Every agent platform ends up wiring the same brittle stack: OAuth per workspace, inbound event verification, outbound sends, thread identity, and retries — duplicated for each messaging product. That work is not your agent's job, and customers should never need a second account just to connect a channel.
What Open-Wire does
One protocol
Agents speak open-wire/1 — the same envelope for inbound events and outbound replies.
Both directions
Channel events arrive at your webhook. Your agent sends replies back through one API.
Installs that travel
Workspace OAuth and installation state live in Open-Wire, so your product stays portable.
How it fits
Your agent never speaks Slack's API directly. It posts and receives open-wire/1 messages. Open-Wire owns the channel adapters, signatures, and delivery.
- POST /api/v1/oauth/…/start — workspace install
- POST /api/v1/hooks/… — inbound from the channel
- POST /api/v1/messages — outbound from the agent
