> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dexpaprika.com/llms.txt
> Use this file to discover all available pages before exploring further.
# The console: keys, usage and billing
> Where to get an API key, rotate it, watch what you have spent, connect an AI client and find your invoices.
Everything account-shaped lives in one place: [console.dexpaprika.com](https://console.dexpaprika.com). Your key, what you have spent this period, the errors your calls returned, the MCP setup for AI clients, and billing.
You do not need it to start. The API answers keyless requests, and a key is what raises the allowance and unlocks any-token streaming. See [pricing](https://dexpaprika.com/api/pricing) for what each tier includes.
## What each section is for
| Section | What you do there |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Dashboard** | The one-screen answer to "am I fine?". Current plan, credits spent against the cap, whether autoscaling is on, and when the next billing cycle starts |
| **Usage** | The same numbers with history: which endpoints you call, how the spend moved day to day |
| **Error Log** | What your failed calls actually returned. Start here before assuming the API is down |
| **API Keys** | Reveal, copy, revoke. One active key per account |
| **MCP & AI Setup** | Ready-made configuration for Claude, Cursor, Cline and anything else that speaks MCP |
| **Billing** | Plan and billing period, the autoscaling switch, credit packs, and invoices with an export |
| **Notifications** | Where quota and billing alerts are delivered |
## Frequently asked
**API Keys** in the sidebar. A key is generated for your account, and there is exactly one active key at a time.
The same screen shows the base URLs your key is valid for. Free keys authenticate against `https://api.dexpaprika.com` and `https://streaming.dexpaprika.com`. Pro moves you to `https://api-pro.dexpaprika.com` and `https://streaming-pro.dexpaprika.com`.
That pairing matters: a key sent to the wrong host answers `403 wrong_host` rather than falling back, and the body tells you which host to use.
Revoke the current one, then generate a new one. Both buttons are on the **API Keys** screen.
Because there is one active key per account, rotation is a break: the old key stops working the moment you revoke it. Have the new key ready to deploy before you press it, and if the key lives in a hosted environment, remember it is usually stored as a secret rather than in the code.
Put the key in the `Authorization` header, on its own:
```bash theme={null}
curl "https://api.dexpaprika.com/networks/ethereum/pools/search" \
-H "Authorization: api_YOUR_KEY_HERE"
```
There is no `Bearer` prefix. `Authorization: Bearer api_...` is rejected with `401`, which is easy to trip over because almost every other API expects the opposite.
**Billing**, at the bottom of the page, with an export control for pulling them out. Until your first payment the section says so rather than sitting empty, so an empty list is not a sign that something failed.
The same screen carries the rest of the money: your current plan with the period it runs for, the autoscaling switch, and the credit packs.
The dashboard shows the next billing cycle at a glance. If it reads no active subscription, you are on a free tier and there is nothing to invoice.
Both are ways to keep going past your monthly allowance on Pro. They differ in when you decide.
**Autoscaling** is a switch. Leave it off and the allowance is a hard stop, exactly like a free tier. Turn it on and once the plan is spent, extra credits are bought automatically at \$20 per million, up to a spending limit you set on the same screen. You decide the ceiling once and then stop thinking about it.
**Credit packs** are bought up front, and they cost less per credit than autoscaling does: 5M for $79, 15M for $199, 50M for \$499. The larger the pack the wider the gap, from roughly a fifth cheaper to about half.
They combine. A pack sized to what you expect, with autoscaling behind it for the month that surprises you, means you pay the lower rate for the bulk of it and never hit a wall.
Both are Pro features. On a free tier the controls are visible but inactive.
The dashboard card **Usage this period** is the short answer: credits used against your monthly cap, with the percentage. **Usage** breaks it down over time and by endpoint, so you can see which call is doing the spending.
One request costs one credit. Batch endpoints charge one credit per item, and each delivered streaming update costs one credit too. See [plan your credit usage](/knowledge-base/credit-usage) for how to size a workload before you build it.
On a free tier the cap is hard: the API answers `402` and the body names the next step for your tier. Nothing is charged, and the allowance refills when the period rolls over. The `resets_at` field in the body tells you when.
On Pro you can let it keep going. The dashboard calls this **autoscaling**: with it off the cap behaves like the free tier, with it on the overage is charged per additional block up to the monthly spend limit you set. See [error handling](/knowledge-base/error-handling) for the difference between a `402` and a `429`, which is worth getting right in code: a `429` is a per-minute rate limit and is worth retrying, a `402` is the monthly allowance and retrying will not help.
**MCP & AI Setup** generates the configuration with your key already filled in, for Claude Code, Claude Desktop and any client that takes a JSON config.
The hosted server speaks two transports. Streamable HTTP, which is what current clients use:
```
https://mcp.dexpaprika.com/streamable-http
```
and SSE, for older clients:
```
https://mcp.dexpaprika.com/sse
```
Authentication is the same `Authorization` header as REST. Full setup per client is in [the hosted MCP guide](/ai-integration/hosted-mcp-server).
No. Keyless requests work at 200,000 credits a month per IP, with no signup and no card. Registering a free key raises that to 500,000 and lifts the streaming restriction from the [showcase list](/streaming/showcase-streams) to any token we index.