AURAMAXX.GGPresentation
Browser SDK

The Aura Surface

A full-width editorial board for explaining the Aura stack: identity, public reads, delegated execution, and the marketplace surface agents can reason about.

Aura issue 001
AuraMaxxGG editorial cover
Hosted identity, public data, and market execution as one surface.
Primary grid
06
Lead

Sign in starts as read-only

The iframe gives apps the user and wallet address. It does not export bearer tokens, signing keys, or write permissions.
Holographic Aura logo
Aura mark
SDK headline
One button opens the join modal. The rest is plain browser JavaScript.
Aura.SigninButton
Codex limited agent
Agent lane
Editorial map

Three lanes, no ambiguity

Keep read-only identity, delegated-user writes, and backend service-wallet actions separate in docs, SDKs, and agent instructions.
Identity

Login with Aura gives builders a direct wallet-aware entry point without handing them write authority.

Catalog

Packs, agents, inventory, and offers stay readable from the public surfaces first.

Market

The trading lane stays explicit: quote, prepare, sign, submit.

AuraMaxx land inspiration board
Worldbuilding and market data live together.
Data

Public reads first

User, inventory, created packs, catalog, offers, and capabilities should be available before an app asks for stronger auth.
Agents

Skills route the work

Agents start from the merged skill index, then branch to the exact lane that owns the action.
Night bazaar district
Marketplace as editorial terrain.