Get Started with Qualifire
Using Qualifire with Portkey
1. Add Qualifire Credentials to Portkey
- Click on the
Admin Settingsbutton on Sidebar - Navigate to
Pluginstab under Organisation Settings - Click on the edit button for the Qualifire integration
- Add your Qualifire API Key (obtain this from your Qualifire account at https://app.qualifire.ai/settings/api-keys/)
2. Add Qualifire’s Guardrail Checks
- Navigate to the
Guardrailspage and click theCreatebutton - Search for any of the Qualifire guardrail checks and click
Add - Configure the specific parameters for your chosen guardrail
- Set any
actionsyou want on your check, and create the Guardrail!
Guardrail Actions allow you to orchestrate your guardrails logic. You can learn more about them here
Available Guardrail Checks
Qualifire provides a comprehensive set of guardrail checks organized into five main categories:Security
| Check Name | Description | Parameters | Supported Hooks |
|---|---|---|---|
| PII Check | Checks that neither the user nor the model included PIIs | None | beforeRequestHook, afterRequestHook |
| Prompt Injections Check | Checks that the prompt does not contain any injections to the model | None | beforeRequestHook |
Safety
| Check Name | Description | Parameters | Supported Hooks |
|---|---|---|---|
| Sexual Content Check | Checks for sexual content in the user input or model output | None | beforeRequestHook, afterRequestHook |
| Harassment Check | Checks for harassment in the user input or model output | None | beforeRequestHook, afterRequestHook |
| Hate Speech Check | Checks for hate speech in the user input or model output | None | beforeRequestHook, afterRequestHook |
| Dangerous Content Check | Checks for dangerous content in the user input or model output | None | beforeRequestHook, afterRequestHook |
Reliability
| Check Name | Description | Parameters | Supported Hooks |
|---|---|---|---|
| Instruction Following Check | Checks that the model followed the instructions provided in the prompt | None | afterRequestHook |
| Grounding Check | Checks that the model is grounded in the context provided | None | afterRequestHook |
| Hallucinations Check | Checks that the model did not hallucinate | None | afterRequestHook |
| Tool Use Quality Check | Checks the model’s tool use quality. Including correct tool selection, parameters and values | None | afterRequestHook |
Policy
| Check Name | Description | Parameters | Supported Hooks |
|---|---|---|---|
| Policy Violations Check | Checks that the prompt and response didn’t violate any given policies | policies (array of strings) - For more details | beforeRequestHook, afterRequestHook |
Configuration Examples
Policy Violations Check
For the Policy Violations Check, you can specify custom policies to enforce:Add Guardrail ID to a Config and Make Your Request
- When you save a Guardrail, you’ll get an associated Guardrail ID - add this ID to the
input_guardrailsoroutput_guardrailsparams in your Portkey Config - Create these Configs in Portkey UI, save them, and get an associated Config ID to attach to your requests. More here.
- NodeJS
- Python
- OpenAI NodeJS
- OpenAI Python
- cURL
Use Cases
Qualifire’s guardrails are particularly useful for:- Content Moderation: Filtering harmful or inappropriate content in user inputs and AI responses
- Compliance: Ensuring AI responses adhere to company policies and regulatory requirements
- Quality Assurance: Detecting hallucinations, instruction violations, and poor tool usage
- Data Protection: Preventing PII exposure and ensuring data privacy

