HUMAN INTERFACE

One integration across every product surface.

Put the same chat-to-transaction experience used by Aomi Portal where your users already are: embedded in your product, or in a Telegram bot you register in minutes. Bring your application, authentication, and signer. Aomi brings the execution harness.

Start integratingOpen live Portal

Web widget · Telegram · Portal · EVM + Solana · browser, Para, or Privy authentication

IN PRODUCTION Sommelier ships its liquidity assistant on this surface.

Live product surfacechat.aomi.dev
InstallOne component
SurfacesWidget · Telegram · Portal
NetworksEVM + Solana
Keys held by AomiZero

INTEGRATION MODEL

One application across every surface, under customized API contracts

01

Build the Aomi app

Existing product endpoints are wrapped as a curated set of typed tools, governed by an operating mandate, and deployed to Aomi's hosted runtime. Exposure limits, venue allowlists, and authorization requirements are enforced as execution policy outside the model.

02

Integrate any customer surface

The same hosted app is delivered through an embedded Widget, a registered Telegram bot, or Aomi Portal. One application, every channel, with no additional integration work per surface.

03

Retain the existing wallet infrastructure

Browser wallets, embedded providers such as Para and Privy, Safe, or an institutional signer remain the authority. Aomi constructs and simulates the exact payload; the designated signer approves it. No private keys are held by Aomi.

INSTALL AND CONFIGURE

Own the integration. Keep the execution runtime.

Install the packaged widget, bind one application ID, and choose the authentication and wallets that already belong in your product.

npm install @aomi-labs/widget-lib
Read integration documentation

Browser mode authenticates an existing EOA. No Para or Privy provider import required.

"use client"; import { AomiWidget } from "@aomi-labs/widget-lib";import "@aomi-labs/widget-lib/styles.css"; export default function AssistantPage() {  return (    <AomiWidget      applicationId={process.env.NEXT_PUBLIC_AOMI_APPLICATION_ID!}      apiUrl={process.env.NEXT_PUBLIC_AOMI_API_URL!}      auth={{ kind: "browser_wallet" }}      height="calc(100dvh - 32px)"    />  );}

YOUR PRODUCT BOUNDARIES

Bring the identity and signer your users already trust.

Browser wallets

MetaMask, Rabby, Coinbase Wallet, WalletConnect, and the signer your users already know.

Embedded wallets

Register Para or Privy only when you want their authentication session and embedded-wallet experience.

Application policy

An Aomi application ID selects the backend-owned execution, sponsorship, and fee policy for every widget action.

THE EXECUTION BOUNDARY

A visible checkpoint at every stage.

  1. 01

    Intent

    Your user asks in plain language.

  2. 02

    Construct

    Aomi resolves tools, venue, route, and calldata.

  3. 03

    Simulate

    The complete action is rehearsed before approval.

  4. 04

    Sign

    The user's existing wallet authorizes the exact payload.

SHIP THE SURFACE

Put Aomi where your users already are.

Start buildingTalk to us