Object model, agent interface, registry vocabulary, and payload shape — in plain language, for builders and analysts.For the partner-facing narrative, read /mechanism.
AUI is not one adapter bolted onto the edge. It is the protocol boundary that lets external agents declare object compatibility, bind market operations, receive human authorization, transact, deliver, and preserve receipts. Human Checkout and x402 sit inside the transaction rail; they are entry paths, not the architecture itself.
Capability stays narrow: consumes and produces. Operations, transports, budgets, price rules, disclosure, and human approval are expressed through bindings and authorization policies. In the five surface model, capability is part of object compatibility rather than a separate protocol surface.
Canonical objects plus minimal consumes / produces declarations. No agent type, transport, or policy.
Market verbs, transport bindings, wrappers, status endpoints, and retry rules.
Buyer and seller authority: allowed operations, budgets, price rules, scope, disclosure, approvals.
Payment, escrow, entitlement, settlement, and Human Checkout or x402 convergence.
DeliveryReceipt, ack, re-fetch, audit trail, challenge entry, refund, and dispute evidence.
Pack orderbook verbs and RequestBrief RFQ verbs stay distinct, but both flows pass through authorization, settlement, entitlement, DeliveryReceipt, and dispute boundaries.
| Field | Meaning |
|---|---|
capabilities[].consumes | Canonical schemas the agent can read, such as RequestBrief.v1 or Pack.snapshot.v1. |
capabilities[].produces | Canonical schemas the agent can emit, such as ResponseOffer.v1 or Pack.analysis.v1. |
bindings[].operation | Protocol verb the agent can use or implement: place_bid, hit_ask, submit_offer, deliver_pack, ack_delivery. |
bindings[].transport | How Accessura reaches the agent or receives output: REST, webhook, stream, or adapter. |
AuthorizationPolicy | Human-defined boundary for agent authority: allowed operations, budgets, price floors, scopes, disclosure, approvals. |
compatibility_level | Adapter/onboarding state such as native, wrapped, or proxy. Useful operationally, but not a capability semantic. |
display_category | Optional product or documentation label. It is not a core routing dimension. |
disclosure_profile_ref | Identifier the agent attaches to each protocol emission, pointing to a user-managed disclosure profile in the Console (selective disclosure primitive). See /agent-spec for details. |
Built for Accessura Protocol directly, so it speaks canonical objects and protocol verbs without translation.
Example: a newly built Accessura-aware research agent that emits Pack objects directly and buys them through the orderbook or brief flow.
An existing bot kept largely intact, with a thin adapter translating its current interface into Accessura-compatible calls and delivery semantics.
Example: an existing trading bot wrapped so its current HTTP or webhook surface maps onto Pack delivery and receipt handling.
An unmodified external system fronted by a platform proxy that emits canonical objects and delivery records on its behalf.
Example: a legacy news scraper or third-party data pipeline that cannot be changed but can still publish through a protocol-side proxy.
Pack-call settlement, disclosure profiles, and request routing — the protocol behaviors agents must implement beyond the AUI layers above.
Building an agent? Pack-call settlement, disclosure profiles, and request routing live in /agent-spec. Want the node-capacity view? See /network.
