Skip to content
Docs

Norynta public docs

Norynta Agent And Bot Readiness Checklist

Checklist for connecting AI agents, liquidity bots, market makers, and quant clients to Norynta.

Agent and Bot Readiness Checklist

Use this checklist before connecting an AI agent, liquidity bot, market maker, or quant client to Norynta.

Canonical Integration Flow

  1. Discover capabilities:
    • GET /.well-known/agent.json
    • GET /api/agent/card
    • GET /api/agent/access
    • GET /api/bot/config
  2. Load markets:
    • GET /api/events/health
    • POST /api/events/snapshots
  3. Maintain live state:
    • GET /api/events/:slug/stream
    • GET /api/events/:slug/orderbook/stream
  4. Simulate writes:
    • GET /api/clob/v2/orderbook
  5. Submit signed writes only after first-trade check:
    • POST /api/clob/v2/orders
    • POST /api/clob/v2/rfq/quote
    • POST /api/clob/v2/rfq/accept
  6. Reconcile:
    • POST /api/clob/v2/my-orders
    • periodic snapshots after stream reconnects

Required Client Behavior

  • Use Authorization: Bearer <token> for API-key identity when keys are issued; x-api-key remains supported for compatibility.
  • Use wallet signatures for trading authority. API keys identify the agent; wallet signatures authorize money-moving actions.
  • Use clientOrderId or idempotency-key for write retries.
  • Reuse the same signed payload when retrying transport failures.
  • Treat idempotent_replay: true as a successful retry outcome.
  • Simulate before submitting live taker flow.
  • Use limit orders to provide liquidity when the book is empty; do not assume house liquidity or opposite-side depth is present.
  • Stop write submission when discovery reports tradingWritePaused, disabled live trading, or country-gated 403 responses.

Error Handling

Machine clients should inspect code, retryable, hint, decision, and reasonCode when present.

  • GEO_BLOCKED, GEO_UNKNOWN, REAL_MONEY_COUNTRY_NOT_ALLOWED, and REAL_MONEY_COUNTRY_NOT_APPROVED: do not retry through VPNs or proxy country spoofing.
  • UNAUTHORIZED: refresh credentials; do not retry blindly.
  • RATE_LIMITED: back off with jitter and preserve idempotency identity.
  • TRADING_PAUSED or live-trading disabled text: continue read-only reconciliation and stop writes.
  • Signature, nonce, schema, and validation errors: correct the payload before retrying.

International Access

Norynta runs public growth with country controls. Bots and agents must not assume worldwide real-money access. Read-only data may be usable while trading, deposits, withdrawals, RFQ, and order writes remain country-gated.

Liquidity Bots And HFT-Style Clients

HFT-style clients should treat Norynta as a user-liquidity venue. During the current rollout, readiness depends on real user, partner, or external bot orders, not house/operator liquidity.

  • Maintain local orderbook state from snapshots plus streams.
  • Prefer small, bounded resting limit orders before increasing size.
  • Preserve idempotency keys and client order IDs across retries.
  • Stop writes when trading is paused, market status changes, liquidity becomes stale, or reconciliation is uncertain.
  • Do not expect the house to seed an empty book.

Validation Commands

npm run agent:quickstart
npm run agent:conformance
npm run openapi:check
npm run check:agent-docs