When your canister needs to talk to an external API, this shows you how to make HTTPS requests that actually reach consensus across replicas. The tricky part is that every node runs the same code, so you need a transform function to strip out non-deterministic fields like timestamps and header ordering before responses are compared. The examples cover cycle cost management (outcalls aren't free), the 2MB response limit, and why you should never skip max_response_bytes unless you want to burn 21 billion cycles per call. Also walks through idempotency patterns for POST requests, since a 13-node subnet means your "create order" endpoint gets hit 13 times. Both Motoko and Rust examples use helper functions that auto-compute cycle costs.
npx skills add https://github.com/dfinity/icskills --skill https-outcalls