Pricing API

Name: Pricing API API
Brand: Pricing API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingnone3 EndpointsREST

For Agents

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

Quickstart

Get started with Pricing API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get outbound sms pricing for a country"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Pricing API 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

Compare carrier-level pricing across mobile networks within a single country

GET STARTED

Start building with Pricing API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Pricing API, keeping it validated and agent-ready.

The Nexmo Pricing API exposes outbound SMS, voice, and other Vonage service rates so applications can calculate cost before sending traffic. It returns full pricing tables, per-country pricing, and per-prefix pricing for any service type, which lets billing dashboards, finance teams, and routing systems make cost-aware decisions in real time. The endpoint is rate-limited to one request per second, so the typical pattern is to fetch the full pricing table once and cache locally.

Use Cases

Patterns agents use Pricing API 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 though Jentic?

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

Credential isolation

Nexmo apiKey and apiSecret are stored encrypted in the Jentic vault. Agents receive scoped tokens, so the raw secret never enters the agent's prompt or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'get sms pricing for a country') and Jentic returns the GET /get-pricing/outbound/{type} operation with its input schema.

Time to first call

Direct integration: half a day to wire up auth, caching, and the 1-rps limit. Through Jentic: under 15 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio Pricing v2

Twilio's equivalent pricing API covering messaging, voice, and phone numbers.

Choose Twilio Pricing when joining a least-cost routing table that already includes Twilio rates.

Complementary

Nexmo SMS API

The SMS API is the spend driver whose unit cost the Pricing API surfaces.

Look up the rate via Pricing first, then send the message via the SMS API once cost is approved.

Complementary

Nexmo Account API

Account API exposes balance and top-up state that pairs naturally with pricing for spend forecasting.

Combine Pricing with Account balance to enforce spend caps before authorising a send.

FAQs

Specific to using Pricing API 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.