# Tempo Agent Skill

Use this skill as the top-level router for Aura and Tempo agent work. Start here, decide which wallet is supposed to act, then move into the specialized skill for that lane.

- Generated: 2026-04-17T14:10:09.239Z
- Site: https://auramaxx.gg
- API base: https://api.auramaxx.gg
- Docs shell: https://auramaxx.gg/docs
- API shell: https://auramaxx.gg/api
- Agent shell: https://auramaxx.gg/agents
- Skills page: https://auramaxx.gg/skills.md
- Sign in with Aura: https://auramaxx.gg/docs/sign-in-with-aura
- LLM index: https://auramaxx.gg/llms.txt
- Public Tempo capabilities: https://api.auramaxx.gg/api/tempo/capabilities
- Developer v1 capabilities: https://api.auramaxx.gg/api/tempo/developer/v1/capabilities

## Fastest start

- When unsure, read the merged skills page first: https://auramaxx.gg/skills.md
- Pick the lane before building payloads: public read, delegated-user developer v1, or service-wallet wrapper.
- After choosing the lane, open the specialized skill below and treat it as the source of truth for request shape and auth.

## First decision

- If you only need reads, stay on the public read routes and the docs shells. Do not bootstrap auth just to inspect pack or user state.
- If a browser app needs the current user wallet for read-only UI, use Sign in with Aura first. It returns a user and wallet address, not a bearer token.
- The hosted Login with Aura SDK includes read-only helpers such as `Aura.getUser`, `Aura.getInventory`, `Aura.getCreatedPacks`, `Aura.getDeveloperCapabilities`, `Aura.getMarketplaceCatalog`, and `Aura.getMarketplaceOffers`.
- If a real user should create, buy, sell, offer, or transfer, use the delegated-user developer lane.
- If the backend-owned Tempo agent wallet should act directly, use the API-key-only service-wallet wrapper lane.

## Which specialized skill to open

- Delegated mint or onboarding agent mint: https://api.auramaxx.gg/skill.md
- Create or submit new collections: https://api.auramaxx.gg/create/skill.md
- Delegated live trading with a human user's access key: https://api.auramaxx.gg/bazaar/trading.md
- Service-wallet checkout, open, or mint/open: https://api.auramaxx.gg/agents/marketplace/skill.md
- Versioned developer API skill reference: https://api.auramaxx.gg/api/tempo/developer/v1/skill.md

## Default routing rules

1. Read the public docs and current state first.
2. Decide whether the action belongs to a human user wallet or the configured backend service wallet.
3. For delegated-user work, bootstrap the local access-key bundle into a bearer token and stay under `/api/tempo/developer/v1/**`.
4. For service-wallet work, send `x-tempaitown-agent-key` and stay under `/api/tempo/agents/marketplace/**`.
5. Use the specialized skill above before building payloads by hand.

## Guardrails

- Do not use the service-wallet wrapper to impersonate a user.
- Do not reuse a user's delegated marketplace key on the service-wallet routes.
- Do not mix API-key auth and delegated-user bearer auth in the same transaction flow.
- Prefer the capabilities manifests, docs shell, and llms.txt when you need discovery before execution.