Soul Machines
Soul Machines builds autonomously animated "Digital People" — AI-driven interactive avatars that combine a real-time facial/gesture animation engine with conversational AI so brands can deploy human-like agents for customer experience, sales, education, and health. Developers integrate Digital People through the Web SDK (a JavaScript library that renders and drives a Digital Person in the browser over a WebSocket session to the dh.soulmachines.cloud session server) and the Skills API (a REST/callback contract for building web services that supply the conversational responses a Digital Person speaks). Personas, API keys, and content are configured in DDNA Studio. Soul Machines was founded in Auckland, New Zealand and is a portfolio company of the SoftBank Vision Fund.
Soul Machines publishes 2 APIs on the APIs.io network. Tagged areas include Company, Enterprise, Artificial Intelligence, Digital Humans, and Avatars.
The Soul Machines catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Soul Machines’ developer surface includes documentation, API reference, getting-started guide, support, pricing, signup flow, authentication, and 17 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Soul Machines Digital Person Session
Real-time WebSocket session API used by the Web SDK to connect a browser client to a Digital Person running on the Soul Machines session server. A session is authenticated with ...
Soul Machines Skills API
REST/callback contract for building web services ("skills") that respond to a Digital Person's conversational user input — NLP-adapter skills, intent matching, and pre/post proc...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
soul-machines-mcp.yml
MCP SERVEREvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Soul Machines Skills Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
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
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API