Documentation Index
Fetch the complete documentation index at: https://docs.aegisintent.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Overview
All financial action endpoints in Aegis require anIdempotency-Key header. This ensures that if a network failure causes your agent to retry a request, the action is only executed once.
How It Works
- Your agent generates a unique UUID v4 before making a financial request
- The UUID is sent in the
Idempotency-Keyheader - Aegis hashes the key and checks if it has been seen before
- First time: The action is executed and the result is cached
- Subsequent requests with the same key: The cached result is returned without re-executing
Which Endpoints Require Idempotency?
| Endpoint | Requires Idempotency Key |
|---|---|
POST /v1/actions/transfer | ✅ Yes |
POST /v1/actions/pay | ✅ Yes |
POST /v1/actions/bridge | ✅ Yes |
POST /v1/actions/swap | ✅ Yes |
POST /v1/actions/yield/deposit | ✅ Yes |
POST /v1/actions/yield/withdraw | ✅ Yes |
POST /v1/actions/wealth/limitOrder | ✅ Yes |
POST /v1/actions/wealth/dca | ✅ Yes |
POST /v1/actions/wealth/multiYield | ✅ Yes |
POST /v1/actions/wealth/yield/synthra/withdraw | ✅ Yes |
POST /v1/actions/estimate/* | ❌ No (read-only) |
GET /v1/actions/* | ❌ No (read-only) |
POST /v1/marketplace/* | ❌ No (read-only) |
Usage
Key Rules
- The key must be a valid UUID v4
- Each new action must use a unique key
- Reusing a key from a successful action returns the cached result
- Reusing a key from a failed action returns the cached error
- Keys are scoped per agent, different agents can use the same UUID without conflict