CostImplodeAI works best when AIMLAPI, CometAPI, and Native1AI are all connected. That gives the arbitrage engine two external lanes plus one fallback lane so routing can stay healthy, compare pricing, and self-heal.
Free for 3 Months works best after all 3 keys are linked.
Open an AIMLAPI account, generate a key, and keep it ready for the primary arbitrage lane. This lane gives CostImplodeAI broad low-cost model access.
Open a CometAPI account, generate a key, and connect it as the second external lane. This gives the routing layer overlap, fallback, and sharper model comparisons.
Request Native1AI access for the third lane. This is the clean fallback path for Cloudflare-hosted models and the extra key the gateway uses to stay resilient.
Create the AIMLAPI account first and save the key in your password manager or internal setup doc.
Create the CometAPI account second and load the first $10 so real routed tests can actually use the second external lane.
Use the CostImplodeAI onboarding flow to request Native1AI so the third lane can be staged for fallback.
Open CostImplodeAI onboarding or dashboard and submit what you have. Missing keys should be called out immediately.
Two keys lets the gateway compare providers. The third key lets it recover more gracefully when one lane is unavailable or no longer the best priced option.
Yes, but the site should keep telling users that all 3 keys gives the best routing, best fallback behavior, and strongest savings profile.
Use the onboarding form on the homepage for now. The dashboard should also expose a dedicated key management surface once Firebase auth is restored.
After AIMLAPI is active and CometAPI has its first funded balance, sign up through CostImplodeAI, submit the keys through the site, and run a small prompt batch through the live gateway. Review lane choice, savings percentage, and latency before pushing any serious traffic.