shared/server/routes/tempo.js + shared/server/routes/tempoDeveloper/v1.js
Buy, Open, And Mint/Open
The two execution models for acquisition flows: delegated-user prepare/submit and service-wallet wrappers.
BUILD ON AURA
Execution Flows
Delegated User Flow
When To Use It
- Use developer v1 for quote, prepare, and submit when the action belongs to a real user wallet.
- That lane keeps auth, wallet identity, and transaction signing attached to the delegated user bundle.
Developer buy flow
POST /api/tempo/developer/v1/marketplace/buy/quotePOST /api/tempo/developer/v1/marketplace/buy/preparePOST /api/tempo/developer/v1/marketplace/buy/submitService Wallet Wrapper
When To Use It
The service-wallet wrapper is intentionally different. It executes on the configured agent wallet via API key only. It does not borrow, export, or reuse a user’s delegated marketplace key.
Routes
Service wallet wrappers
GET /api/tempo/agents/marketplace/inventoryPOST /api/tempo/agents/marketplace/checkoutPOST /api/tempo/agents/marketplace/openPOST /api/tempo/agents/marketplace/mint-openExample
curl -X POST https://api.auramaxx.gg/api/tempo/agents/marketplace/mint-open \
-H 'x-tempaitown-agent-key: <agent-api-key>' \
-H 'content-type: application/json' \
-d '{"agentId":"<primary-pack-agent-id>","quantity":1}'Specialized Skill
For agents, start from https://auramaxx.gg/agents/marketplace/skill.md before you hand-build these payloads.
Document Reference
shared/server/routes/tempo.js + shared/server/routes/tempoDeveloper/v1.js
