Agentic Application
An isolated agent environment that defines what the AI can do and access. Each App has its own tools, preamble, model, and API key. Switching Apps changes the agent entirely.
See: Key Concepts, Building Apps, Apps & Auth
Anvil Fork
An ephemeral copy of a blockchain network state created using Foundry’s Anvil. Aomi simulates transactions against forks before sending them to the real chain.
See: Simulation Reference
A Rust trait for single-result tools. Tools implement call(), name(), and description() and are registered with the Tool Scheduler.
See: SDK Reference
AomiBackend
A Rust trait implemented by all agentic applications (ChatApp, ForgeApp, L2BeatApp). Provides process_message() and system_events() as a common interface.
See: SDK Reference
AomiRuntimeProvider
The top-level React provider from @aomi-labs/react. Sets up all contexts — thread state, user state, notifications, events, and control — with a single wrapper.
See: Headless Library
API Key
Scoped credentials used to authenticate requests to an App. Keys are isolated per App — a key for one App cannot access another.
See: Apps & Auth, Security
App
Short for Agentic Application. The unit of deployment on Aomi — a configured agent with a specific tool set, preamble, model, and API key.
See: Agentic Application
App Isolation
Each App runs independently with its own tool registry, model configuration, and API key scope. No cross-App data sharing.
See: Architecture, Runtime
Assertion
A check used in evaluation harnesses to verify agent behavior. Examples: balance assertions, state assertions, event assertions.
See: Evals & Testing
aomi-build
A skill bundle for building and deploying custom Aomi Apps. Provides CLI patterns for scaffolding, tool registration, and deployment.
See: Skills
aomi-transact
A skill bundle for executing on-chain transactions through Aomi. Provides CLI patterns for swaps, transfers, contract interactions, and simulation.
See: Skills
BackendApi
A direct HTTP client class from @aomi-labs/react usable outside React. Provides methods for chat, thread management, model queries, and tool calls.
See: Headless Library
ChatApp
The default agentic application type. A general-purpose assistant that can be configured with custom tools, preamble, and document store.
See: SDK Reference
ChatAppBuilder
A builder-pattern API for constructing ChatApp instances. Supports adding tools, configuring docs, and finalizing builds with MCP and event channel options.
See: SDK Reference
ChatCommand
An enum representing streaming response variants from the Aomi runtime: StreamingText, ToolCall, AsyncToolResult, Complete, Error, Interrupted.
See: SDK Reference
CLI
The command-line interface for interacting with Aomi. Supports chat, app management, model selection, session inspection, transaction simulation, and secret management.
See: CLI Usage Guide, CLI Reference
ERC-4337
The Ethereum account abstraction standard. Aomi supports ERC-4337 for session keys, gas sponsorship, and batched user operations.
See: Account Abstraction
ERC-6900
The modular account standard. Extends ERC-4337 with pluggable modules for custom validation, execution, and payment logic.
See: Account Abstraction
EIP-1271
The signature validation standard for smart contract wallets. Aomi supports EIP-1271 for contract-based account signing.
See: Account Abstraction
EvalCase
A single test case in the Aomi evaluation framework. Defines a name, instruction, and set of assertions to verify agent behavior.
See: Evals & Testing
EvalHarness
The test runner for evaluating agent behavior. Takes an AomiBackend instance and runs EvalCases against it, reporting pass/fail for each assertion.
See: Evals & Testing
Execution Plan
A grouped set of operations produced by the ForgeExecutor. Groups related script steps into a single execution unit for dependency-aware ordering.
See: Script Generation
ForgeApp
An agentic application specialized for smart contract development. Extends ChatApp with Forge-specific tools — compilation, deployment, fork testing, and dependency management.
See: SDK Reference
ForgeExecutor
A dependency-aware executor for Forge scripts. Handles compilation, dependency resolution, and script execution against Anvil forks.
See: Script Generation
Fork Provider
Manages the lifecycle of Anvil fork instances. Supports managed forks (created on demand) and external forks (connected to existing instances).
See: Simulation Reference
Fork Snapshot
A captured state of an Anvil fork at a point in time. Enables reverting to a known state after simulation, allowing multiple simulations without recreating the fork.
See: Simulation Reference
A feature of account abstraction where transaction gas costs are paid by a sponsoring account (paymaster) instead of the end user. Useful for onboarding users who don’t hold ETH.
See: Account Abstraction
Headless Library
The @aomi-labs/react npm package. Provides runtime logic, state management, hooks, and an API client with zero UI opinions for building completely custom interfaces.
See: Headless Library
HistoryBackend
A pluggable persistence trait for session history. Supports in-memory (development), SQLite, PostgreSQL, and custom backends.
See: Runtime Reference, SDK Reference
Integration Paths
The three ways to deploy an Aomi-powered assistant: Widget (shadcn component), Headless Library (React hooks), and Telegram Bot (managed by Aomi).
See: Integration Guide
L2BeatApp
An agentic application specialized for Layer-2 protocol analysis. Provides tools for querying L2Beat data, analyzing rollup configurations, and comparing risk parameters.
See: SDK Reference
MCP
Model Context Protocol. A protocol for connecting LLMs to external tools and data sources. Aomi supports MCP for extended tool registrations beyond built-in tools.
See: Architecture
A Rust trait for tools that produce streaming results over time. Implements call_stream() with a sender channel for progress updates and final results.
See: SDK Reference
Non-Custodial
A security model where Aomi never holds private keys or signing material. All transactions are signed locally in the user’s wallet after simulation review.
See: Non-Custodial Wallets, Security
OWASP AST03
The OWASP AI Security framework. Aomi’s skill repository runs four AST03-compliant scanners on every pull request: behavioral audit, offline analysis, static analysis, and dependency scanning.
See: Security, Skills
Para Wallet
The wallet infrastructure provider backing Aomi’s non-custodial wallet integration. Handles wallet creation, key management, and blockchain connections through wagmi-compatible connectors.
See: Non-Custodial Wallets
Preamble
The system prompt that defines an agent’s personality, constraints, and behavior rules. Every App has a preamble that shapes how the AI responds and when it calls tools.
See: Integration Guide, How It Works
RAG
Retrieval-Augmented Generation. Aomi can ingest documentation, FAQs, and knowledge base articles into a vector store. The AI searches these documents when answering questions beyond what tools provide.
See: Integration Guide
Runtime
The hosted execution environment that manages sessions, processes messages, coordinates tool execution, and streams responses via SSE.
See: Runtime Reference
Script Generation
The process of constructing and executing Foundry forge scripts through Aomi’s ScriptAssembler and ForgeExecutor. Supports dependency resolution, source fetching, and execution planning.
See: Script Generation
Server-Sent Events
SSE is the streaming protocol used by Aomi to deliver real-time responses. Events include text chunks, tool calls, tool results, and completion signals.
See: How It Works, Runtime Reference
Session
A conversation thread identified by a UUID. Sessions maintain their own message history, tool execution state, and event queue. Sessions expire after a configurable TTL.
See: Sessions Reference
Session Key
An ephemeral, limited-permission key used in account abstraction. Session keys allow the AI to execute approved operations without requiring user interaction for every transaction.
See: Account Abstraction
Simulation-First
The core safety principle of Aomi: every on-chain transaction is simulated on a forked network before it reaches the user’s wallet. Users review exact outcomes before signing.
See: Simulation Reference, Non-Custodial Wallets
Skill
A markdown-based instruction file that teaches AI coding agents (Claude Code, Cursor, Copilot) how to use Aomi’s CLI and tool surface. Skills are OWASP-scanned in CI.
See: Skills
State Diffing
The process of computing the difference between pre-simulation and post-simulation network state. Shows exact token changes, gas costs, and contract calls made during simulation.
See: Simulation Reference
SystemEvent
An event emitted by the Aomi runtime for out-of-band communication. Variants: InlineDisplay (UI notifications), SystemNotice (status messages), SystemError (errors), AsyncUpdate (background updates).
See: SDK Reference
SystemEventQueue
A thread-safe event buffer used by the runtime to collect and dispatch system events. Consumers can read events without consuming them.
See: SDK Reference
A typed function that an LLM can invoke during a conversation. Tools wrap APIs, on-chain actions, or data sources. Each tool has a name, description, and typed input parameters.
See: Integration Guide, Custom Tools
The global registry and executor for all registered tools. Manages tool registration, concurrent execution, and result streaming back to the LLM.
See: SDK Reference
A streaming abstraction for tool results. Supports single-result tools (shared future) and multi-step tools (mpsc channel) for progressive result delivery.
See: SDK Reference
User Operation
An ERC-4337 user operation (UserOp). Bundles transaction intent, signature, and metadata into a single object that can be sent to an entry point contract for execution.
See: Account Abstraction
The AomiFrame shadcn/ui component. Provides a ready-made chat interface with compound components (Root, Header, Composer, Messages) installed directly into your project.
See: Widget Installation, Frontend Setup
Next Steps
Last modified on May 30, 2026
