Nordstern

Rate Limits

The Nordstern API has no fixed rate limit for normal usage — only automated spam is blocked.

Automated spam and bot behaviour is blocked at the network level, but legitimate integrations (including high-frequency applications) are not subject to hard quotas.

Best practices

Even without strict limits, well-behaved clients reduce latency and stay well clear of any abuse thresholds.

  • Batch token requests. Both /prices and /liquidity accept comma-separated addresses. Fetch all the tokens you need in a single call instead of one request per token.
  • Cache prices for short windows. Token prices are stable over a few seconds. A 5–15 second client-side cache is safe for most UIs and cuts unnecessary request volume.
  • Refresh quotes on user activity, not on idle polling. Fetch a new route when the user changes inputs or is about to submit. There is no need to keep refreshing when the user is inactive.

Errors

Error responses use plain-text bodies, not JSON. Check the HTTP status code first, then read the response body.

Architecture

Every Nordstern swap flows through a two-contract pipeline — a Guard Contract for security and an interchangeable Executor Contract for routing.

On this page

Best practices