Coding
API integration
Wire your code to third-party and model APIs without the guesswork and the silent failures.
Knowledge cards
Best practice
Tell Claude to Make API Failures Loud, Not Swallowed
An instruction to Claude that every external call must handle timeouts, non-2xx statuses, and malformed responses explicitly — surfacing typed errors — rather than the default happy-path client that assumes the network always works and JSON always parses.
Best practice
Paste the Real API Docs Before Claude Writes the Client
A grounding step: paste the actual endpoint reference — routes, request/response shapes, auth, error codes — into the context before asking Claude to write the integration, instead of relying on what it remembers about the API.