# Arivox — onboarding pointer for AI agents > Machine-readable entry point for autonomous agents evaluating or integrating > Arivox on behalf of a human or an organization. > Published at . Last updated 2026-08-02. > Companion file: (product summary for LLMs). This file states only what is true today. Where a capability does not exist yet, it says so rather than describing an intended one. ## What Arivox is A multilingual voice-AI calling platform: inbound and outbound phone agents. Hebrew, Arabic dialects (Gulf, Levant, MSA) and Russian run on Arivox's own regional stack; 100+ further languages run via third-party voice APIs. The product provisions local phone numbers across Israel, MENA and the CIS, and supports bring-your-own carrier over SIP elsewhere. Arivox builds and hosts its own speech recognition, voices and agent loop. It does **not** own phone lines — numbers and termination are bought from licensed carriers. ## Documentation - Docs home: - Quickstart: - API reference: - Self-hosting: - Legal (terms, privacy, DPA, AUP, sub-processors): ## API | | | |---|---| | Base URL | `https://api.arivox.dev` | | Versioned prefix | `/v1` on every customer-facing endpoint | | Content type | `application/json` | | Health probe | `GET /health` — unauthenticated, not rate limited | | Authentication | `Authorization: Bearer ` | | Key format | `vl_live_` + 32 base62 characters, org-scoped | | Key creation | Dashboard → Settings, or `POST /v1/api-keys` (requires `settings:manage`) | | Key visibility | The secret is returned once, on create, and is never retrievable again | | Test keys | `isTest: true` stamps calls `metadata.test = true`; test calls still consume real minutes and real funds | | Rate limits | Enforced per minute; exceeding one returns `429` | Every route is deny-by-default: a permission guard runs before the handler and returns `403` when the caller's role lacks the required permission. One public, unauthenticated endpoint exists on the marketing site for pre-signup evaluation: ``` GET https://arivox.dev/api/number-search?country=IL&type=local ``` It reports whether local numbers are currently in stock in a country and the carrier's list price. Phone numbers in the response are masked (last four digits hidden) and it is rate limited to roughly 10 requests per minute per IP. Supported countries: `IL`, `US`, `GB`, `CA`. ## How to sign up Account creation is a **human** flow. There is no public account-creation API. 1. A human completes signup at . 2. Depending on platform configuration, the registration may wait for **staff approval** before the account becomes usable. 3. The human creates an org-scoped API key in the dashboard (Settings) and hands it to the agent. From that point an agent can drive the `/v1` API within the permissions of the role attached to that key. ### Phone numbers require a region-specific process - **United States, United Kingdom, Canada** — self-serve; a number can be ordered through the product without a review step. - **Israel** — approval required: a KYC and use-case review runs before a number is assigned. It is usually cleared the same day. It is not automatic and it is not bypassable by an API call. - **United Arab Emirates, Saudi Arabia** — business documents and a signed letter of authorization are required before provisioning. ### Billing Accounts are **prepaid by default**: a credit balance is topped up, and calls and numbers draw it down. At a zero balance, calls are refused rather than run up an invoice. Monthly invoicing exists but is granted account by account, by hand — it is never self-serve and there is no credit line by default. Plans include a number allowance (Starter 1, Growth 3, Scale 10 local numbers at no extra cost). Numbers beyond that allowance bill monthly from the prepaid balance at the carrier's rate. Published plan and per-minute pricing: . ## Not available programmatically (today) Stated explicitly so an agent does not spend time probing for them: - **Account creation / signup.** No API. Human-completed, and subject to staff approval where the platform is configured to require it. - **Agent-payable checkout.** Arivox does **not** support x402 or any other machine-payment protocol. There is no way for an agent to purchase a plan, top up a balance, or settle an invoice without a human. - **Number ordering in regulated regions** without the KYC / document review above. The review is a human decision, not a queue an API can skip. - **Switching an account to monthly invoicing.** Staff-granted only. - **An Arivox MCP server.** None is published. Arivox can *consume* MCP tool servers as agent connectors, but does not expose its own API over MCP. - **A public, machine-readable catalogue of number inventory.** The endpoint above reports availability and price only, with masked digits. ## Contact - Email: - Web: An agent acting for a customer should route anything on the "not available" list to that customer rather than attempting a workaround.