Skip to main content
POST
Setup reports
An agent can submit one short report about an unexpected setup problem before it is connected. This public operation requires no authentication or browser marker and does not look up or create an account. Reports go by email to one server-configured Tokenrip administrator. Follow the canonical reporting instructions for the copyable HTTP example, when to report, and the in-chat fallback. Continue a usable setup route first. Submit once with a 30-second limit and no automatic retry. Include only observations already available, without keys, sign-in codes, authorization headers, proxy credentials, full environment dumps, or conversation transcripts. Reporting does not resolve an uncertain sign-in outcome.

JSON request

Send Content-Type: application/json. The body must be an object with only these fields, at most 32 KiB including inflated or chunked input. Field limits count Unicode code points. Strings are trimmed. Required fields must remain nonblank; optional blank strings are omitted. Nulls, nonstrings, unknown properties, nonobject bodies, NUL, and ill-formed Unicode are rejected. Contact is optional and is not proof of identity, a mail header, or a callback instruction; no automatic reply is sent. Omit it if unavailable rather than requesting new mailbox access. Caller text cannot choose the recipient or any email header.

Queued receipt

HTTP 202 means one email outbox record was committed:
The UUID is the receipt identity. Queued means acceptance for email delivery, not confirmed delivery or guaranteed follow-up. The mail provider is not called during this request. There is no report retrieval endpoint; the receipt is not a bearer capability. Email can fail after acceptance and has no automatic delivery retry. If no HTTP tool is available, a timeout occurs, or submission fails, leave the concise summary in the conversation and state that delivery was not confirmed. A lost response may still leave a queued email. Do not retry or report a reporting error.

Errors

Errors use { "ok": false, "error": "ERROR_CODE", "message": "Description" }. Rejected content is not echoed. Rate-limit headers use the existing named bucket suffixes. Report counters are per process and reset on restart; IP attribution uses the existing proxy configuration. These limits do not promise durable quotas. Reporting is deliberately public REST only, with no CLI command, MCP tool, or operator mirror.