Dashboard
Tasks per day
Error codes
| Code | Occurrences |
|---|
System
Volume per client
| Client | Tasks | Ready | Failures | Rate | Last |
|---|
Tasks
Metadata only: no page parameters or tokens are stored in the database.
| taskId | Client | Status | Code | Created | Duration | Relay |
|---|
Users
Registered accounts. A key request awaits your approval; suspending revokes the key and closes sessions.
| # | Role | Status | 2FA | Key | Plan | Credits | Signed up | Last login | Note |
|---|
Security log for
| When | Event | IP | Browser | Details |
|---|
Subscriptions
Plan requests from users. Approving applies the plan and its monthly quota immediately.
| # | Current plan | Requested | Message | When | Note |
|---|
Bitcoin orders
Receiving address — · credited automatically after — confirmation(s). Mark an order paid by hand when the amount sent does not match exactly.
| # | User | Credits | Amount | Sats | Status | Transaction | Created | Expires |
|---|
Invoices
Drafts generated from the month's produced tokens (paid plans). Issuing sends the invoice and payment instructions; payment is recorded manually.
| # | Period | Plan | Tokens | Amount | Status | Issued | Paid | Ref. |
|---|
Charts
Activity per client, sign-ups and revenue.
Tokens produced per day
Sign-ups per day
Revenue per month (paid / pending)
This month's quotas
| Plan | Used | Quota |
|---|
Clients and keys
Keys are created from user accounts (Users tab): here, rotation or revocation. The database keeps only the fingerprint.
| Client | Status | Prefix | Note | Created | Tasks | Ready | Last |
|---|
"env" clients come from MINIMAL_API_KEYS and are managed in Dokploy.
Page requests
Requests submitted by clients from their console. Move them to reviewing, calibrating, validated or rejected; the note is visible to the client. "In registry" means the page is already served by the API.
| # | Client | Page | Sitekey | Action | Ent. | Target request / volume | Status | Received |
|---|
Request ·
To calibrate: preparer-release.py --url … --sitekey … --action … --promouvoir on the calibration workstation, then import into minimal.v1 and deploy. The request switches to "in registry" automatically once the page is served.
Registered pages
Every page in the API registry. A page can show "Needs revalidation" even after it is fixed and redeployed: the flag only clears on a fresh success that happens to match the exact fleet path (relay, mode, release) the last failure was recorded on, which is not guaranteed to recur. Use "Mark revalidated" once you have checked the page by hand.
| Page | Sitekey | Action | Ent. | Status |
|---|
Transport
The forge from A to Z: every relay as it declares itself, the version the payload announces, the TLS fingerprint reCAPTCHA sees, and which actions each exit is allowed to serve.
Policy
Reference fingerprints
Relays (hub) every relay the hub can mint through — add, qualify, enable, remove
| Relay | Credit | Enabled | State | Native / declared | Egress | QUIC | TLS | Mints | Temperature | Débit / rotation | Agent (start / stop / version / proxy) |
|---|
Agent: a small supervisor runs on the relay machine (pull, no open port) and executes Start / Stop / Restart, library (Chrome version) and egress proxy changes from here. Issue its key with “Agent key”, paste it on the machine, run deploy/relay-agent.py. Routing on the hub is by credit: createV2 never uses a weak relay, good is preferred over unknown, equals rotate. The env relay is REV3_CHROMET (its URL changes only via env); every other relay lives on the data volume and survives redeploys.
Nodes (pull agents)
| Node | Credit | Serves | Relay | State | Native / declared | Egress | QUIC | TLS | Score guard | Temperature |
|---|
Routing is by capability: a node only receives tasks for the profiles it advertises (MINIMAL_NODE_PROFILES). A weak exit serves login only; createV2 needs a good exit. A relay behind a proxy shows egress: proxy — Windows relays cannot keep HTTP/3 through a proxy, so it stays informational until a working provider is wired on the relay side.
Profiles
Generate and edit forge profiles field by field. Base profiles are read-only; saving one under a base name creates an admin override on the data volume. Every save is validated by the real registry — if it no longer loads, the change is reverted.
| Name | Source | Action | Executes | Served |
|---|
Editor
Native generation — per-slot native vs replay. Default = max-native (validated). Page-descriptor slots (URL, title, SRI 65, callback 29, scripts 42) stay replay: they describe the target page and can't be forged.
No credential-like value is accepted (password, cookie, token, proxy, user:pass@ URLs). Fixtures already present on the volume can be referenced without shipping them again.
Public status
What the site's status page shows. Published immediately, no commit needed.