AgentBridgeby Victor
DEVELOPER NOTES

Simple outside.
Considered underneath.

A clear boundary between the web workspace and the private carrier prototype.

01 / THE WEB WORKSPACE

A place to prepare.

The studio stores route drafts, guidance preferences and workspace activity. Drafts are separate from carrier reservations, and the web service does not expose telephony callbacks.

GET /api/studio/overviewWorkspace statePOST /api/studio/routesSave a draftPATCH /api/studio/settingsSave preferences
02 / THE PRIVATE BACKEND

Inspect, with intention.

The optional backend connection uses an HTTPS origin and a scoped account token, stored only on the server. The studio calls the read-only get_bridge_setup and list_my_numbers tools.

Keep carrier routing disabled while the separate security and platform checks remain unresolved. A successful inventory check does not prove live calling.

03 / DEPLOYMENT

Made for its own home.

The intended host is agentbridge.victor.ceo, with the product linked from Victor beside Meridian. The Railway service needs one persistent volume and a configured operator access-key hash.

Open the Railway runbook
04 / DESIGN SYSTEM

A shared set of details.

The interface uses Meta’s open-source Astryx React components: navigation, buttons, cards, segmented controls, dialogs and form inputs, composed with AgentBridge’s own connection imagery and material treatment.

Explore Astryx