Get detailed detection results | Lakera API documentation

The results endpoint screens submitted content according to the policy assigned to the specified project. It then returns the confidence level results of the detectors. It doesn’t make a flagging decision or create a request log in Guard. It can be used to analyze data and calibrate detector threshold levels for policies.

You can use the results endpoint to analyze historic LLM prompt and response data without worrying about triggering alerts or affecting monitoring, as they are not logged as screening requests by Lakera Guard.

If no project ID is passed in the request, then the default Lakera Guard policy is used, which runs all Guard defenses and detectors at the highest sensitivity level.

results requests are not logged as screening requests in Lakera Guard and do not appear in the platform or exported logs. It should not be used in runtime GenAI application security decisions as it removes the ability to control your defenses using policies.

The `results` endpoint screens submitted content according to the policy assigned to the specified project. It then returns the confidence level results of the detectors. It doesn't make a flagging decision or create a request log in Guard. It can be used to analyze data and calibrate detector threshold levels for policies. You can use the `results` endpoint to analyze historic LLM prompt and response data without worrying about triggering alerts or affecting monitoring, as they are not logged as screening requests by Lakera Guard. If no project ID is passed in the request, then the default Lakera Guard policy is used, which runs all Guard defenses and detectors at the highest sensitivity level. <Warning>`results` requests are not logged as screening requests in Lakera Guard and do not appear in the platform or exported logs. It should not be used in runtime GenAI application security decisions as it removes the ability to control your defenses using policies.</Warning>

Authentication

AuthorizationBearer

Bearer authentication using API key. Generate an API key from the Lakera platform. Example: Bearer sk_123…

Request

This endpoint expects an object.

messageslist of objectsRequired

List of messages comprising the interaction history with the LLM in OpenAI API Chat Completions format. Can be multiple messages of any role: user, assistant, system, tool or developer.

project_idstringOptional

ID of the relevant project. The request will be screened according to the policy assigned to the project. If no project ID is passed then the Lakera Guard Default Policy will be used for screening.

metadatamap from strings to anyOptional

Metadata tags can be attached to screening requests as an object that can contain any arbitrary key-value pairs. Common use cases include specifying the user or session ID.

dev_infobooleanOptional

When true the response will return an object with developer information about the build of Lakera Guard.

Response

Successful retrieval

resultslist of objects or null

List of detector results

If no project ID is passed in the request, then the default Lakera Guard policy is used, which runs all Guard defenses and detectors at the highest sensitivity level.

1	import requests
2
3	url = "https://api.lakera.ai/v2/guard/results"
4
5	payload = { "messages": [
6	{
7	"content": "string",
8	"role": "system"
9	}
10	] }
11	headers = {
12	"Authorization": "Bearer <token>",
13	"Content-Type": "application/json"
14	}
15
16	response = requests.post(url, json=payload, headers=headers)
17
18	print(response.json())

1	{
2	"results": [
3	{
4	"project_id": "string",
5	"policy_id": "string",
6	"detector_id": "string",
7	"detector_type": "string",
8	"result": "string",
9	"custom_matched": true,
10	"message_id": 1
11	}
12	]
13	}