Check whether a claim supplies six required fields.

Checks only that subject, claim, issuer, method, scope and issuedAt have truthy JSON values; it does not validate field types. It does not verify signatures, truth, expiry or execution authority. Missing or false-like values return HTTP 200 with conformant:false and missingFields. This handler is served by the production Postgres backend; the local JSON fixture backend may return 404.

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.