Developer early access: request access, get keys when onboarding opens

ChefSphere developer early access is open for requests: share what you are building, we review, and we email when onboarding opens for keys and prepaid packs. Teams get contacted when access is ready for their use case across marketplace, live, AI, social, billing, and more.

This page explains the request path and what happens next—not pack SKUs in depth, not X-API-Key hygiene, and not module burn weights. Those intents live in prepaid-api-tokens, api-keys-guide, and multi-module-token-billing. Use this guide when your question is simply how to get in and what to expect before keys exist.

Name your product, stack, launch markets, and which modules you need first—catalog, planning, marketplace, live, AI, social, or billing—so review is not guesswork. Add rough volume bands if you have them; honesty beats fake precision that collapses in the first onboarding call. Optional company and product URL fields help us prioritize real builders over empty curiosity forms.

After you submit, expect a confirmation that we received the request and will email when early access opens for your use case. Timing depends on rollout and fit; we email you when onboarding is ready for your use case. When access opens, packs start at $29 for 200,000 tokens on one balance, and keys use Firebase-style X-API-Key billing per call.

Illustrative OpenAPI samples are available now for planning shapes across product surfaces while you wait. Treat them as samples—not production contracts—until onboarding provides environments and keys. Enterprise from $300 per month can be discussed for dedicated limits once volume and modules are clear, and keep that dependency map explicit in your early-access request so onboarding stays accurate.

It is not a public token checkout that drops live keys into an inbox without review of your product and module needs. It is not a guarantee that every regional payment rail or KYC path is live on day one of your pilot. It is not a substitute for reading module guides so you request the right surfaces instead of “all nineteen immediately.”

If you need decision support, read build-versus-buy and food-app backend composition before submitting a vague request. If you need pricing mechanics, read prepaid tokens and multi-module billing so finance arrives prepared. If you need auth practice, read the API keys guide so secrets handling is ready when keys land, and keep that dependency map explicit in your early-access request so onboarding stays accurate.

While you wait, refine your MVP module map and threat model for where keys will live—preferably server-side—when onboarding arrives. Keep talking to users; early access is infrastructure timing, not an excuse to pause product discovery. When we email, move quickly: buy a pack, authenticate with X-API-Key, and validate the thinnest slice first.

Related guides on prepaid tokens, API keys, and multi-module billing prepare you for day one after access without relearning the platform narrative. Ready to join the queue? Request early access from the developers hub with a concrete module list. We will contact you when onboarding opens.