API keys and usage
Issuing, showing, stopping and deleting API keys in the console, spending limits, reading usage and the call history, and balance and top-ups.
The console (https://token.echohub.io/console ) is where you manage API keys and usage. You log in with your Echo AI Hub account.
The console is available in Japanese only. On this page, labels in the console are written in Japanese, followed by an English translation in parentheses.
| Menu | What you can do |
|---|---|
| 「はじめに」 (Getting started) | Check three things in order: balance, API key and first call. Shown until your first call succeeds |
| 「利用状況」 (Usage) | See the amount spent, number of requests and tokens for a period, and usage by day, by model and by key |
| 「呼び出し履歴」 (Call history) | See a record of each call. You can filter it and export it as CSV |
| 「APIキー」 (API keys) | Issue and show keys, change their name and spending limit, stop and resume them, delete them |
| 「残高とチャージ」 (Balance and top-up) | See your balance, its breakdown and top-up history, and top up |
| 「モデルと料金」 (Models and pricing) | Open the model list |
| 「ドキュメント」 (Docs) | Open this documentation |
Right after you sign up, the console shows 「API の利用を準備しています」 (Preparing API access). When it is ready, the screen switches automatically. If it takes a while, reopen the page after a few minutes.
Issue an API key
- Open 「APIキー」 in the menu and click 「キーを発行」 (Issue key)
- In 「名前」 (Name), enter a name that shows what the key is for (for example, production server). Up to 16 full-width or 50 half-width characters. You cannot create two keys with the same name
- To limit how much this key can spend, enter an amount in 「利用上限（円）」 (Spending limit (JPY)). If you leave it empty, the key can be used up to your account balance
- Click 「発行する」 (Issue) and the key is shown. Click 「キーをコピー」 (Copy key) and store it somewhere safe
- A key is a string that starts with
sk- - After issuing, you can show the key again from its menu in the list with 「キーを表示」 (Show key), up to 10 times per hour
- One account can issue up to 1,000 keys (provisional). You can issue up to 20 keys per hour
If you use separate keys for each purpose (production server, local development, each tool and so on), you can stop just that key when something goes wrong.
Note: Do not show your key to anyone. Do not put it in a public repository or in code that runs in the browser.
The key list
The list in 「APIキー」 shows the following for each key.
| Item | Contents |
|---|---|
| 「名前」 (Name) | The key's name. The first and last 4 characters of the key are shown below it |
| 「状態」 (Status) | 「有効」 (Active), 「停止中」 (Stopped), 「有効期限切れ」 (Expired), 「上限に達した」 (Limit reached) |
| 「利用上限」 (Spending limit) | The remaining limit. Keys without a limit show 「上限なし」 (No limit) |
| 「このキーの利用額」 (Spent with this key) | The total amount spent with this key |
| 「最終利用」 (Last used) | When the key was last used. Keys not used yet show 「未使用」 (Unused) |
| 「作成日時」 (Created) | When the key was created |
Key actions
The menu at the right end of each row in the list has the following actions.
| Action | Result |
|---|---|
| 「キーを表示」 (Show key) | Shows the whole key |
| 「名前を変更」 (Rename) | Changes the key's name. Past records keep showing the old name |
| 「利用上限を変更」 (Change spending limit) | Changes how much this key can spend from now on. Leave it empty for no limit |
| 「停止」 (Stop) | Stops calls with this key. You can undo it with 「再開」 (Resume) |
| 「削除」 (Delete) | Deletes the key. This cannot be undone. To confirm, you type the key's name |
Calls with a stopped or deleted key return HTTP 401. After you delete a key, its past usage records stay in the call history.
If a key leaks, stop or delete it right away and issue a new key.
Spending limits
The 「利用上限」 you enter when issuing a key, or with 「利用上限を変更」, is the maximum amount the key can spend. It goes down as you use it and is never reset automatically.
When a key reaches its limit, its status changes to 「上限に達した」 (Limit reached) and a 「利用上限を変更」 button appears in its row. If you raise the limit, the key resumes automatically. You do not need to replace the key in your program.
The errors returned when a key is close to or at its limit are in Limits and rate limits.
Check your usage
In 「利用状況」 (Usage) in the menu, choose a period to see the following. Times are Japan time.
| Item | Contents |
|---|---|
| 「期間の合計」 (Period total) | Amount spent, number of requests, number of tokens |
| 「日別の利用額」 (Spending by day) | A chart of the amount spent each day |
| 「モデル別」 (By model) | Requests and amount spent for each model |
| 「キー別」 (By key) | Requests and amount spent for each key name |
The totals, daily figures and per-model figures are aggregated every hour. The latest calls can take up to 5 minutes to appear.
Check the call history
「呼び出し履歴」 (Call history) in the menu shows a record of each call, newest first. The text of requests and model answers is not shown. What we record is described in Data handling.
| Item | Contents |
|---|---|
| List | Time, result (success or failure), key, model, amount, request ID |
| Details | What failed and what to do, HTTP status, input tokens, output tokens, duration, whether it was streamed |
| 「絞り込み」 (Filter) | Period, result, key, model ID, request ID |
| 「CSV を書き出す」 (Export CSV) | Exports one month of records as CSV. The request text is not included |
Records can take a few seconds to appear.
Video generation tasks
Each video generation task (Video generation) is shown as one row.
| Item | Contents |
|---|---|
| State | One of 「待機中」 (Waiting), 「生成中」 (Generating), 「完了」 (Completed) and 「失敗・返金済み」 (Failed, refunded). While generating, the time since you submitted the task is shown too (for example 生成中 · 1 分 20 秒, 1 minute 20 seconds) |
| Amount | Until generation finishes, the estimated amount deducted at submission. After that, the recalculated amount. Failed tasks have been refunded in full |
| 「開く」 (Open) | In the row of a completed task. Opens the generated video |
| 「期限切れ」 (Expired) | Shown in the row of a task whose file the provider no longer keeps. The video can no longer be opened |
Balance and top-ups
In 「残高とチャージ」 (Balance and top-up) in the menu, you can see your current balance, how much of it is bonus credit, and the nearest expiry date.
| Item | Contents |
|---|---|
| 「内訳」 (Breakdown) | For top-ups and bonus credit: date granted, amount granted, amount left and expiry date. The balance with the nearest expiry is used first |
| 「チャージ履歴」 (Top-up history) | Date, amount (tax included), receipt |
The breakdown and the top-up history are shown after the member site Echo AI Hub opens.
To top up:
- Click 「チャージする」 (Top up) in 「残高とチャージ」. When your balance is low or zero, you can also use 「チャージする」 in the line at the top of each page
- Choose an amount and click 「お支払いへ進む」 (Continue to payment). The same screen shows your balance after each top-up amount, what to check before you pay (the amount added to your balance, when it is added, expiry, refunds) and links to 「利用規約」 (Terms of Use) and 「特定商取引法に基づく表記」 (Specified Commercial Transactions Act notice)
- You are taken to the Stripe payment page. Pay by credit card. Stripe emails you the receipt
- When the payment is done, you return to the page where you clicked 「チャージする」. It can take a few seconds to about a minute before the balance is updated. The screen refreshes automatically when it is
Top-up amounts, expiry, invoices and receipts are in Pricing and top-ups.
Sources
| What | Source | Checked |
|---|---|---|
| Menus, the key issuing screen and list columns, key actions, changing the spending limit and resuming, the items in usage, call history and balance, the screen right after sign-up | The Echo Token Station console (screens as of 2026-09-28) | 2026-09-28 |
| How video generation tasks are shown in the call history (state, elapsed time, amount, 「開く」, 「期限切れ」) | The Echo Token Station console specification (as of 2026-10-02) | 2026-10-02 |
| Top-up steps (the screen for choosing an amount, moving to the Stripe payment page, the page you return to), the top-up history columns | Measured in Echo's test environment, with test servers in place of the member site Echo AI Hub and Stripe | 2026-10-01 |
| Stopped, expired and deleted keys, and keys that have used up their limit, return 401 | Measured in Echo's test environment, with the same relay settings as production and a server that returns test responses in place of the upstream API | 2026-09-28 |
| How many keys one account can issue | Echo relay server settings (as of 2026-09-28) | 2026-09-28 |