Integration Walkthrough: Sprappy Filter in Front of SPRAPP Panel
Wire Sprappy Filter threat scoring ahead of a SPRAPP Panel call for a screened multi-model pipeline.
The Goal
This walkthrough connects two SPRAPP products: Sprappy Filter screens incoming requests, and only clean traffic reaches SPRAPP Panel for multi-model reasoning. The result is a pipeline that doesn't waste expensive panel calls on malicious or junk input.
Why Order Matters
Panel is your most expensive call — several models run per query. You don't want to spend that on a prompt-injection attempt or abusive input. Putting Sprappy Filter first means threats are rejected cheaply before they trigger a multi-model fan-out. Order is the whole point of the integration.
Step 1: Score With Sprappy Filter
On each incoming request, call Filter's scoring endpoint with the user input. You get back a threat score and category signals. This is fast and cheap relative to what comes next. Setup is in the docs at https://doc.sprapp.com.
Step 2: Gate on the Score
Apply your threshold. If the score is high, block or flag and return early — Panel is never called. If it's low, pass the request forward. This single gate is what protects your panel budget and reduces attack surface.
Step 3: Call SPRAPP Panel
For requests that clear the filter, send the prompt to Panel. Because the input is pre-screened, the models reason over cleaner, safer text, and you've avoided spending multi-model tokens on garbage.
Step 4: Consider an Output Pass
Filtering input is half the story. You can also run Panel's output back through a screening step before showing it to users, depending on your risk model. Decide deliberately whether your application needs output screening too.
Step 5: Log the Whole Chain
Log the filter score, the gate decision, and the panel result together. This lets you see how often the filter is saving panel calls, and whether your threshold is tuned right. The docs at https://doc.sprapp.com list useful fields.
Honest Limitations
This pipeline reduces wasted panel spend and obvious threats, but it isn't a complete security solution. The filter won't catch everything, and a panel of models can still disagree or err on legitimate hard questions. Treat the chain as layered defense and quality improvement, not a guarantee.
Result
You now have a cost-aware, screened pipeline: Sprappy Filter as the cheap gate, SPRAPP Panel as the expensive specialist that only runs on traffic worth its cost. Extend it with routing and logging as documented at https://doc.sprapp.com.