Integration

Soniox Organization API integration

The Soniox Organization API covers a Soniox organization as a whole rather than one project: read the organization's profile and projects, its prepaid balance and billing setup, the cost of a calendar month against the budget, the daily cost and activity per project and model, and the budget, rate and quota limits per region, and list or revoke the API keys of any project. Creating project API keys is not exposed (the new key would be returned in run data), and Speech-to-Text and Text-to-Speech are in the separate Soniox API, which needs a project key. Authentication is an organization API key (it starts with snx_org_; only organization admins create them in the Soniox Console under Settings, Organization API keys, with a permission per area) sent as a Bearer token. Calls go to api.soniox.com only and share one limit of 50 requests per minute per organization by default.

Connect Soniox Organization API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Soniox Organization API.Built from the 8 Soniox Organization API tools below, on the connection you add once.

What you can do with Soniox Organization API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Project api key, 2 operations

delete_project_api_keyDelete project api keyDELETEAgents: ask firstRevokes one API key of a project: requests made with it are refused from then on (the change can take a few minutes to apply). Irreversible; integrations using the key stop working.
list_project_api_keysList project api keysGETAgents: ask firstLists a project's API keys, newest first: id, the key's leading characters, name, permissions, creation time and creator (a console user's email address, or an organization key). Never the key itself. Not cached.

Monthly usage, 1 operation

get_monthly_usageGet monthly usageGETAgents: ask firstReturns the cost of one calendar month (USD, as decimal strings) for the organization and each project, split by API, playground, granted and invoiced use, with the budget and what remains of it.

Organization, 1 operation

get_organizationGet organizationGETAgents: ask firstReturns the organization the API key belongs to: its id, name and creation time.

Organization balance, 1 operation

get_organization_balanceGet organization balanceGETAgents: ask firstReturns the organization's prepaid balance (available, granted and used, in USD as decimal strings), whether it is exhausted, and the billing setup: invoice billing, autopay threshold and amount, payment method.

Organization limit, 1 operation

get_organization_limitsGet organization limitsGETAgents: ask firstReturns the organization's monthly budget, its maximum and notification level, and for each region it can use the rate and quota limits in effect (requests per minute, concurrency, stored files and voices).

Organization usage summary, 1 operation

get_usage_summaryGet usage summaryGETAgents: ask firstReturns the organization's cost (USD, as decimal strings) and activity (requests, tokens, audio duration) per UTC day between start_time and end_time, in total and for each project and model. The window may cover at most 366 days.

Project, 1 operation

list_projectsList projectsGETAgents: ask firstLists every project of the organization, oldest first, with id, name, description, region and creation time. Deleted projects are left out.

Use Soniox Organization API from Claude Code, Cursor or Codex

Connect Soniox Organization API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Soniox Organization API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Soniox Organization API

Create your workspace
Sign up free. Nothing to install.
Connect Soniox Organization API once
Add your Soniox Organization API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.