Robylon AI

Enterprise AI customer-support platform spanning voice, WhatsApp, chat, email, social media and ticketing. The platform runs AI agents against a customer knowledge base with configurable personas, model selection, human-agent handover and assignment logic, and its APIs let external systems interact with Robylon and trigger workflows including voice and outbound automation. Documentation is public and extensive and the docs host serves both an llms.txt index and an unauthenticated MCP server; what is not published is a machine-readable contract for the product API itself.

Robylon AI publishes 1 API on the APIs.io network. Tagged areas include Customer-Support, AI Agents, Conversational AI, Voice, and WhatsApp.

Robylon AI’s developer surface includes documentation, API reference, getting-started guide, and 4 more developer resources.

14.3/100 emerging Agent 4/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
1 APIs 1 MCP Servers
Customer-SupportAI AgentsConversational AIVoiceWhatsAppChatEmailTicketingContact CenterWorkflow-Automation

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 14.3/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.6 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 0.0 / 12
Discoverability 6.7 / 10
Agent readiness — 4/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 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
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/robylon: 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.

Robylon Platform API

Lets external systems interact with Robylon and trigger workflows, including voice and outbound automation. Operations are not enumerated here: no OpenAPI or other machine-reada...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: robylon
name: Robylon AI
description: Enterprise AI customer-support platform spanning voice, WhatsApp, chat, email, social media and ticketing. The
  platform runs AI agents against a customer knowledge base with configurable personas, model selection, human-agent handover
  and assignment logic, and its APIs let external systems interact with Robylon and trigger workflows including voice and
  outbound automation. Documentation is public and extensive and the docs host serves both an llms.txt index and an unauthenticated
  MCP server; what is not published is a machine-readable contract for the product API itself.
url: https://raw.githubusercontent.com/api-evangelist/robylon/refs/heads/main/apis.yml
created: '2026-08-20'
modified: '2026-08-20'
specificationVersion: '0.23'
tags:
- Customer-Support
- AI Agents
- Conversational AI
- Voice
- WhatsApp
- Chat
- Email
- Ticketing
- Contact Center
- Workflow-Automation
tags_raw:
- Customer Support
- AI Agents
- Conversational AI
- Voice
- WhatsApp
- Chat
- Email
- Ticketing
- Contact Center
- Workflow Automation
apis:
- aid: robylon:robylon-platform-api
  name: Robylon Platform API
  description: 'Lets external systems interact with Robylon and trigger workflows, including voice and outbound automation.
    Operations are not enumerated here: no OpenAPI or other machine-readable contract is served, so nothing is asserted about
    the operation surface.'
  humanURL: https://guides.robylon.ai/
  baseURL: https://www.robylon.ai
  tags:
  - Customer-Support
  - AI Agents
  - Workflow-Automation
  tags_raw:
  - Customer Support
  - AI Agents
  - Workflow Automation
  properties:
  - type: Documentation
    url: https://guides.robylon.ai/
  - type: LlmsText
    url: https://guides.robylon.ai/llms.txt
common:
- type: Website
  url: https://www.robylon.ai
- type: DeveloperPortal
  url: https://guides.robylon.ai/
- type: Documentation
  url: https://guides.robylon.ai/
- type: APIReference
  url: https://guides.robylon.ai/
- type: LlmsText
  url: https://guides.robylon.ai/llms.txt
- type: MCPServer
  url: https://guides.robylon.ai/mcp
- type: GettingStarted
  url: https://guides.robylon.ai/index.md
maintainers:
- FN: Robylon AI
  url: https://www.robylon.ai
x-evidence:
  round: '2026-08-20'
  admitted_from: Direct request to info@apievangelist.com from Akash G M, Growth Team at Robylon AI, asking to be indexed
    and offering to supply whatever artifacts would help.
  verified_2026_08_20:
    www.robylon.ai: 200, 102,466b; an invented path returns 404, so the host discriminates.
    guides.robylon.ai: 200, 250,163b of real documentation.
    llms.txt: 200 text/plain 8,883b, plus llms-full.txt at 125,053b.
    mcp: /.well-known/mcp.json 200 application/json; POST tools/list to /mcp returned 200 text/event-stream with real tools,
      anonymously.
    user_agent_check: Every request run twice, with a default client user-agent and with a browser user-agent. Byte-identical
      both ways — Robylon filters nobody.
  no_openapi: 'No OpenAPI, apis.json or other machine-readable contract found on either host. Probed the docs-platform conventions
    as well as the obvious paths: /openapi.json, /references/openapi.yaml, /openapi/api-reference.json, /api-reference/introduction
    — all 404. Nothing derived or modelled; the single API entry asserts no operations because none are readable.'
  mcp_scope_note: The MCP server is real and unauthenticated, and it is a Mintlify DOCUMENTATION server — its tools search
    the docs corpus. None create a ticket, place a call or trigger a workflow. An agent can learn how to integrate Robylon
    through MCP but cannot transact with it.
  defect_to_report: The MCP descriptor advertises https://robylonai.main-kill-isr.mintlify.me/mcp — a Mintlify PREVIEW hostname
    — while the endpoint actually answers at guides.robylon.ai/mcp. Any agent following the descriptor is pinned to a vendor
    preview host Robylon does not control.