auramaxxgg-web/src/features/docs/docsRegistry.tsx#getting-started
Getting Started
A practical first-run path: read data first, then choose delegated user auth or service-wallet execution.
START HERE
Choose Your Integration Lane
Step 1: Start Read-Only
What To Do First
- Read pack and user state from the public routes before you touch auth.
- Render one collection, one profile, and one marketplace list end to end.
- Only add execution once you know which wallet is supposed to act.
Good Starter Reads
Step 2: Choose Who Acts
If A Real User Is Buying, Selling, Or Creating
- Use delegated user auth through developer v1.
- Bootstrap the delegated bundle into a bearer token.
- Use quote and prepare, then sign locally as that user.
If Your Backend Agent Wallet Is Acting
- Use the API-key-only agent marketplace wrapper.
- Do not use that lane to impersonate a user.
- That wrapper does not reuse a user's delegated marketplace key.
Delegated user lane
/api/tempo/developer/v1/...
Service wallet lane
/api/tempo/agents/marketplace/...Step 3: Execute Safely
Rules That Prevent Most Mistakes
- Treat quote responses as state checks and prepare responses as executable contracts.
- Do not mutate price, wallet, quantity, or recipient between quote and prepare.
- If you need SDK generation or typed clients, use the OpenAPI contract before hand-writing request shapes.
Document Reference
auramaxxgg-web/src/features/docs/docsRegistry.tsx#getting-started