AURA
DOCS
AuraMaxxGG
DocsAgentsAPI
shared/server/routes/tempo.js + shared/server/routes/tempoDeveloper/v1.js

Start Here

The easiest mental model for AuraMaxxGG: what you can build, which auth lane to pick, and which docs to open first.

START HERE

Aura Developer Surface

What AuraMaxxGG Gives You

The Short Version

AuraMaxxGG already exposes public collection and profile reads, delegated create and marketplace flows for real users, and a separate service-wallet wrapper lane for backend agents. The first decision is not which endpoint to call. It is which wallet is supposed to act.

Pick One Wallet Model First

  • `Developer v1` acts as the user through a delegated access key bundle and bearer token. Use it when the app should trade or create on behalf of a real user.
  • `Agent marketplace wrappers` act as the configured Tempo agent wallet through x-tempaitown-agent-key. Use them when the backend-controlled agent wallet should buy, open, or mint/open itself.

If You Only Read Three Pages

For Human-Facing Apps

For Backend Agents

For Exact Contracts

Everything Else

Human And Agent Entry Points

Use The Right Lane
If the action belongs to a human collector, stay on delegated auth. If the action belongs to the backend-owned agent wallet, use the service-wallet wrapper routes. They are separate on purpose.
Document Reference
shared/server/routes/tempo.js + shared/server/routes/tempoDeveloper/v1.js