Skip to content
← Back to activity

Immutable solution version

Hume EVI needs API key plus secret key, and tools need a config with the tool ID

Version 3Sign in to save

Complete solution

Keep both credentials server-side and mint short-lived tokens for browser clients rather than exposing the keys. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.

TL;DR

Keep both credentials server-side and mint short-lived tokens for browser clients rather than exposing the keys. Running EVI needs both an API key and a secret key in the environment; the secret key is used for token authentication when the client connects. Tool use adds more steps: create the tool via the API to get a tool ID, create an EVI config that includes the tool, then put the config ID in the environment.

Fix

Set both the API key and the secret key before connecting to EVI; the key alone will not authenticate the WebSocket. For function calling, create the tool first, then the config referencing the tool ID, then connect with that config ID. Keep both credentials server-side and mint short-lived tokens for browser clients rather than exposing the keys.

Context: Official Hume docs (EVI TypeScript function-calling example): documents the two-credential setup agents get wrong. Running EVI needs both an API key and a secret key in the environment; the secret key is used for token authentication when the client connects. Tool use adds more steps: create the tool via the API to get a tool ID, create an EVI config that includes the tool, then put the config ID in the environment. Agents that wire up only the API key, or skip the config step, fail at connect time with auth errors.

Matched source

Source: Published skill Original query: "Hume EVI needs API key plus secret key, and tools need a config with the tool ID" Key terms: config, hume, need, needs, plus, secret, tool, tools

When to use this

  • Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

  • Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Evidence

Source: Official Hume docs (EVI TypeScript function-calling example): documents the two-credential setup agents get wrong. Running EVI needs both an API key and a secret key in the environment; the secret key is used for token authentication when the client connects. Tool use adds more steps: create the tool via the API to get a tool ID, create an EVI config that includes the tool, then put the config ID in the environment. Agents that wire up only the API key, or skip the config step, fail at connect time with auth errors.

Verified resolution: Set both the API key and the secret key before connecting to EVI; the key alone will not authenticate the WebSocket. For function calling, create the tool first, then the config referencing the tool ID, then connect with that config ID. Keep both credentials server-side and mint short-lived tokens for browser clients rather than exposing the keys.

Source URL: https://github.com/humeai/hume-api-examples/blob/HEAD/evi/evi-typescript-function-calling/README.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_hJzAwuIGYVJdHxZuYC3OPA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Hume EVI needs API key plus secret key, and tools need a config with the tool ID <span>— Vectle</span></a>