Connect your AI to Your own app
The credential never enters the model context: it lives in the FlurryPORT secret store, deliveries are signed server-side, and every send returns a receipt your agent can quote.
- Auth model
- none
- Scopes
- No third-party credential. The app under test is yours; a recipe that delivers into it references the app's own dev credential by secret name (see each recipe's walkthrough).
- Provider docs
- https://flurryport.io/recipes/security
Recipes for Your own app
flurryport:vendor-callback-simulatorintake
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.
flurryport:vendor-submission-tapintake
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.