DIDWW Public API
66
AI ReadinessAI-Aware (B)66/100
Official vendor OpenAPI document · agent-readyCommunicationsVoice TelephonyapiKey107 EndpointsREST
For Agents
Browse DID coverage, reserve and order phone numbers, and route them to voice trunks through DIDWW. Read the account balance and request call-detail-record exports over its JSONAPI interface.
Use for: Browse DID coverage by country, List available phone numbers in a city, Reserve a number before I buy it, Create an order for a DID
Not supported: Does not handle SMS messaging, call recording playback, or number portability filings. Use for DID provisioning and voice trunk routing only.
The DIDWW API browses telephony coverage, orders and manages DID phone numbers, and routes them to inbound and outbound voice trunks over a JSONAPI interface. Agents search coverage by country, region, city, and area, reserve numbers before purchase, place orders, and configure trunks and trunk groups. Account operations read the balance and request call-detail-record exports, and the API is versioned by dated releases selected per request.
Install Jentic One Beta
Connect the DIDWW Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DIDWW Public 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdidww.com%2Fdidww" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdidww.com%2Fdidww" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 DIDWW Public API.
Browse coverage by country, region, city, and area
List available DIDs and reserve a number before purchasing it
Order DIDs and track the order through to completion
Route DIDs to inbound and outbound voice trunks and trunk groups
Read the account balance and request call-detail-record exports
Review DID history and manage capacity and regulation records
Use Cases
Patterns agents use DIDWW Public API for, with concrete tasks.
★ Provision a Phone Number
An AI agent provisions a local number in a target market: it browses coverage for the country and city, lists available DIDs, reserves one so it cannot be taken, and places the order. The agent discovers the coverage, availability, reservation, and order operations through Jentic by intent, so it provisions a number without hardcoding endpoint paths.
Browse coverage for a city, list available DIDs, reserve one, and create an order to purchase it
Route Numbers to Trunks
After purchasing DIDs, an agent wires them into the voice path. It creates an inbound voice trunk, groups trunks where needed, and updates a DID to point at the right trunk. DIDWW keeps trunks and DIDs as separate resources, so the agent configures routing by linking them.
Create an inbound voice trunk and update a DID so its inbound calls route to that trunk
Monitor Account and Usage
A billing agent keeps an eye on spend and call activity. It reads the account balance, lists DID history, and requests a call-detail-record export to analyze usage offline. Because the export is created as a job, the agent requests it and retrieves the result when it is ready.
Read the account balance, then request a CDR export and retrieve it once the export job completes
Key Endpoints
107 endpoints — the didww api browses telephony coverage, orders and manages did phone numbers, and routes them to inbound and outbound voice trunks over a jsonapi interface.
METHOD
PATH
DESCRIPTION
GET
/countries
List coverage countries
GET
/did_groups
List DID groups
GET
/available_dids
List available DIDs
POST
/did_reservations
Reserve a DID before purchase
POST
/orders
Create an order
GET
/dids
List DIDs on the account
POST
/voice_in_trunks
Create an inbound voice trunk
GET
/balance
Read the account balance
GET
/countries
List coverage countries
GET
/did_groups
List DID groups
GET
/available_dids
List available DIDs
POST
/did_reservations
Reserve a DID before purchase
POST
/orders
Create an order
GET
/dids
List DIDs on the account
POST
/voice_in_trunks
Create an inbound voice trunk
GET
/balance
Read the account balance
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
D
DIDWW Public API
- AI-Aware (B)66/100
74
Foundational Compliance66
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience83
Agent Usability50
Security81
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
66
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
12%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
63%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
62%
Summary Coverage
Coverage of summaries across operations/tags/info.
83
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
83%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
81
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
81%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring DIDWW by hand means issuing an API key, sending it in the api-key header, selecting the dated API version with a version header, and working through its JSONAPI request and response shapes. Through Jentic you install once, import DIDWW from the API Directory, store the key once, and your agent calls it.
Permission scoping
You choose which DIDWW operations your agent may call, so you can allow coverage browsing and DID reservations while leaving order creation, trunk changes, and deletions out unless you add them. That keeps purchasing and routing changes off the table until you allow them.
Credential isolation
Your DIDWW key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as list available phone numbers or route a DID to a trunk, and Jentic returns the matching DIDWW operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DIDWW Public API through Jentic.
What authentication does the DIDWW API use?
The DIDWW API authenticates with an API key sent in the api-key request header, per its OpenAPI spec, and a dated API version is selected with a version header on each request. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.
Can I buy phone numbers with the DIDWW API?
Yes. Browse coverage to find numbers, list the available DIDs, reserve one so it is held for you, and create an order to purchase it. The reservation step keeps a number from being taken while the order is placed.
What are the rate limits for the DIDWW API?
The OpenAPI spec does not publish numeric rate limits for the DIDWW API. Check DIDWW's own API documentation for current limits, which its versioning and authentication guides link out to.
Can I limit what my agent is allowed to do with the DIDWW API?
Yes. Write a rule that allows only coverage browsing and DID reservations, so the agent can research and hold numbers while order creation, trunk changes, and deletions stay out unless you add them. Every call the agent makes is logged.
How do I provision a number with the DIDWW API through Jentic?
Search Jentic for an intent like provision a phone number, store your DIDWW key once, and your agent browses coverage, reserves a DID, and creates the order in sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a DIDWW MCP server?
You don't need an MCP server to give your agent the DIDWW API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the operations it needs on demand.
GET STARTED