Total requests
—In the selected windowService adminService-wide visibility across all clients. This view is read-only.
Admin accessYOUR WORKSPACE AT A GLANCE
Overview
Every request, from queue to completion.
Solve success
—Completed / completed + failedAverage duration
—End-to-end successful requestsIn progress
—Queued and runningRequest volume
Requests received over time
RequestsCompleted
Worker status
Hibernates when the forest is quiet
CheckingReading controller state
Request and result data stay available while the worker sleeps.
- Concurrent solves
- —
- Outstanding request limit
- —
- Result availability
- —
- History retention
- —
- Service queued
- —
- Service running
- —
- Local active requests
- —
- Controller readiness
- —
Viewing this dashboard never wakes the worker or delays idle sleep.
Failure breakdown
Where requests fell, and why
Target origins
Where your requests are headed
Client activity
Configured clients and retained request history in this window
| Client | Access | Requests | Completed | Failed | In progress | Last request |
|---|
No client activity yet
Requests will appear as clients use the API.
Recent requests
The latest activity in your workspace
| Request ID | Status | Client | Target origin | Created | Duration | Details |
|---|
“Completed” means a token was produced. Downstream token acceptance is not measured here.
REQUEST OBSERVABILITY
Requests
Inspect status, timing, and failures for your application.
| Request ID | Status | Client | Target origin | Created | Duration | Details |
|---|
No matching requests
Try a different request ID or status filter.
Loading requests…
History contains status and timing only. Proxy credentials, full page URLs, and solve tokens are excluded.
BUILD WITH SOLVE4ME
API reference
One HTTP API for submission, status, and cancellation.
Connect your application
Send your client API key as a bearer token. Keep it in your application's server-side secret configuration.
https://your-service.exampleThe examples use placeholder credentials. Dashboard access uses a separate session cookie; your API calls use the assigned client key.