Your Console, Screen by Screen¶
Every page in Pay Digital LLM Platform, what it is for, and what each control does.
This is the tour. Three pages go deeper on the things you will use daily: API Keys, Balance & Billing and Usage & Analytics.
The sidebar¶
| Section | What it is for |
|---|---|
| Playground | try a model without writing any code |
| Chat | a full chat interface, already signed in as you |
| Overview | is everything working, and how much is left |
| Dashboard | how much you have used, over time and per model |
| API Keys | the credentials your application authenticates with |
| Usage Logs | every request, what it cost and why |
| Task Logs | the same, for jobs that finish later — images, video |
| Wallet | your balance, top-ups and transfers |
| Profile | your account, password, two-factor, sign-in methods |
Some accounts see more than this. If a section is missing from your sidebar, it is not available to your account rather than broken.
Overview¶
The first page after signing in. It answers two questions: is anything wrong and what do I do first.
Cards along the top
- Credit remaining — what is left on your balance. It turns red when your recent rate of spending would exhaust it within a day.
- Last 24h usage — what you spent in the past twenty-four hours.
- Average latency — how long a model has been taking to answer.
The setup guide walks a new account through creating a key, choosing a model and making a first request. Copy ready-to-run curl gives you a command with your address and a model already filled in — paste it into a terminal as is. Once you have made a request the guide can be hidden.
Below that, whatever Pay Digital LLM Platform has published: announcements, frequently asked questions, API addresses, and service status.
Playground and Chat¶
Playground sends a single request and shows the raw response, the tokens used and the cost. It is the fastest way to check that a model does what you expect before wiring it into anything.
Chat is a conversation interface using your own account and key — useful for testing prompts over several turns.
Both spend from your balance at the same prices as the API. Nothing here is free because it is in the browser.
Dashboard¶
Charts and totals for your own traffic.
Five cards:
| Card | What it means |
|---|---|
| Total count | requests in the selected period |
| Total quota | what those requests cost |
| Total tokens | prompt tokens plus completion tokens |
| Average RPM | requests per minute |
| Average TPM | tokens per minute |
The last two are averages across the whole period, not peaks. Select a month and a busy afternoon disappears into the average. To find a spike, narrow the period.
Below the cards: consumption split by model, and a response-time chart.
Deeper detail is in Usage & Analytics.
API Keys¶
The credentials your code uses. Full details in API Keys; the short version:
- Create API Key — name it, optionally set an expiry, a spending cap and which models it may reach.
- Copy API key — the full key is shown once, at creation. After that only its prefix. Lost it, create another; there is no way to reveal it again.
- Copy connection info — address and key together, ready to paste into a client.
- Delete — takes effect immediately, including for requests in flight.
Every key draws on the same balance. A spending cap on a key limits that key, not your account.
Usage Logs¶
One line per request: when, which model, how many tokens, what it cost, how long it took. Expand a line to see how the charge was calculated.
Task Logs is the same for work that does not finish inside the request — image and video generation. A task appears there while it is still running.
Wallet¶
- Add funds — pay through the available payment method, or redeem a top-up code.
- Transfer — send part of your balance to another account.
- Invites — your referral link and any rewards earned, which can be moved to your main balance.
How spending works. Charges are taken as requests complete, computed from the tokens actually used — which is only known once the model has answered. When your balance cannot cover a request, that request is refused. Your balance does not go negative and there is no bill afterwards.
More in Balance & Billing.
Profile¶
- Email, username, display name.
- Password — change it, or set one if you signed up through a social account.
- Two-factor authentication — a code from an authenticator app, with backup codes. Worth enabling: your account holds a balance and working API keys.
- Passkey — sign in with your device instead of a password.
- Linked accounts — connect or disconnect the sign-in methods Pay Digital LLM Platform offers.
A code is emailed to you when you register and when you reset a password. Signing in does not use email codes — the second factor at sign-in is the authenticator app above, if you have enabled it.
Questions people ask twice¶
Where is my API key? I only see the first characters. Shown once, at creation, and never again. Create a new one and delete the old.
Why does the cost of the same prompt differ between runs? You are billed for tokens actually used, and a model does not produce an identical-length answer every time.
My balance did not drop immediately after a request. The charge is applied when the request completes. For streaming responses that is after the last chunk.
A request was refused and I have money. Check the key as well as the balance: a key can carry its own spending cap, an expiry date, or a restricted list of models.
Can I go negative and settle later? No. Requests are refused instead — there is no credit and no invoice.
Getting help¶
Support contacts, terms and privacy are linked at the bottom of every page on https://llm.paydigital.shop.