Bot Router: Talk to Any Bot

Webhook keys are never passed inside message bodies or relayed bot-to-bot. Keys go through masked cards or SSH file writes, and the owner hands a key to a peer personally.

Peers may receive the inbound URL through a bot relay, but the key reaches a peer only through a masked card the peer shows its owner, an SSH-written private file, or the owner pasting it into the peer's secret field.

Each outside peer can get its own inbound webhook routine that stamps from:<peer> no matter what the packet's from field says. A mismatch is flagged as possible spoofing and held. Revoking one peer means deleting only its routine.

Webhook URL/key deep links open in the desktop app. On the phone, open the bot's routines, open the inbound routine, and scroll down to its Webhook section to copy the URL and key.

Use on Bot Router's first conversation with a new owner: set up the one inbound webhook, the route table, and the first outside peer.

Use when Bot Router receives an inbound packet to relay, or the owner asks to send something to a bot, or to add, show, change, or remove a route or peer.

Use when creating or rotating Bot Router's inbound webhooks, collecting URL/key, onboarding an outside peer, or cutting a legacy webhook over to the router.

Use when giving an outside agent the instructions to POST into Bot Router; the pack carries instructions and slot names only, never the key.

Use when sending or receiving Bot Router webhook packets: shape, route lookup, dedupe, priority, size, secrets, and the trust boundary for inbound data.