Happy-path examples lie by omission. These pages show the bodies you actually get when the entity is missing, when you have been throttled, and when the server failed. Parse the status code first; then the payload. A 404 is not a 500 with extra steps, and retrying a 404 will not create the planet.
Rate limits are expected under load. Back off, do not tight-loop, and read rate limits plus the rate-limiting pattern before you wrap a client. Server errors are retryable with jitter; missing entities are not.
The canonical error catalog is api/error-codes. These files are the shapes. play/errors maps the strings you will see in structsd to the skill that fixes them.
Open error examples when you are writing a client parser or a retry loop. If you just got an error string while playing, start at play/errors, not here.