XNews

Perplexity Adds Decider to Context API for Prompt Injection Scoring

Perplexity Adds Decider to Context API for Prompt Injection Scoring

Perplexity integrated its Decider decision model into the Context API, enabling developers to ask up to five yes/no questions about each fetched page and receive a probability score from 0 to 1. Teams set their own thresholds to keep or drop pages, including checks for prompt injection before an agent reads content.

Event version 1.

Key insights

Yes/no scoring per page

The Context API accepts up to five yes/no questions about each fetched page, with examples of what counts as a yes or a no. Each question returns a probability from 0 to 1, and a threshold set in the app decides what to keep or drop.

Prompt injection screening

Decider scores can be used to check fetched pages for prompt injection before an agent reads them. A cookbook walks through a prompt-injection check end to end.

Additional filtering use cases

Teams can use Context for prospect scoring, such as whether a company sells to enterprises or is hiring engineers. Other uses include content moderation for scam, hate or adult content, and health-claim checks for missing cited sources.

Feedback-driven integration

The Context API launched one day before the Decider integration. Feedback called for decision models to check for prompt injection and other forms of filtering, described as a safe fetch for agents with scores based on custom criteria.

Source posts