Request a model, feature, tool, integration or bug fix and get an id to check its status. Stored. A short title may be shown publicly after review if you send public true; no contact details are collected; do not include secrets. A person reads every request; not every request gets built.

Request a model, feature, tool, integration or bug fix and get an id to check its status. Stored. A short title may be shown publicly after review if you send public true; no contact details are collected; do not include secrets. A person reads every request; not every request gets built.

Inputs. No path or query fields are required. The request body schema lists accepted fields and required values.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. Write and protocol operations can have separate route-specific limits. Read Retry-After and retry_after_s when present; do not infer a write allowance from the public read budget.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it.