Skip to content
Docs

Norynta public docs

Norynta Bot And Agent Operations Checklist

Operational checklist for monitoring and safely opening Norynta to automated clients and liquidity bots.

Bot and Agent Operations Checklist

Use this checklist while opening Norynta to automated clients, liquidity bots, and AI agents.

Launch Controls

  • Keep live write access capped until npm run agent:conformance and production smoke checks pass.
  • Require API keys for professional bots when BOT_API_KEYS is configured.
  • Require wallet signatures for all trading and money-moving authority.
  • Keep first-trade-check behavior in onboarding, examples, and support replies.
  • Verify baseline writes from detected-country and unknown-country probes.
  • Keep HFT-style execution in read-only/shadow mode until HFT_LITE_GATE_CANDIDATE_LIMIT=10 npm run check:prod:hft-shadow passes on real non-excluded user, partner, or external bot liquidity.
  • Do not use house, operator, or canary wallets to satisfy bot/HFT liquidity gates.

Monitoring Signals

Track these signals daily during public growth:

  • unexpected country block events or country-gating failures
  • bot API errors by status and machine-readable code
  • agent key usage by key id, plan, endpoint, and quota profile
  • rate-limit events by scope and caller
  • trading write blocks from circuit breakers, pauses, and live-trading flags
  • HFT gate blockers, especially no_liquid_markets
  • two-sided depth from non-excluded owners
  • support contact rate for access, deposit, withdrawal, and API-key confusion

Response Playbook

  • If country blocks spike, confirm Vercel/Cloudflare country headers and review docs/PUBLIC_GROWTH_COUNTRY_GEO_PROBES.md.
  • If RATE_LIMITED spikes, ask clients to use backoff with full jitter and assign per-agent keys instead of shared generic traffic.
  • If trading-write blocks spike, keep clients read-only until /api/agent/access write controls return healthy.
  • If the HFT gate reports no_liquid_markets, keep HFT-style clients in shadow/read-only mode and route liquidity partners toward resting limit orders. Do not seed the book with house/operator wallets.
  • If signature failures spike, point clients to wallet-signature headers and deterministic idempotency guidance in docs/public/AGENT_BOT_READINESS_CHECKLIST.md.
  • If support requests cluster by country, review localization priority in docs/INTERNATIONAL_LAUNCH_READINESS.md.

Release Gates

Before broadening bot access, run:

npm run openapi:check
npm run check:agent-docs
npm run agent:quickstart
npm run agent:conformance
npm run check:prod:public-growth-countries
HFT_LITE_GATE_CANDIDATE_LIMIT=10 npm run check:prod:hft-shadow

The HFT gate may fail closed with no_liquid_markets during early public growth. That is acceptable until real user or partner liquidity exists.