Hume AI through Squiid

What Hume AI is

Hume AI works on the emotional layer of voice. Its Empathic Voice Interface is a speech to speech API that listens, detects tone and responds with matching prosody, so the reply sounds appropriate rather than flat. The Expression Measurement API scores vocal bursts, speech prosody, facial expression and language for dozens of dimensions, and Octave is a text to speech model that takes acting directions in the prompt. The voice interface runs over a websocket and streams both audio and the expression scores it derived, so your app can react to tone as well as text.

In a product this is used where the way something is said matters as much as the words. Support triage that flags a frustrated caller, coaching and practice tools that give feedback on delivery, companion and wellbeing apps, and research pipelines that need consistent scoring across thousands of recordings. It is a specialist service rather than a default, and it is usually added after a basic voice loop already works. Sessions are billed per minute, which makes an abandoned open connection the main cost risk in a voice product.

Why connect it through Squiid

Hume AI is on the Squiid roadmap. When it lands, requests will go to https://api.squiid.io/v1/hume-ai/... with Authorization: Bearer $SQUIID_API_KEY, the official SDKs will work by pointing their base URL at the gateway (gateway convention), and both the voice interface and the measurement endpoints will meter against your prepaid credits at Hume's list price. Squiid will hold the key, which matters for a service that is often called from a client-adjacent realtime session where credentials are easiest to leak.

• One account, one key, one bill, one dashboard. Hume AI sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Hume AI credentials. Your code carries SQUIID_API_KEY, so HUME_API_KEY, HUME_SECRET_KEY, HUME_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Hume AI costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Empathic Voice Interface through the gateway
• Expression measurement on voice, face and language
• Octave text to speech with acting directions
• Usage metered against prepaid credits
• Hume list pricing, no markup

How to connect Hume AI

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces HUME_API_KEY, HUME_SECRET_KEY, HUME_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/hume-ai/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Hume charges per minute for voice sessions and per unit of analysed media for expression measurement, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Hume AI usage, with no markup and no per-request margin.

Hume AI has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Hume AI usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Hume AI is usage-metered, so leaving means creating your own Hume AI key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Hume AI's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Hume AI through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Hume AI usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.