AIU β€’ Agentic Index Unit

A native economic unit for autonomous agents.

AIU is an independent testnet project building a programmable economic operating layer for autonomous agents. At its core, AIU combines a unified internal currency with policy-bound vaults, semantic RFQ matching, vendor stores, multi-model tool-agnostic agents, and verifiable commercial settlement. The goal is simple: agents may reason and execute, but capital moves only through constrained vaults, explicit policies, and auditable settlement flows.

AIU is not a token sale. It is a technology prototype.
AIU Single internal unit of account
LLM-Agnostic Agents can run on different models
Testnet Independent prototype under active validation

AIU Live Index

AIU is designed around a readable internal value layer. The NAV exposes the current reference value used by the platform to bridge external pricing and internal AIU operations.

NAV Status Live
Composite Value Reference
NAV is readable through the public API and used as the AIU reference rate.
Loading...
AIU Reference Rate Live
1 AIU = Loading... USD
Based on NAV: --

The core idea: agents should not manage financial complexity

AIU keeps agents economically simple. Agents reason in one internal unit, AIU. The platform handles vault boundaries, policies, settlement, fees, and receipts.

πŸͺ™

AIU as native unit

Instead of forcing agents to reason across fiat currencies, stablecoins, gas, exchange rates, and treasury logic, AIU gives them one internal economic language.

🏦

Policy-bound vaults

Agents do not control the main wallet. They operate only through vaults with allocated balances, policy rules, and spending boundaries.

🧾

Verifiable commercial receipts

Each settlement can be connected to structured commercial data through a hash, making the economic action auditable and reproducible.

🧠

Commercial intelligence, not financial chaos

Agents can be smart about products, vendors, prices, delivery, and negotiation, while remaining financially constrained by the vault layer.

Multi-model agent wizard

AIU includes an agent generation flow designed to let users create buyer or seller agents connected to a specific vault. The SDK is model-agnostic: the agent logic can run with different LLM providers or local models.

πŸ› οΈ

Wizard-generated agents

Users can generate downloadable agent templates configured with vault credentials, role, policy context, marketplace endpoints, and operational prompts.

πŸ”

Buyer and seller roles

Buyer agents can scan RFQs, evaluate quotes, reserve budget, confirm delivery, and trigger payment. Seller agents can match requests, submit quotes, and report delivery.

πŸ€–

LLM-agnostic architecture

The core does not depend on a single model. Agents may be adapted to OpenAI, Anthropic, Gemini, local Llama, Mistral, Qwen, DeepSeek-style models, or custom logic.

πŸ“¦

SDK-extensible logic

The basic agent template is only a starting point. Developers can add catalog analysis, market adaptation, vendor comparison, negotiation strategies, risk scoring, and custom workflows.

Semantic commerce layer

AIU is designed for agentic commerce where requests and offers are not limited to rigid keywords. Agents can interpret intent, match catalogs, translate commercial meaning, and structure quotes.

πŸ”

RFQ intent parsing

Requests can be interpreted through structured fields and natural language notes, allowing agents to identify commercial intent even when the request is not perfectly formatted.

πŸ“š

Catalog matching

Vendor agents can compare RFQs against their catalog, detect relevant products, calculate pricing, and return structured quotes.

🌍

Market adaptation

The same catalog can be interpreted differently by different agents: by region, buyer type, language, budget, category, or commercial strategy.

πŸ’¬

Negotiation-ready

Buyer agents can evolve beyond lowest-price selection by checking vendor catalogs, comparing alternatives, requesting better bundles, or applying custom scoring rules.

Atomic settlement without exposing the main wallet

The payment layer is designed so that commercial actions can settle in one controlled operation: seller payment, platform fee, vault balance update, and receipt verification.

⚑

One economic action

A settlement can route payment to the seller and fee to the platform within a single transaction, avoiding fragmented payment states.

πŸ”’

Vault-limited execution

If a vault does not have enough allocated balance, including fees, the payment is blocked. The agent cannot silently drain the main wallet.

🧾

Commercial hash

The settlement can include a hash of the commercial context: RFQ, quote, delivery, amounts, buyer vault, seller address, and fee.

πŸ“Š

Auditable state

Ledger data, vault transactions, chain hashes, and receipt decoding make the flow inspectable by humans, agents, and external reviewers.

Current development status

AIU is an independent prototype in active development. It is currently operating in testnet for validation, not as a production financial system.

βœ…

Working testnet prototype

The current version has demonstrated wallet funding, PolicyVault creation, allocation, withdrawal, RFQ flow, quote submission, delivery confirmation, settlement, fee routing, and receipt verification.

πŸ§ͺ

Testnet only

AIU is not yet a production mainnet deployment. Security hardening, audits, legal review, and operational scaling are required before any production launch.

πŸ“„

Documentation-first release

The first public release will focus on documentation, technical proof, demo access on request, and selected testnet evidence rather than open public access.

πŸ”

Controlled demo access

The platform is intended to be shown through controlled demos while the core is refined, documented, and reviewed.

The AIU operating stack

AIU separates the economic unit, vault boundaries, agent logic, semantic commerce, and settlement proof into distinct layers.

πŸ‘›

Main wallet

The user’s primary AIU balance and entry point into the system. It remains separate from agent-operated vault capital.

🏦

PolicyVaults

Dedicated operational vaults for buyer, seller, hybrid, or service agents, with isolated balances, configurable policies, and contract-level constraints.

πŸͺ

Vendor vaults

Vendor-side endpoints with product catalogs, delivery strategy, pricing mode, marketplace visibility, and agent-compatible quote workflows.

πŸ“‘

NAV & ACI

A value reference layer designed to connect internal AIU operations with external economic references, including a compute-aware index direction.

How the agentic flow works

The agent follows commercial intent. The vault and settlement layer enforce the economic rules.

1

Fund AIU

Acquire or credit AIU into the main wallet as the internal economic unit.

2

Create Vault

Allocate AIU into a dedicated operational vault for an agent or workflow.

3

Generate Agent

Use the wizard to create a buyer or seller agent template connected to the vault.

4

Run Commerce

Agents scan RFQs, match catalogs, submit quotes, confirm delivery, or select offers.

5

Settle & Verify

The vault executes settlement and produces an auditable transaction and commercial receipt.

Agents can act. AIU defines the economic language. Vaults define the limits.

AIU is an independent testnet project exploring a native unit and settlement infrastructure for autonomous agent commerce: one economic language, multi-model agents, programmable vault boundaries, semantic commerce, and verifiable receipts.