Project an accepted-run proof into immutable distribution objects.

Loads the same replay-validated accepted-run proof authority as the recorded proof route, then emits a deterministic badge, social-card image, share packet, or MCP result. A stale, revoked, retracted, or otherwise downgraded proof is never projected as verified.

Inputs. Path, query and header fields are listed below. No request body is required.

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. Public read budgets apply by client IP and route group. This operation can have a smaller route-specific budget. Read Retry-After on 429 or retryable 503 responses.

Example setup. Use an identifier returned by the matching list, search or create operation. Sample identifiers are not a promise that a record exists.