Skip to content
Docs

Norynta public docs

Norynta API Overview

High-level map of Norynta public APIs, SDKs, schemas, discovery, market data, and trading surfaces.

API Overview

Current product mode (2026-07-28): Norynta is play-only. Real-money trading, deposits, withdrawals, cash payouts, yield, and mainnet execution are postponed until further notice. Any such workflow retained below is historical or implementation reference, not an available product capability. See PLAY_MODE_GUIDE.md.

Purpose

This document gives external developers a high-level map of Norynta's public integration surface.

Audience

  • API integrators
  • bot and AI agent developers
  • technical partners
  • trading infrastructure teams

How to think about the API

Norynta's external API is easiest to understand in six layers:

  1. Discovery — learn capabilities, contracts, and auth expectations
  2. Market data — fetch markets, health, rankings, and snapshots
  3. Streaming — maintain live state with low-latency updates
  4. Trading — check, place, cancel, and reconcile signed writes
  5. Funding and account data — deposits, withdrawals, balances, and statements
  6. Tooling — use SDKs, CLI helpers, and examples to reduce integration time

If you are building an automated integration, start with discovery first.

1. Discovery and schema

Primary endpoints:

  • GET /.well-known/agent.json
  • GET /api/agent/card
  • GET /api/agent/access
  • GET /api/bot/config
  • GET /api/international/access
  • GET /api/rate-limits
  • GET /api/markets/policy
  • GET /openapi.json
  • GET /api-schema.json

What these tell you:

  • protocol capabilities
  • execution hints
  • auth expectations
  • retry and idempotency guidance
  • rate-limit budgets
  • sensitive-market and market-integrity policy
  • detected country source and real-money availability
  • stable schema versions
  • machine-readable contracts

2. Market data

Primary endpoints:

  • GET /api/v1/events
  • GET /api/events
  • GET /api/events/health
  • GET /api/events/:slug/health
  • GET /api/events/:slug/snapshot
  • POST /api/events/snapshots
  • GET /api/events/snapshots?slugs=a,b
  • POST /api/events/bot-snapshot
  • GET /api/events/top
  • POST /api/events/health-snapshots
  • GET /api/events/health-snapshots?slugs=a,b
  • GET /api/markets/requests
  • GET /api/markets/requests/launch-packs
  • GET /api/markets/requests/maker-kit?queue=1
  • GET /api/markets/requests/maker-kit?id=123

Recommended use cases:

  • discover which markets to track
  • rank opportunities
  • seed state before streaming
  • refresh state in bulk
  • recruit external first liquidity without funding house market making

3. Streaming

Primary endpoints:

  • GET /api/events/:slug/stream
  • GET /api/events/:slug/orderbook/stream

Recommended use cases:

  • live trade monitoring
  • orderbook maintenance
  • low-latency strategy triggers
  • reconciliation between polling intervals

4. Trading

Primary endpoints:

  • POST /api/v1/orders
  • POST /api/v1/orders/batch
  • DELETE /api/v1/orders
  • POST /api/clob/v2/orders
  • DELETE /api/clob/v2/orders
  • POST /api/clob/v2/orders/batch
  • POST /api/clob/v2/my-orders
  • GET /api/clob/v2/orderbook
  • GET /api/clob/v2/config
  • GET /api/fees/estimate
  • GET /api/treasury/fee-config
  • POST /api/clob/v2/rfq/quote
  • POST /api/clob/v2/rfq/accept
  • GET /api/clob/v2/rfq/network
  • POST /api/clob/v2/cancel-all
  • DELETE /api/clob/v2/cancel-all
  • DELETE /api/clob/v2/cancel-market-orders

Recommended use cases:

  • pre-trade checks
  • exact fee estimation before submission
  • signed order placement
  • quote-driven taker flow
  • RFQ network capability discovery
  • open-order reconciliation
  • controlled cancellation and invalidation

5. Funding and account data

Primary endpoints:

  • GET /api/v1/deposit-options
  • GET /api/withdrawal-options
  • GET /api/payment-rails/countries?country=US
  • GET /api/v1/accounts/:publicKey/deposit-address
  • GET /api/v1/accounts/:publicKey/withdraw-address
  • GET /api/v1/accounts/:publicKey/balance
  • GET /api/v1/accounts/:publicKey/transactions
  • GET /api/v1/accounts/:publicKey/statement
  • GET /api/v1/accounts/:publicKey/deposits
  • GET /api/v1/accounts/:publicKey/withdrawals
  • POST /api/v1/accounts/:publicKey/withdrawals

Recommended use cases:

  • show available deposit rails
  • request a Solana, Base/EVM, or bridge deposit address
  • prepare an external-chain withdrawal destination
  • reconcile cash balance, ledger transactions, deposits, and withdrawals
  • track a withdrawal transaction hash after funds leave the Norynta vault

Deposit and withdrawal history includes rail-neutral settlement metadata alongside legacy Solana-compatible fields, so clients can reconcile Solana, Base/EVM, bridge, card onramp, and local payout rows through the same settlement_network, settlement_adapter, provider, rail, and transaction fields.

These routes require signed secure-action context for user-specific data: x-signature plus nonce, domain, cluster, and expiresAt.

6. Tooling and integration helpers

  • External SDK: packages/bot-sdk/src/sdk.ts
  • Class-based API client: NoryntaClient from @norynta/bot-sdk
  • Internal SDK: src/lib/bot/sdk.ts
  • CLI: norynta ... from the SDK package, or npm run bot:cli -- ... locally
  • Examples: examples/README.md

Recommended integration order

  1. Discover schema and capabilities.
  2. Fetch health and bulk snapshots.
  3. Start live streaming.
  4. Simulate intended writes.
  5. Submit signed orders.
  6. Reconcile orders, balances, deposits, withdrawals, and trades continuously.

Most common integration paths

Read-only market monitor

Use:

  • discovery endpoints
  • health endpoints
  • bulk snapshots
  • event stream

Bot or AI agent

Use:

  • discovery endpoints
  • /api/bot/config
  • /api/bot/config execution.onboarding, execution.errorTaxonomy, and execution.internationalAccess
  • snapshots + streaming
  • optional first-trade check and write paths

Professional trading system

Use:

  • full discovery set
  • bulk snapshots for ranking
  • stream-based live maintenance
  • first-trade checks before aggressive writes
  • deterministic request identity for writes

Source-of-truth references

  • OpenAPI contract: public/openapi.json
  • AsyncAPI contract: public/asyncapi.json
  • Stable schema fields: public/api-schema.json
  • Human endpoint reference: docs/public/API_REFERENCE.md
  • Canonical agent guide: docs/AGENT_INTEGRATION.md
  • Canonical external developer guide: docs/DEVELOPERS.md

Related docs

  • docs/public/DEVELOPER_QUICKSTART.md
  • docs/public/API_REFERENCE.md
  • docs/public/MARKET_DATA_DISCOVERY.md
  • docs/public/ORDERBOOK_AND_PRICING.md
  • docs/public/ERROR_CODES.md
  • docs/public/AGENT_BOT_READINESS_CHECKLIST.md
  • docs/public/AUTH_AND_RATE_LIMITS.md
  • docs/public/SDK_AND_EXAMPLES.md
  • docs/public/TRADING_INTEGRATION_WORKFLOW.md
  • docs/public/STREAMING_AND_RECONCILIATION.md