Dixa
Dixa is a conversational customer service platform with a REST API for managing conversations, queues, agents, routing, knowledge base articles, and customer satisfaction data. The API enables developers to build automated workflows, integrate external data into routing logic, export conversations and activity logs, manage users and teams, and access omnichannel messaging across phone, email, chat, and social channels.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Dixa the way a machine reads it — 43 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Dixa scores 58.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Dixa
Each block below is one kind of artifact we hold for Dixa. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Dixa Agents API
The Agents API from Dixa — 7 operation(s) for agents.
Dixa Analytics API
The Analytics API from Dixa — 5 operation(s) for analytics.
Dixa Anonymization API
The Anonymization API from Dixa — 5 operation(s) for anonymization.
Dixa Business Hours API
The Business Hours API from Dixa — 4 operation(s) for business hours.
Dixa Chatbots API
The Chatbots API from Dixa — 13 operation(s) for chatbots.
Dixa Contact Endpoints API
The Contact Endpoints API from Dixa — 2 operation(s) for contact endpoints.
Dixa Conversations API
The Conversations API from Dixa — 27 operation(s) for conversations.
Dixa Custom Attributes API
The Custom Attributes API from Dixa — 4 operation(s) for custom attributes.
Dixa End Users API
The End Users API from Dixa — 6 operation(s) for end users.
Dixa Internal Notes API
The Internal Notes API from Dixa — 2 operation(s) for internal notes.
Dixa Knowledge API
The Knowledge API from Dixa — 16 operation(s) for knowledge.
Dixa Messages API
The Messages API from Dixa — 2 operation(s) for messages.
Dixa Organization API
The Organization API from Dixa — 1 operation(s) for organization.
Dixa Queues API
The Queues API from Dixa — 5 operation(s) for queues.
Dixa Ratings API
The Ratings API from Dixa — 4 operation(s) for ratings.
Dixa Search API
The Search API from Dixa — 1 operation(s) for search.
Dixa Tags API
The Tags API from Dixa — 7 operation(s) for tags.
Dixa Teams API
The Teams API from Dixa — 4 operation(s) for teams.
Dixa Templates API
The Templates API from Dixa — 2 operation(s) for templates.
Dixa Webhooks API
The Webhooks API from Dixa — 4 operation(s) for webhooks.
Scroll within the panel for all 20 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Dixa Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Dixa Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Dixa Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Dixa Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Dixa API Rules
SPECTRALJSON Schema 9
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Agent
JSON SCHEMAArticle
JSON SCHEMAConversation
JSON SCHEMAEndUser
JSON SCHEMAMessage
JSON SCHEMAQueue
JSON SCHEMATag
JSON SCHEMATeam
JSON SCHEMAWebhookSubscription
JSON SCHEMAScroll within the panel for all 9 ·
Examples 6
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Dixa — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/dixa · machine-readable index on apis.io