Beta onboarding
Get from signup to your first grounded answer.
Genesis Access is the external beta period. You sign up, verify your email, reveal a Genesis API Key, test Anzoth-Core or Anzoth-Coder, upload a document, and watch usage and logs in the dashboard.
Genesis Access
Account-approved onboarding during the beta period.
Your key
Reveal the masked Genesis API Key once, then copy it.
Models
Choose Anzoth-Core or Anzoth-Coder in Playground and API calls.
Private data
Knowledge Bases stay scoped to your account and customer.
What to expect
The beta flow is intentionally simple: sign up, verify, reveal, test, upload, and review usage. No self-serve paid plan is required to get started.
Checklist
First-user launch flow.
Follow these steps in order for the cleanest beta experience and the quickest path to a useful first request.
Step 1
Sign up
Create your account with an email, organization name, and use case. The dashboard appears as soon as signup is complete.
Step 2
Verify email
Confirm the inbox link so your Genesis API Key and account-scoped model access are fully enabled.
Step 3
Reveal your Genesis API Key
Open API Keys, reveal the masked key once, and copy it into your client or test environment.
Step 4
Try Playground
Pick Anzoth-Core or Anzoth-Coder and send a short message to see the dashboard chat flow work end to end.
Step 5
Upload and query Knowledge Bases
Add one document, wait for ingest, and ask a grounded question with citations from your own content.
Step 6
Monitor usage and logs
Review account totals, per-key usage, and recent requests before you expand to more users or workloads.
What not to upload yet
Keep the first test simple.
Early beta testing works best with harmless, well-understood documents. Keep anything sensitive out of the first round until your own policy and review process are in place.
Do not upload secrets, raw API keys, credentials, or private tokens.
Do not upload regulated data unless your own policy allows it for beta testing.
Use the dashboard to confirm what your account can see before sharing broader access.
If your data is sensitive, start with a harmless sample document and a single test question.
Support and next steps
Where to go when you get stuck.
Use the docs for how-to guidance, the dashboard for your account-scoped data, and the support page for onboarding questions or bug reports.
Need help
Open dashboard support after signing in.
Need details
Check docs/errors for user-fixable vs temporary issues.
Need API help
Use the API Quickstart for curl examples and response shapes.
Need KB help
Read the Knowledge Bases guide before uploading or querying.
Resources
The main places beta users spend time.
These are the surfaces most users will touch on day one. The links below keep the onboarding flow short and familiar.
API Quickstart
Make your first request with curl or an SDK.
Use the base URL, Authorization header, and the supported request fields for chat completions.
Start here
Knowledge Bases
Ground answers in your own documents.
Create a collection, upload a file, wait for ingest, then ask a question with citations.
Private context
Usage
Watch request and token totals by account and key.
Check scoped totals, per-key breakdowns, and recent activity without ever seeing raw key values.
Dashboard view
Logs
Review recent request rows and status details.
Use the logs page to confirm model, route, status, latency, and token counts.
Request history
Settings
Set safe defaults for the dashboard and Playground.
Choose the default model, max tokens, streaming preference, and landing page for your account.
Account preferences
Support
Get help without exposing secrets or internal details.
Use the support page for onboarding, troubleshooting, and issue reporting once you are signed in.
Help path
Next
Start the beta flow when you are ready.
Sign up, verify, reveal, test, and keep the first round small so you can confirm the launch path before widening access.