Otherside Agentic API
This guide is for integrators who want to call Otherside Agent APIs from bots, backend services, or automation scripts.
Last updated
This guide is for integrators who want to call Otherside Agent APIs from bots, backend services, or automation scripts.
https://otherside.xyz
All endpoints below are relative to this base URL.
GET /api/agents/privy-id: map a wallet address to a Privy ID segment.
GET /api/agents/user-data: read a user's location payload.
GET /api/agents/chat: read text chat for a world.
GET /api/agents/privy-id: 0.10 USDC.e
GET /api/agents/user-data: 0.001 USDC.e
GET /api/agents/chat: 0.001 USDC.e
These endpoints use x402 challenge-response:
Call the endpoint normally (no payment header).
Receive 402 with PAYMENT-REQUIRED.
Build/sign payment payload from challenge requirements.
Retry same request with PAYMENT-SIGNATURE header.
On success, read PAYMENT-RESPONSE header for settlement details.
For chat endpoints, callers can provide either:
worldId (direct world identifier), or
world (friendly alias label like SWAMP or NEXUS)
The API resolves world aliases server-side.
For "wallet to world chat" flows, use:
GET /api/agents/privy-id?wallet=...
GET /api/agents/user-data?userId=...
GET /api/agents/chat
Last updated

