Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nexroute.io/llms.txt

Use this file to discover all available pages before exploring further.

Capture does not enforce request rate limits at the partner endpoint. The service is designed to absorb partner traffic at production rates without throttling.

​
Behavior under burst

  • Each submission is processed concurrently. There is no fixed worker pool to saturate
  • If internal capacity is momentarily strained, transactions take a fast-forward path that delivers them through nexroute’s private partnerships without backrun analysis. The delivery guarantee is preserved
  • No partner request is rejected for rate-limit reasons

​
What this means for integration

  • You don’t need client-side throttling against the Capture endpoint
  • Sustained extreme bursts may reduce backrun yield on the affected window (capacity goes to delivery first), but every acknowledged transaction still lands
  • Connection reuse (HTTP keep-alive or persistent WebSocket) is recommended for high-throughput callers to amortize TLS handshakes

​
Anticipated heavy patterns

If you expect sustained traffic that could strain capacity (large-scale TWAP, market-making bursts, scheduled order release), let nexroute know during onboarding so capacity can be pre-provisioned for your endpoint.