Exedus Xen · canonical telephony layer

Beside AI proxy

The only path to Twilio API while Twilio stays on the D.I.E. list. AI-layer interception. Cost containment. qi sovereignty.

The flow

qi
Source
voice · text · SMS
Beside
AI proxy
chatID prv_BD42PG...
Twilio
Carrier API
backend only
→ delivered to 8672 (qi's phone) · or any recipient

qi
Source
code · agent · script
Twilio
Direct API
DIE'd · no Exedus code calls api.twilio.com directly
api.twilio.com/2010-04-01/Accounts/AC.../Messages.json · banned in Exedus code

Why Beside is the only allowed path

1 · AI-layer interception
Beside is an AI proxy, not just a dumb relay. Every inbound/outbound message passes through an AI-aware layer that can route, classify, escalate, or compose before hitting Twilio.
2 · Cost containment
Beside absorbs Twilio's per-message pricing complexity. One subscription line at the proxy, no per-message Twilio billing leak into agent code.
3 · qi sovereignty
qi owns the Beside chatID and proxy config. Twilio is the carrier — Beside is the surface. If Twilio changes terms or pricing, Beside swaps the backend without rewriting any Exedus code.
4 · No raw endpoints in agent code
No Twilio account SID / auth token in Ezekiel or mac-xen code. The credential surface stops at Beside. Reduces blast radius of any token leak.

Implementation spec

Beside chatID · qi 8672 VVS leg
prv_BD42PGSXAD2KV575NQZQWGCT84private chat · drives the SMS leg of VVS
Outbound (xen-reply-vvs)
POST → Beside RESTtoken: bdapi_... · payload: text + chatID
Inbound (beside_inbox_poller.py)
Beside fetch_inboxline 117 · Authorization: Bearer <token> · external API auth (canon as-is)
Bridge forward (forward_to_beeper)
POST /api/beside-bridge/inboundline ~247 · X-Xen-Token header · landed 2026-05-21 21:21:06 (bridge-401 v2 fix)

Recent operational

canonical SMS leg
Beside → Twilio → 8672
qi's phone, qi's chatID, qi's proxy. Every VVS SMS goes through here. Direct Twilio remains on the D.I.E. list.