Skip to main content
Welcome to the API reference documentation for AMAS, the Artaios Multi Agent System. This API allows you to programmatically create, configure, and execute intelligent agents for a wide range of tasks and workflows.

​
API Overview

The AMAS API is organized around REST principles. It accepts JSON and YAML-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Base URL

All API requests should be made to:

API Versioning

The current API version is v1. All endpoints are prefixed with /api/v1/.
For a comprehensive interactive API reference, visit the Swagger Documentation.

​
Key Concepts

Agents are AI-powered entities configured with specific capabilities, instructions, and behaviors. AMAS supports two types: LLM Agents (conversational) and ReAct Agents (tool-using, reasoning agents).
A session represents a conversation instance with an agent. Each session maintains its own message history and state. Sessions are created with a complete agent configuration in YAML or JSON format.
The Runtime API allows you to execute messages in sessions and interact with agents in real-time. Send user messages, retrieve agent responses, access conversation history, and monitor execution status with detailed metadata and usage statistics.
Knowledge bases provide agents with access to domain-specific information through semantic search. AMAS supports Milvus vector database for production-ready retrieval.
Files are uploaded documents that can be organized into collections. Collections group related data sources for knowledge base ingestion and management.

​
REST Limitations

This REST API is request/response. Two things it cannot do:
  • Streaming — /execute runs the agent to completion and returns one result. There is no token-by-token output and no visibility into tool calls while they happen.
  • Human-in-the-Loop — approval cards cannot be delivered or answered over REST. An agent with a gated tool suspends mid-run with nothing able to resume it.
Both are available on the WebSocket API. For a REST-only integration, keep every tool on the agent ungated — see Human-in-the-Loop.

​
Getting Started

1

Get your API key

Contact your administrator or use the dashboard to generate an API key.
Keep your API keys secure! Do not expose them in client-side code or public repositories.
2

Validate your agent configuration

Test your agent configuration before creating a session:
3

Create a session and execute

Create a session with your configuration and start executing messages:

​
What’s Next

Explore the full API documentation to learn about all available endpoints and features:

Authentication

Learn how to authenticate your API requests