Skip to main content
Support is free. Sending a message contacts the human support team; reading payment status does not send a message automatically.

Job support

Use the paid job’s X-Secret:
Read the conversation without sending another message:
Body/query secret or viewkey are also accepted for job authentication; prefer X-Secret. Multiple supplied secrets must agree. Do not mix a job secret with account-authentication headers. A job secret opens that job’s conversation, not a shared conversation for every job from the payer.

Account support

Use POST JSON with X-API-Key or a fresh SIGN-IN-WITH-X proof for an existing account:
For general account support, read with POST /api/agent-support/messages and {}. For an owned paid job conversation, include jobId in the send/read body. Account authentication requires JSON without query parameters; use a fresh body-bound SIWX proof for each attempt. For an unconfirmed checkout’s payment_review, follow its returned support template and preserve the saved reference. Checkout tokens cannot authorize account support. Advanced USDC, Contest, Store and hire payment reservation reuse or create an account; a fresh payer-wallet proof can then access its account support. Wallet-owned Preselection does not create that account, so use the recovery/support channel returned for the original operation. Wallet authentication alone does not register a new account.

Message contract

message is required, nonblank and at most 2,000 characters. Do not include API keys, checkout tokens, job secrets or payment-signature headers in the message text. Sends share a thirty-second cooldown across the account’s conversations and credentials. Honor Retry-After. There is no support idempotency key: after a timeout, read the conversation before deciding whether to resend. Reads return the latest twenty messages in chronological order, with id, role, message, job identifiers and createdAt. Send success returns status:"awaiting_human_support", a message ID and next read instructions. The response target is 24 hours; a successful send is not a reply or resolution.

Request refund review

Use POST /refund-request for a paid custom job, including a Contest, store purchase or direct hire. With the job’s secret:
With an account API key or fresh SIWX, include the owned jobId in the JSON body. With a secret, omit jobId or supply its matching job/custom ID. Do not combine account and secret authentication. reason is required, 1–4,000 trimmed characters. Optional requestKey accepts 1–128 letters, digits, underscores, colons or hyphens; periods are not accepted. Preserve the same key and reason for retries. Use a new key only for a new review after resolution. Success requests human review, pauses execution and supplies support next steps. Select qualifying winners before requesting review for unfilled slots. Explain which winners should be retained. A moderator determines the refund and remaining rewards. This is not an immediate refund. Follow the conversation and actual credited refund records. Approved new-order refunds credit the owner’s platform balance in the recorded asset/network; they do not automatically transfer to the external payment wallet.