Getting help

What to gather before asking, and what these documentation pages will never contain.

Before you ask

For an API problem: the request_id from the error body, the endpoint, and the approximate time.
For an agent behaving unexpectedly: the run, not a description of it. A trace answers questions a summary cannot.
For a connection problem: the registry key, the state it is in, and whether it worked before.
For anything intermittent: two examples. One is an anecdote.

Documentation is the surface people trust most and verify least, so it is worth saying plainly what is kept off it.

Customers, testimonials, benchmarks, case studies or press. None exist yet, and inventing one in an example is still inventing one.
Prices. They are read live from the billing catalogue and belong on the pricing page.
Absolute promises about what an agent cannot do at runtime. Controls are described as things you configure, because that is what they are.
Any credential, key, connection string or internal address, in an example or anywhere else.
Capabilities that are not connected yet, written as though they are. Where something is a preview, this documentation says so.