Contact hello@humanbased.ai. Explain what you were trying to do, the step you reached, and the message you saw.
Include the relevant record
| Problem | Useful information |
|---|---|
| Task, submission, or review | Campaign, Task, and Submission identifiers; the time; current result; and the specific feedback you need help with |
| Learning or eligibility | Course or requirement name, the recorded result, and the Campaign that checks it |
| API access | Request time, environment, request path, HTTP status, error code and message, and a redacted description of the subscription scope |
| Earnings or payment | The original record identifier, time, amount, state, and exact error |
If two pages disagree, include both results and how the records relate. A small redacted screenshot can help explain the discrepancy. You do not need to include the full dataset or unrelated taskA specific item a contributor claims or enters materials.
Protect credentials and personal information
Leave passwords, login verification codes, complete API keys, private keys, seed phrases, and signing credentials out of the request. Submit identity documents through the relevant verification process rather than a support email or task form.
If a submissionThe record created when work is submitted, payment request, or API write has an unclear outcome, inspect its original record before trying again. Keeping the original identifier helps support investigate the same attempt and avoids creating duplicates.
A useful request
What I was trying to do:
Portal or API environment:
Campaign / Task / Submission / request identifier:
Time and timezone:
Last completed step:
Message or status shown:
What I expected:Fill only the fields relevant to your issue, and redact sensitive values before sending.
After you write
Support replies by email to the address you wrote from. While you wait, keep the original record. Before you retry, confirm in that record that the earlier attempt did not go through: a duplicate submission, withdrawal, or payment has to be resolved separately.
Report a product bug
When a page misbehaves, open the bug report from the portal header: Report a bug in the Contributor portal, Report Bug in the Developer portal. Describe the steps, what you expected, and what happened, and add screenshots with personal data removed. My Reports lists what you have filed. In the Contributor portal, an accepted report earns a USDC reward by severity, shown on the form and credited to Earnings.