Skip to content
0G Private Computer Cookbook

Contact and feedback

Before anything else, check whether the symptom is already covered in Troubleshooting — the common failures have a confirmed cause and a fix there.

What to include

Section titled “What to include”

Whichever channel you use, these turn a guess into an answer:

Include Why
request_id Present on every error response, next to the error object. It is the only handle that identifies one specific request.
The exact error.type and error.code Several codes share a status. 403 insufficient_scope and 403 access_denied have different fixes.
Model ID and any X-0G-Provider-* headers you sent Routing constraints change which providers were eligible, and most 503s are about eligibility.
Whether it is reproducible A failure that happens once and a failure that happens every time are different problems.

Never include an API key, a wallet private key, or a full prompt containing data you would not publish. A request_id is enough to locate a request; the key is not needed and should be treated as compromised if it is ever pasted anywhere.

Reporting an API problem

Section titled “Reporting an API problem”

The developer community on Discord is the fastest route: discord.gg/0glabs. Post the request_id and the details above rather than a screenshot — the identifier is what makes a specific request findable.

Reporting a docs problem

Section titled “Reporting a docs problem”

Something wrong, out of date, or missing on this site — a code sample that does not run, a field that no longer exists, a step that skips something.

Raise it in the same Discord channel for now. Include the page URL and what you expected to happen; a code sample that fails is worth more than a description of it.

Documentation pages state the date of any figure that changes over time (model counts, catalog snapshots). If a page contradicts what GET /v1/models or the Console returns right now, the live API is correct and the page is the bug.

Requesting something that does not exist yet

Section titled “Requesting something that does not exist yet”

Model availability, a trust tier for a specific model, an endpoint, a limit — these are product decisions rather than documentation ones.

Discord again, but say what you were trying to build rather than only what you want added — the use case is what makes a request actionable.

Section titled “Related”