Testing & debugging recipes for AI agents
Test and debug your own integration: capture what your app sends, replay what providers send, and fake the callbacks you cannot schedule
These recipes point at your own application; there is no vendor token to paste. The move is substitution: your app gets a capture URL where the vendor's API used to be, and whatever it sends lands byte-for-byte as a capture. You test against real bytes, not a fixture written from guesswork.
They split the round trip. The submission tap diverts the outbound leg: you see what your app sends while its empty 200 holds real submissions back. The callback simulator plays the return leg, reshaping a captured submission into the vendor's callback and delivering it to localhost by the CLI on your machine, Authorization header overridden so the captured vendor credential never re-transits.
Tap first, simulator second; each recipe page carries the calculator that fits the pair to your plan.
Fake a vendor's async callback: reshape your app's captured submission into the callback shape and deliver it back to your app, no vendor involved.
See exactly what your app sends a vendor, without sending it: divert the outbound call to a capture URL and real submissions stay safely blocked.