Antigravity setup
Use 9router to make Antigravity routing more predictable
Antigravity-style IDE traffic is valuable when it stays reliable. 9router can help by translating formats, tracking provider availability, and moving traffic through a planned fallback stack.
For Antigravity users who need practical routing and operational guardrails before paying for a rollout.
What to decide first
Before connecting an IDE, decide which provider should be primary, what counts as an acceptable fallback, and whether the team wants strict logs or token-saving compression.
Do not expose a router endpoint broadly until API keys, TLS, dashboard auth, and log retention are clear.
- Primary route for best coding quality.
- Cheap backup for rate-limit or quota events.
- Free lane for continuity when the task is low risk.
- RTK saver for tool-heavy prompts.
Antigravity-specific caution
IDE routing can involve extra integration details. Keep the first setup small, verify one model route, and only then add more providers or shared team access.
If the route fails, the team should know whether it is an IDE setting, 9router endpoint, provider auth, quota limit, or model translation issue.
Why Pro is the default
A single-user Antigravity test can start small. A team rollout needs provider policy, installation notes, and checkout-supported onboarding, which is why Pro annual is selected by default.
Common questions
Is Antigravity support the same as Codex support?
No. The operational goal is similar, but IDE traffic can have different setup details. Verify the current 9router upstream docs before relying on it.
Should I use a cloud endpoint for Antigravity?
Only if you can secure it. Local or private network routing is easier to control for the first rollout.
What should I test before checkout?
Confirm that one Antigravity route reaches 9router, uses the intended model stack, and fails over in a way the team understands.