The Pipeline
Each tool wraps one or more of your API endpoints. A one to one mapping is not required. You can aggregate multiple endpoints into a single tool so the LLM’s context stays clean and semantically coherent.1. Your APIs
Aomi does not modify your APIs. The only requirement is that they are reachable over HTTP. Your backend owns all user state. The Aomi App retains conversation history but nothing about your users, balances, or sessions.2. Aomi Tool Layer
Aomi wraps your endpoints as tools, typed functions the LLM can invoke during a conversation. Each tool has a name, description, and typed input parameters. Tools can execute concurrently.3. AomiApp Configuration
Three settings define the App’s behavior: Preamble is the system prompt that shapes the AI’s personality, constraints, and rules. A well written preamble keeps the AI on task and prevents overstepping.
RAG Document Store: if you have documentation, FAQs, or knowledge base articles, Aomi sets up RAG ingestion. The AI searches these documents when answering questions beyond what tools provide.
4. Deployed App
Aomi compiles and deploys the configured App as an isolated app on the hosted platform. Each app gets a scoped API key and a dedicated chat endpoint.5. Client Integration
Next Steps
- Agentic Application: how Apps and API keys fit together
- API Reference: full HTTP endpoint documentation
- Sessions: how chat sessions are created and managed