Skip to Content

API Explorer

This page gives you a complete route map of the elizaOS Cloud REST API, generated directly from the codebase (app/api/v1/**/route.ts) so it stays in sync with production.

Most public REST endpoints live under /api/v1. Some internal endpoints (admin/cron) are hidden by default — toggle “Show all” in the explorer if you need them.

Base URL

https://cloud.milady.ai/api/v1

For server-to-server usage, send your API key as a Bearer token:

curl -X GET "https://cloud.milady.ai/api/v1/models" \ -H "Authorization: Bearer YOUR_API_KEY"

Requests

Responses & errors

Errors are returned with appropriate HTTP status codes (e.g. 401, 403, 404, 429, 500). If you need a stable programmatic contract, rely on status codes first, then parse error bodies.

OpenAI compatibility

For OpenAI-style chat, use the OpenAI-compatible route:

Full API route explorer

Route Explorer
282 endpointsClick to view details
advertising8
affiliates2
Agents11
API Keys4
app1
app-auth2
App Builder12
app-credits3
Applications29
billing1
blooio4
browser5
chain3
character-assistant1
Chat2
connections1
Containers7
Credits & Billing4
Dashboard1
device-bus3
discord9
Discovery1
eliza1
Embeddings1
extract1
Gallery1
Image Generation1
generate-prompts1
Video Generation1
jobs1
Knowledge Base7
market5
MCP Integrations3
messages1
milady41
milaidy14
Models3
oauth11
pricing1
proxy3
Redemptions5
referrals2
remote3
reports1
Responses1
rpc1
search1
solana5
steward2
stt1
telegram6
topup3
track1
tts1
twilio4
twitter4
User4
voice6
voices6
whatsapp3
x8
x402 Payments3

Select an Endpoint

Choose an endpoint from the list to view details, authentication requirements, and example code.

OpenAPI spec + client generation

The platform exposes an OpenAPI spec endpoint at:

https://cloud.milady.ai/api/openapi.json

You can generate TypeScript types/clients from that spec using your preferred tooling (e.g. openapi-typescript, orval, or OpenAPI Generator).