Call Nomi for agents

Bring your phone conversations into your agent workflow. Connect a local terminal agent, such as Codex or Claude Code, through the Call Nomi CLI to read calls and prepare changes for review.

Account-scoped access. Production outbound calling does not require approval of each destination. It requires an enabled number, an active Agent grant and a configured route for that account's caller ID. Only supported Australian geographic and mobile numbers are allowed. Test mode retains an exact destination allowlist. Live capability and admission checks determine availability. Drafts do not place calls or publish profiles.

Help me connect Call Nomi. Read https://callnomi.com/agent-setup.md, its official Skill and https://callnomi.com/agent-task-brief.md. Check existing connections and granted scopes first; preserve them and reuse active permissions without logging in again for each call. For a new connection use the official CLI device flow only, not a remote connector, manually copied API key or localhost callback server. Check for a local terminal, Python 3.10+ and a supported OS keychain; stop and explain if unavailable. Inspect the official package and obtain required installation permission. Only when a connection or additional permission is needed, request my approval and run nomi auth login with the necessary scopes in a background/PTY session. Show its exact authorization_url and user_code. I must verify my email, matching code and permissions myself. Never expose tokens or store them in plaintext files. Run nomi +me and nomi tools list to verify the connection. For any later call I request, you prepare its recipient, facts, task and boundaries; Nomi handles realtime conversation. Check live outbound requirements, number activation, route eligibility and cost limits. Use only my authorized account's Nomi number. Existing outbound permission is reusable, but does not authorize an unrequested call. Return the result through polling and respect separate summary/transcript permissions. Do not read calls, publish profiles, activate paid services, place calls or pay without my request.
Read setup guide

Available now

For example: “Review yesterday's calls and list the customers waiting for a callback.” Recurring daily analysis requires a separate schedule in your agent client.

Connect your agent

  1. Copy the connection prompt into your local terminal agent.
  2. Let your agent prepare the official CLI and open the Call Nomi authorization page.
  3. Sign in, verify your email, match the displayed code and approve the permissions you want to share.

Use the same verified email whether you already have an account or are getting started. Keep your existing setup and complete only the missing steps. Login, permission approval and payment stay in your browser.

Official Call Nomi skill · Connection guide · Task preparation and responsibilities

CLI device authorization requires Python 3.10+ and a supported system keychain. No local callback server or manually copied API key is needed. Browser-only chat without these capabilities cannot complete CLI setup. Existing connections remain supported. Full onboarding status is currently checked in your account workspace.

You stay in control

Connections are scoped to your account and expire after 90 days. Access tokens last up to 15 minutes and refresh automatically within that period. Revoke the matching Agent connection key in API & integrations to stop data access. Read permissions and draft-writing permissions are separate.

Review or dismiss drafts in your account. Drafts do not change your active profile, plan, number or billing. Login verification and payment stay with you on the Call Nomi website.

Your chosen agent receives the call information you permit. Grant access only to trusted clients and review their data-handling policies.

Task-specific outbound calling

Outbound tools support requesting and checking a call, such as asking a business about availability, once execution is enabled. Your agent collects the recipient, objective, context, success criteria, language, duration and telephony cost limit. You must request the call and explicitly grant outbound permission. Existing connections never gain this permission automatically.

The call cost limit is separate from an order budget. Order calls require the ordering person's name, contact number, items, fulfillment details and explicit total-price authorization. Up to 10 order calls per account per rolling 24 hours, within the overall outbound limit. No payment processing or card sharing. Preparing a draft does not place a call.

A$5/month add-on; A$0.20/min to standard Australian numbers after included outbound minutes. AI-assisted calls also use AI allowance. Number activation, service availability and call limits are checked separately. Production mode has no per-destination allowlist; test mode does. Account spending, duration and anti-abuse limits still apply. No purchases or payments are authorized by an Agent permission.

Review number activation in Phone numbers and Agent permissions in API & integrations. Existing active outbound permission is reused until expiry or revocation; it need not be granted again for each requested call. General self-service route activation is not yet available.

The initiating agent prepares the recipient, facts, objective and authorization boundaries; Nomi handles natural realtime conversation within fixed rules. Results are retrieved by agent polling. Summaries and transcripts require their separate read permissions; a completed call is not proof of task success.