Total requests
0All timeWorkspace access
Welcome back
Sign in to continue to your developer workspace.
Or continue with
Loading your workspace...
Workspace access
Sign in to continue to your developer workspace.
THINK · CREATE · EXPLORE
A focused space for your ideas, code, and everyday work.
No API key needed. Usage is charged to your account.
Current workspace
Live request, token, and spend activity.
Requests and tokens by day
OpenAI-compatible base URL
http://localhost:4173/v1Latest gateway activity
| Time | Request | Endpoint | Model | Tokens | Cost | Status |
|---|
Workspace
Explore models, compare suppliers, and view details without leaving your workspace.
Workspace
Discover the latest PicoX activities.
Credentials
Create, reset, and delete keys used by SDKs and services.
PicoX stores a one-way SHA-256 hash and a short prefix of your API key, not the full key. This lets us verify requests without retaining a recoverable secret. Even an administrator cannot retrieve the original key from these records, reducing the risk of keys being exposed through database access.
Use Reset to generate a new key. The old key will stop working immediately, so update it in your apps and services. Copy the new key before closing the dialog and save it in a password manager or secrets manager. Avoid putting keys in screenshots, chats, or source code.
In October 2026, OpenCode disclosed a Console security incident affecting some users with linked external providers. Its notice warned that stored provider API keys may have been exposed. This is a reminder to limit readable copies of keys and protect the credentials saved in your clients as well.
Keys authenticate requests to the PicoX gateway.
| Name | Key prefix | Available budget | Provider discount | Request limit | Access scope | Expires | Last used | Status | Actions |
|---|
Your provider credentials
Use your own provider API keys through PicoX.
Your provider keys are encrypted and are never returned after saving.
| Name | Provider | Status | Actions |
|---|
SDK requests use a PicoX API key and the X-Pico-BYOK header. In the AI workspace, sign in and select a saved connection.
X-Pico-BYOK: byok_...Requests are sent to the provider with the requested public model ID.
Observability
Explore request volume, tokens, cost, performance, and reliability.
Selected time range
Throughput and average response time
Last 60 seconds
—Refreshes every 10 seconds. Uses recorded requests and current filters, excluding dates and requests still in progress.
0 matching requests
| Created | Request ID | API key | Endpoint | Model | Supplier | Status | Input | Output | Latency | Output speed (TPS) | Cost |
|---|
Credits
Prepaid balance and immutable credit ledger.
Gift credit pays for model requests. The earliest expiration is used first; expired or revoked credit cannot be spent. Subscription purchases use the permanent balance.
| Gift amount | Unused amount | Expires at | Status | Reason |
|---|
Recharges and wallet funding activity
| Description | Type | Amount | Created |
|---|
Plans
Your active subscription and available plans.
Current plan, quota usage, and renewal window.
Purchase a plan with your wallet balance.
Pricing
Supplier and account offers do not stack. The best available price applies.
Prices are shown per million tokens. Cache read and write prices are included when configured.
| Model | Provider | Discount | Source | Input | Cache read | Cache write | Output | Tool call |
|---|
Account
Manage identity, data controls, routing preferences, and request defaults.
Administration
Customers, infrastructure health, and gateway activity.
Customers, infrastructure health, and usage across the gateway.
Input and output tokens over the last 14 days
Daily request volume and average response time
Last 7 days
| Model | Requests | Success | Tokens | Spend |
|---|
Last 7 days
| Provider | Requests | Success | Tokens | Spend |
|---|
Provision, search, and manage customer accounts, access, and balances.
| ID | User | Group | Role | Status | Balance | Created | Last login | Registration IP | Last login IP |
|---|
All successful wallet credit events across customer accounts.
| Ledger ID | Customer | Source | Recharge method | Amount | Balance after | Description | Created |
|---|
Create recurring quota plans and manage customer subscription lifecycles.
| ID | Plan | Price | Billing type | Quota limits | Models | Validity | Priority | Subscriptions | Assignment limit | Wallet overflow | Status |
|---|
Provision, inspect, and control credentials across every customer workspace.
| Key | Customer | Available | Budget / spent | Provider discount | Request limit | Models | Network | Expires | Last used | Created | Status |
|---|
Issue prepaid credit codes and track their complete lifecycle.
| ID | Name | Code prefix | Value | Status | Expires | Redeemed by | Created |
|---|
Manage shared limits and pricing policies for customer tiers.
| Group | Default policy | Model overrides | Customers | Updated | Actions |
|---|
Effective customer-level pricing overrides by model and provider.
| Customer | Model | Provider | Multiplier | Effective discount | Updated | Actions |
|---|
Manage supplier identity, model ownership, billing, access, and tags.
| ID | Name | Logo | Tags | Access | Discount | Total billed | Routes | 24h activity | Enabled | Actions |
|---|
Manage physical upstream connections and bind each channel to one or more suppliers.
Total billed counts customer charges for successful requests through each channel, including resource-pack deductions.
| Channel | Connection | Suppliers | Routing policy | Total billed | Credentials | Status | Updated | Actions |
|---|
Create public models and bind them to provider routes.
| Model | Logo | Vendor | Description | Tags | Channel tiers | Capabilities | Context window | Pricing | Created | Updated | Status | Actions |
|---|
Platform-wide inference traffic, billing, latency, and routing outcomes.
Last 60 seconds
—Refreshes every 10 seconds. Uses recorded requests and current filters, excluding dates and requests still in progress.
Averages use all matching requests over the full selected time range. RPM = requests / minutes; TPM = input and output tokens / minutes.
| Created | Customer | Request | API key | Supplier | Channel | Endpoint / model | HTTP status | Tokens | Latency | Output speed (TPS) | Cost | Actions |
|---|
Failures grouped by error code, channel, and public model.
Last 7 days, UTC
Most frequent failures in the selected period
| Error code | Failures | Last seen |
|---|
Failure rate across routed provider traffic
| Channel | Failures | Rate | Last seen |
|---|
Failure rate across public model traffic
| Model | Failures | Rate | Last seen |
|---|
Latency percentiles and throughput by endpoint, channel, and model.
Last 7 days, UTC
Highest-volume request paths in the selected period.
| Endpoint | Requests | Average | P95 |
|---|
Latency by routed provider channel.
| Channel | Requests | Average | P95 |
|---|
Latency by public model ID.
| Model | Requests | Average | P95 |
|---|
Configure daily Token packs or wallet rewards.
Keep Skills and MCP tools up to date from GitHub, public URLs, or the official MCP Registry.
Control customer onboarding and platform-wide outbound routing.
Live service, runtime, and database pool diagnostics.
Current server process information.
Live PostgreSQL pool counters.
Active non-secret service limits.
Maintenance work coordinated across running server instances.
Tasks waiting for an executor or currently running.
| Type | Status | Progress | Executor | Updated | Detail |
|---|
Recently completed and failed maintenance tasks.
| Type | Status | Progress | Executor | Updated | Detail |
|---|
Administrative changes and security-relevant operations.
| Created | Actor | Action | Resource | Metadata | Event ID | Actions |
|---|