Rime Prism vs Vogent API

Rime Prism

Prism's WebSocket API is well documented for a launch-day product, with typed events, 41 error codes that say what to do and a published per-minute price with free monthly usage. It has no Prism component or history on Rime's status page, no published concurrency limit, alpha SDKs, English only, and no data-handling statement that covers caller audio.

Vogent API

IVR detection and navigation models for outbound calls. No public changelog and no release found since January 2026.

Rime Prism

1. Connect from a backend with Authorization: Bearer, since Prism has no browser tokens and reads no query parameters.
2. Send session.update before any audio, or every append fails with session_not_initialized.
3. Keep streaming audio, silence included, while Prism speaks, because it finds turn ends and interruptions from that audio.
4. Ask for the continuation after each tool result, since Prism doesn't resume on its own, and never rerun a call with an unknown outcome.
5. Pin the exact SDK version, because the SDKs are alpha and a new release can change the API.

Vogent API

1. Send an idempotencyKey on POST /dials, a reused key returns 409
2. Create a call with callAgentId, plus toNumber and fromNumberId for phone calls
3. Tell the model when to emit <|transfer|>, since transfers fire on that tag
4. Verify webhooks with the HMAC in X-Elto-Signature
5. Expect new dials to fail at the workspace's concurrent dial limit until calls end