Agentic Application

An Agentic Application (App) defines the isolated environment in which an AI agent operates: the tools it can invoke, the data sources it can access, the model it runs on, and the system prompt that shapes its behavior. Apps are stateless — all runtime state is managed by AomiRuntime, the execution harness that hosts them.

When you interact with Aomi, you are always operating within an App. The active App determines the agent's full capability surface. Switching Apps changes the agent entirely.

For Users

The App you're in determines what the assistant can do. An agent running in a DeFi App may have access to swap aggregators, liquidity pools, and live price feeds. The same platform running a different App might query social APIs or prediction markets instead. If the assistant cannot perform an action you expect, verify you are in the correct App using the App selector in the control bar.

For Builders

Apps are the unit of agent deployment on the Aomi platform. Each App encapsulates:

• Tools — the functions the agent can call
• Preamble — the system prompt defining agent behavior
• Model — the underlying LLM (e.g., claude-sonnet, gpt-4o)
• API key — scoped credentials, isolated per App

Running multiple Apps means running multiple independent agents. A trading agent, a research agent, and a support bot can operate on the same platform without sharing configuration or credentials.

┌──────────────────────────┐   ┌──────────────────────────┐
│  App: defi               │   │  App: research            │
│  tools: [swap,           │   │  tools: [news,            │
│    liquidity, prices]    │   │    social, docs]          │
│  model: claude-sonnet    │   │  model: gpt-4o            │
└──────────────────────────┘   └──────────────────────────┘

The Default App

A default App is available in all environments without requiring an API key. It provides a baseline agent suitable for testing your integration before deploying a scoped App.

Authentication

Apps are protected by API keys scoped to that App. Requests that fail authentication return:

Pass your key via the X-API-Key header, or enter it in the API key field of the control bar.

Further Reading

• Integration Guide — full platform pipeline, including App deployment
• Building Apps — registering tools, preambles, and model config
• API Reference — authentication headers and App-scoped endpoints