API health

Every documented operation is called against the production API on a schedule and the answer is held against this reference: the status, the media type, the schema, the fields promised against the fields sent, the cache contract, and who may call it. The run is read twice, as questions about the API as a whole and endpoint by endpoint. This is the last one, in full, failures included.

Whether the API is answering at all is a different question, and the status page answers it: a deploy serving last week's contract is perfectly available and wrong. The printed examples are checked too.