Nexmo Pricing API

Name: Pricing API
Brand: Pricing API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingnone3 EndpointsREST

Install Jentic One Beta

Connect the Pricing API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pricing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pricing API.

Retrieve the full outbound pricing table for SMS, voice, or any other service type

Look up the price of an outbound SMS to a specific country by ISO code

Look up the price of a number by dialing prefix when the destination country is unknown

GET STARTED

Start building with Pricing API

Explore with Jentic

View OpenAPI Document

For Agents

Retrieve outbound SMS and voice pricing per country or per dialing prefix so an agent can estimate spend before sending traffic.

Use for: I want to know how much an SMS to Brazil costs on Nexmo, Get the full outbound pricing table for voice calls, Look up the price for dialing prefix 447, Compare SMS pricing across UK mobile carriers

Not supported: Does not send messages, place calls, or expose inbound pricing - use for outbound SMS and voice rate lookups only.

Use Cases

Patterns agents use Pricing API for, with concrete tasks.

★ Cost estimation before send

Customer success and billing dashboards call /get-pricing/outbound/sms with a country code to display the per-message rate beside a campaign builder. Showing the rate up-front prevents finance surprises and lets account managers approve high-volume campaigns with full cost visibility before any traffic actually flows.

GET /get-pricing/outbound/sms?country=BR and surface the unit price beside the campaign volume slider

Least-cost routing

Routing engines that send the same message via multiple providers fetch the full Nexmo pricing table via /get-full-pricing/outbound/sms, cache it locally, and join it against equivalent tables from other vendors to choose the cheapest viable route per destination. Because the endpoint is rate-limited to 1 request per second, a daily refresh into a local store is the right pattern.

GET /get-full-pricing/outbound/sms once per day, cache the response, and join against vendor B's table to pick the cheapest route per destination

Prefix-based price lookup

When a number is captured in raw E.164 form without a country code mapping, applications call /get-prefix-pricing/outbound/sms with the leading digits to fetch the price directly. This is essential for fraud and abuse teams reviewing logs of outbound traffic where only the dialed digits are recorded, not the parsed country.

GET /get-prefix-pricing/outbound/sms?prefix=44 and return the per-network breakdown for the United Kingdom

AI agent cost-aware routing via Jentic

An AI agent that sends transactional notifications can call the Pricing API through Jentic to make cost-aware sending decisions per message. The agent searches for the pricing operation, supplies the country, and Jentic returns the unit cost which the agent compares against alternative providers before executing the send.

Search Jentic for 'get sms pricing for a country', load /get-pricing/outbound/sms, and execute with country=DE

Key Endpoints

3 endpoints — the nexmo pricing api exposes outbound sms, voice, and other vonage service rates so applications can calculate cost before sending traffic.

METHOD

PATH

DESCRIPTION

GET

/get-full-pricing/outbound/{type}

Full outbound pricing table for a service type

GET

/get-pricing/outbound/{type}

Outbound pricing for a specific country

GET

/get-prefix-pricing/outbound/{type}

Outbound pricing for a specific dialing prefix

GET

/get-full-pricing/outbound/{type}

Full outbound pricing table for a service type

GET

/get-pricing/outbound/{type}

Outbound pricing for a specific country

GET

/get-prefix-pricing/outbound/{type}

Outbound pricing for a specific dialing prefix

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Nexmo api_key and api_secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get SMS pricing for a country', and Jentic returns the matching outbound pricing operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Pricing API through Jentic.

What authentication does the Nexmo Pricing API use?

The OpenAPI spec for Pricing v0.0.3 does not declare a security scheme on its operations, but in practice Vonage requires the same apiKey and apiSecret query parameters as the rest of the platform. Through Jentic those credentials live in the encrypted vault and never reach the agent.

Can I get inbound pricing through this API?

No - every operation in the spec is scoped to outbound traffic. The path templates are /outbound/{type} and there is no /inbound counterpart. For inbound costs (which Vonage charges differently per number type) consult the Numbers API metadata or your Vonage dashboard.

What are the rate limits for the Pricing API?

The Pricing API is rate-limited to one request per second per account. The right pattern is to call /get-full-pricing/outbound/{type} once a day, cache the table in your own store, and serve cost lookups from cache rather than hitting the live endpoint per send.

How do I get SMS pricing for a country through Jentic?

Run pip install jentic, search for 'get outbound sms pricing for a country', and Jentic returns GET /get-pricing/outbound/sms. Execute with country=DE and Jentic returns the per-network price breakdown directly.

What service types are supported on the {type} parameter?

The Pricing API supports sms, sms-transit, and voice as the {type} path parameter on all three endpoints. Calling the same path with different service types lets a finance pipeline pull a complete cost picture for a destination in three calls.

Is the Nexmo Pricing API free to call?

Yes - Vonage does not charge per pricing-lookup. Only the underlying SMS and voice traffic incurs cost. That said, the 1-request-per-second rate limit means you should not poll it as a cheap alternative to caching.

Can I limit what my agent is allowed to do with the Nexmo Pricing API?

Yes. Because you self-host Jentic One, your own rules decide which of the three read-only rate-lookup operations your agent may call: the full outbound pricing table, per-country pricing, or per-prefix pricing. Scoping is by operation rather than by resource, so you can allow only the lookups the agent actually needs and nothing beyond those runs. Your Nexmo api_key and api_secret stay stored and injected by your instance at execution time, never reaching the agent.