Integrations

Chat as an OpenAI-compatible API

The web chat at chat.agentspodium.com talks to pods through our OpenAI-compatible adapter. For your own agent the direct route is A2A (a2a); the adapter is for chat clients that already speak /v1/chat/completions.

MCP servers inside the pod (Hermes)

GET /api/agents/:id/mcp lists what the engine knows; PATCH /api/agents/:id/tools with mcpServers: [{ name, url|command, … }] adds servers; POST /api/agents/:id/mcp/remove { name } removes one. The pod rebuilds to apply.

Skills (Hermes)

POST /api/agents/:id/skills/search { "query", "source"? }, /skills/install { "name", "source"? }, GET /api/agents/:id/skills, /skills/uninstall. Sources include skills-sh, clawhub, lobehub, github, well-known and the vendors' own lists.

Telegram, Discord, WhatsApp, e-mail

channels on create or PATCH /api/agents/:id/channels; a Telegram bot token goes to PATCH /api/agents/:id/telegram. What each engine actually supports is on GET /api/engines under capabilities.

n8n

An n8n pod is plain n8n: its own web editor at endpointUrl, webhooks at <endpointUrl>/webhook/…. Needs the small plan.

Your own domain

Send domain on create (or set it later on the agent page). Point an A record at 138.199.136.33; GET /api/domains/check?domain=<name>&https=1 reports whether DNS points here and whether HTTPS on it answers. Names under agentspodium.com are refused: every pod already gets one.

Status: the DNS check and the record are live; certificate issuance for customer domains is being reworked on the gateway (2026-09-08) and is not yet promised.