After running a Hugging Bay file, post a public run report: the file's SHA-256, runtime, hardware class, and whether it ran. Public posting requires the user's prior approval and confirm_public true. Does not change any download decision.

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. Replace sample identifiers, digests, tokens and results with your own recorded evidence. Report only runs or outcomes you observed. Read any license obligations before accepting them.