After delivery setup
Once your key is delivered, choose one integration path and test it before moving into production. Use /v1 for OpenAI-compatible tools and /anthropic only for Anthropic-native tools such as Claude Code.
| What to install | Official source | Quick check |
|---|---|---|
| CorvusLLM key | Buy or top up balance | Keep the key ready before pasting examples. |
| Terminal with curl | Built into macOS/Linux; Windows 10/11 include curl.exe. | curl --version |
| Optional Git | Git install guide | git --version |
curl --version
git --version Where the key appears
- On the order confirmation page after the payment reaches
paid_confirmed. - In the delivery email.
- Inside the personal dashboard after the customer logs in.
How customers can log in
All login paths land on the same personal dashboard data.
| Login method | When to use it |
|---|---|
| API key login | Best for direct ownership of one delivered key and quick access to balance, usage, and top-ups. |
| Google or GitHub | Best for users who prefer account-based sign-in and want to keep returning without pasting the key. |
| Email link | Best when the user wants sign-in without OAuth and without keeping the key open on screen. |
What the personal dashboard shows
- Current balance on the selected key
- Total spent amount
- Request count
- Recent requests
- Model breakdown
- The active base URL and key record
How top-ups behave
Top-ups do not create a second key for the same customer flow. They credit the same key again so the dashboard stays coherent.
The same key keeps its identity, usage history, and dashboard line. The balance simply increases again after the top-up confirms.
What to do if something looks missing
- If the key works in the API but the dashboard looks empty, log in with the delivered key first.
- If the key is not in the email yet, check the on-site confirmation page and the order status first.
- If balance looks too low, read Billing, Balance & Cache before assuming there is a dashboard bug.