Skip to main content
All PraisonAI servers are accessible through praisonai serve <type> - one command to start any server.

Quick Start

1

Start Agents Server

2

Start Gateway Server

3

Start All-in-One Server


All Serve Commands

Run praisonai serve to see all available options with descriptions.

Server Details

HTTP REST API for agents.
Options:Test with curl:

Authentication

Set --api-key to require a key on every request. Send it with either header.
A public bind requires a key. praisonai serve agents exits with SystemExit if --host is not 127.0.0.1 / localhost / ::1 and neither --api-key nor PRAISONAI_SERVE_API_KEY is set — because POST /agents can execute YAML-defined tools. See Serve Agents Authentication.
Both headers are equivalent and use constant-time comparison. Missing or wrong keys return 401 {"error": "Unauthorized"}. These paths stay public even when --api-key is set:

How It Works


Common Patterns

Changes to agents.yaml auto-reload the server.
Bind to all interfaces with API key authentication.
Run different server types simultaneously.
Single server with all providers for development.

Discovery Endpoint

All HTTP servers expose /__praisonai__/discovery for endpoint discovery.

Best Practices

Start with praisonai serve unified during development to access all providers. Split into separate servers for production.
Use --host 0.0.0.0 to accept external connections. Default 127.0.0.1 only accepts local connections.
Always use --api-key when exposing servers publicly. Never run unauthenticated servers on public networks.

Agents Server

HTTP REST API details

Gateway Server

WebSocket coordination

MCP Server

Claude Desktop integration

A2A Server

Agent-to-Agent protocol