DialNexa

DialNexa is a Voice AI agents platform for sales calls, lead qualification, follow-ups, meeting booking, collections and support workflows, with a strong focus on Indian-market multilingual calling (English, Hindi, Hinglish, Marathi, Kannada, Gujarati, Tamil, Telugu, Bengali and mixed-language calls). The public contract is an OpenAPI 3.0 document of 41 paths and 54 operations served from api.dialnexa.com with bearer authentication. DialNexa publishes an RFC 9727 api-catalog as a proper application/linkset+json document, two llms.txt files (a site index and a 90KB documentation index), and an auth.md written explicitly for AI agents and automation systems describing how API keys are provisioned.

DialNexa publishes 1 API on the APIs.io network. Tagged areas include Voice AI, Agents, Conversational AI, Telephony, and Sales.

🌐 Visit website 📡 Source on GitHub
23.0/100 emerging ▬ flat Agent 26/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
Voice AIAgentsConversational AITelephonySalesCustomer SupportMultilingual

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 23.0/100 · emerging
Contract Quality 14.4 / 25
Developer Ergonomics 1.9 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 0.0 / 12
Discoverability 6.7 / 10
Agent readiness — 26/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/dialnexa: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

DialNexa API

Voice AI agent platform API — agents, calls, workflows, integrations and analytics. 41 paths, 54 operations, bearer authentication, served from api.dialnexa.com.

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Commercial 1

Pricing, plans, and the legal terms of use

Plans
Plans

Company 1

The organization behind the API

Website
Website

Other 1

Properties that don't map to a standard resource type

APICatalog
APICatalog

Source (apis.yml)

apis.yml Raw ↑ 
aid: dialnexa
name: DialNexa
description: DialNexa is a Voice AI agents platform for sales calls, lead qualification, follow-ups, meeting booking, collections
  and support workflows, with a strong focus on Indian-market multilingual calling (English, Hindi, Hinglish, Marathi, Kannada,
  Gujarati, Tamil, Telugu, Bengali and mixed-language calls). The public contract is an OpenAPI 3.0 document of 41 paths and
  54 operations served from api.dialnexa.com with bearer authentication. DialNexa publishes an RFC 9727 api-catalog as a proper
  application/linkset+json document, two llms.txt files (a site index and a 90KB documentation index), and an auth.md written
  explicitly for AI agents and automation systems describing how API keys are provisioned.
type: Index
url: https://raw.githubusercontent.com/api-evangelist/dialnexa/refs/heads/main/apis.yml
created: '2026-08-21'
modified: '2026-08-21'
specificationVersion: '0.23'
tags:
- Voice AI
- Agents
- Conversational AI
- Telephony
- Sales
- Customer Support
- Multilingual
tags_raw:
- voice ai
- ai agents
- telephony
- lead qualification
- multilingual
apis:
- aid: dialnexa:dialnexa-api
  name: DialNexa API
  description: Voice AI agent platform API — agents, calls, workflows, integrations and analytics. 41 paths, 54 operations,
    bearer authentication, served from api.dialnexa.com.
  humanURL: https://dialnexa.com/docs
  baseURL: https://api.dialnexa.com
  tags:
  - Voice AI
  - Agents
  - Telephony
  properties:
  - type: OpenAPI
    url: openapi/dialnexa-api-openapi.yml
  - type: Documentation
    url: https://dialnexa.com/docs
  - type: APIReference
    url: https://dialnexa.com/docs/api-reference/openapi.json
  - type: Authentication
    url: authentication/dialnexa-auth.md
common:
- type: APICatalog
  url: well-known/dialnexa-api-catalog.json
- type: LLMsTxt
  url: llms/dialnexa-llms.txt
- type: Website
  url: https://dialnexa.com
- type: DeveloperPortal
  url: https://dialnexa.com/docs
- type: Plans
  url: https://dialnexa.com/pricing
maintainers:
- FN: DialNexa
  url: https://dialnexa.com
x-provenance:
  added: '2026-08-21'
  method: searched
  source: https://dialnexa.com/llms.txt
  note: 'Submitted via apis.io/add on 2026-08-21 (twice, as "DialNexa" and "DialNexa | Voice AI Agents Platform" — one provider,
    two records at the gate). The submitted APIs.json URL, https://dialnexa.com/apis.json, returns 404; that is a bad pointer
    in the submission, not an absent surface. A NOTE ON HOW THIS WAS FOUND, because the first pass got it wrong. Probing guessed
    paths (/openapi.json, /developers, /api-docs) suggested DialNexa published nothing: /openapi.json 404s, and /developers
    and /api-docs both return HTTP 200 with the same ~14,930-byte SPA shell the site serves for any unknown path, including
    an invented control. Reading the provider''s own llms.txt instead produced the real locations, and they are all live:
    an application/linkset+json api-catalog, a 352KB OpenAPI under /docs/api-reference/, a 90KB documentation llms.txt, and
    an auth.md addressed to AI agents. Guessing paths on a soft-200 host produces a false negative; the provider''s own index
    is the authority.'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/dialnexa"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/dialnexa/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/dialnexa/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.