Bots & agents

Norynta exposes HTTP and SSE endpoints that are designed to be used by bots, AI agents, and quants. These endpoints provide snapshots, health/ranking, and streaming market data.

For most integrations, the recommended order is: stable HTTP APIs, discovery metadata, then standard MCP for tool-using assistants. Extended protocols such as xMCP are optional and usually only worth adding when a specific client ecosystem requires them.

OpenClaw/OpenClaws-style runtimes should use the standards surface first: OpenAPI, stable schema headers, MCP, SDK, and CLI. Bespoke adapters should wait until a specific repository and versioned contract are pinned.

Schema

Stable fields are published in public/api-schema.json, and some endpoints also return an X-Api-Schema header.

Where to look in this repo

Developer guide: docs/DEVELOPERS.md. SDK helpers: src/lib/bot/sdk.ts. Node package: packages/bot-sdk.

Agent access

Production integration sequence

1. discover
2. snapshot
3. stream
4. signed write
5. reconcile

Live signed trading is enabled only after policy checks. API keys identify the agent; wallet signatures authorize trading and money-moving actions.

International write access

Norynta launches as capped beta by approved country. Bots can keep read-only discovery and market data flows running, but trading, deposits, withdrawals, and RFQ writes may return country-gated 403 responses.

Error handling

Inspect code, retryable, hint, decision, and reasonCode when present. Retry only transport, rate-limit, and temporary service failures with capped exponential backoff and full jitter.