VoidAI is a good router: one OpenAI-compatible endpoint in front of Claude Opus 5.5, Fable 5.1 and Sonnet 5.5. Point your client at https://api.voidai.dynv6.net/v1, keep your own key, and stream like normal. Workers at the edge, GCore in front, dynamic DNS behind a stable name.
A few of the routes on the shared key. Limits are monthly dollar allowances with 5-hour, weekly and monthly windows. This table is static for now — live numbers come later from the usage probe.
| Model | Via | In / 1M | Out / 1M | Monthly allow. |
|---|---|---|---|---|
| claude-opus-5-5 | anthropic · messages | $4.00 | $20.00 | $120 |
| claude-fable-5-1 | anthropic · messages | $10.00 | $50.00 | $60 |
| claude-sonnet-5-5 | anthropic · messages | $2.00 | $10.00 | $80 |
Your client only ever sees the dynv6 name. Behind it, GCore absorbs the edge and the Worker does auth, per-user limits and the upstream call. Streaming responses pass through — the Worker never waits on tokens, so idle time costs nothing.
Checks your VoidAI key, enforces your personal limit, forwards with the house key. →
Static gets cached at the edge. /v1/* bypasses cache; heavy pulls slow to 64 KB/s after 512 KB. →
One hostname for a moving setup. Point, forget, rotate origins without telling clients.