Start a benchmark: a one-time nonce for perf.submit for this kind
A client (pack version given) spends it from 90 seconds to 15 minutes after it is issued. A server (server_load, server_live; no pack) spends it within 7 days and no sooner than its run's measured seconds less 5. A server, and a launcher not signed in that sends sender "new", gets its own sender key here — no account needed: without one the backend issued, a new key comes back once (at most 3 new keys per address or IPv6 /64 a day and a ceiling over all addresses; none left is no error). Name the key in every later perf.begin and perf.submit; it counts publicly once it has accepted runs a day apart. Signed in or not; a nonce asked for while signed in is spent only by the same account. Limited per day.
/api/v1/perf/begin - Sign-in
- No scope
- Scope
- None
- MCP tool
perf.begin
Parameters
None.
Request body
| Field | Type and meaning |
|---|---|
kind required | string |
pack | object |
pack.fileId | string |
pack.portal required | string |
pack.projectId required | string |
sender | string |
Response 201
| Field | Type and meaning |
|---|---|
expiresAt always | string · date-time |
nonce always | string |
notBefore always | string · date-time |
sender | string |
Errors
| Status | Type and meaning |
|---|---|
400 | The request was not understood. |
401 | Sign in and try again. |
404 | There is nothing here, or nothing you may see. |
429 | Too many requests. |
500 | Something on our side went wrong. |
Every error comes back as { code, message, requestId }. Errors