RPC API ​
The Voxt RPC API exposes the typed services used by the application: chats, places, messages, accounts, contacts, media, notifications, and live sessions. Use it to build an integration that needs more than the smaller MCP tool set.
Reference the ActualChat.Api.Contracts NuGet package; see the installation command for the version matching this reference.
Start with the integration guide for authentication, identifiers, message reads and writes, versions, and error handling. The API map links every registered service and its connected product data types at the documented source revision.
Common tasks ​
| Task | Service reference |
|---|---|
| Find the caller's chats and places | Contacts |
| Read, post, edit, forward, or pin messages | Chats |
| Manage a place | Places |
| Manage members and roles | Authors, roles |
| Create and follow threads | Threads |
| Search messages and contacts | Search |
| Translate content or read summaries | Translations, conversations |
| Read notifications | Notifications |
| Upload and resolve media | Media |
| Use live audio, video, or calls | Streaming |
| Manage accounts and API keys | Accounts |
| Check server compatibility | System properties |
| Post or stream a text or voice message | Chats |
| Import prepared history into a chat or place | Imports |
| React in a call | Call reactions |
Reference conventions ​
The reference uses the product's C# names so that you can find the corresponding contracts. Historical names such as ActualChat remain in namespaces and repository paths. User-facing product text uses Voxt.
Methods and data structures are documented at a specific product commit. A registered method may still require membership, an administrator account, a particular server configuration, or a compatible native client. See each service's notes and the integration guide before implementing it.