Private link
Your bot's server sits in the same datacenter as ours, and a direct link inside the building connects the two. Requests and streams go from your machine to the API over that link only. They never cross the public internet.
Why it matters
Every request a bot makes, and every event it waits for, pays the trip between its server and the API twice: out and back. On the public internet that trip runs through other people's networks, and its length changes from one moment to the next. On a private link it is a few metres of cable.
- Streams reach you first. A trade on the Advanced Data Stream or the Ultra Fast Shred Stream is on your machine the moment we publish it, not after a trip across the internet.
- Trades start sooner. A Lightspeed request reaches the race while the slot is still young, which is what the block 0 lane needs.
- The same timing every time. No route changes, no busy hours, no shared queue at the front door. A bot tuned on Monday behaves the same on Friday.
What goes over it
Everything. The Local Trade API, Lightspeed, every WebSocket stream and Ultra Fast Shred Stream all answer on the private address. Your plan's key works the same on it as on the public one, and the public address keeps working as a fallback.
Getting one
- Get the Developer plan.
- Ask in the private Telegram group. Tell us the region: Frankfurt, Amsterdam or New York.
- We tell you which datacenter our servers are in. You rent a server or a rack there.
- The datacenter runs the link between your rack and ours. We hand you the private address.
Put your bot in the same city as the region you use. That alone takes the trip to about a millisecond; the private link is the step after.