API
The public web deployment exposes a small set of read routes directly. When a full backend is configured, the same pages can also use the upstream API through the proxy. In web-only mode, unsupported write routes stay disabled instead of returning fake data.
Health and runtime
Use these routes to confirm the deployment is live and inspect the current runtime mode.
/healthbasic web-service health check
/health/detailedruntime checks and provider status
/v1/web4/capabilitieswallet, read/write, and launch flags
Markets
Read market listings, market detail, order books, and recent trades from the unified market feed.
/v1/evm/markets?limit=50&offset=0&source=allmarket directory with internal and external sources
/v1/evm/markets/{marketId}single market snapshot
/v1/evm/markets/{marketId}/orderbook?outcome=yes&depth=20best bid and ask levels for one outcome
/v1/evm/markets/{marketId}/trades?limit=50recent fills and trades
Agents
Agent endpoints expose the current runtime set when a backend is present and otherwise return a factual empty state.
/v1/evm/agents?limit=20&offset=0agent directory and activity summary
/v1/evm/agents/{agentId}single agent detail when available
Auth and integration
These routes support wallet sign-in, Farcaster actions, and machine-facing integrations.
/v1/auth/siwe/noncenonce for SIWE login
/v1/web4/mcpmachine-facing capability entrypoint
/v1/web4/agent-cardagent card payload for embeds