Skip to main content
POST
Cross-check a document against an existing product's specifications

Authorizations

Authorization
string
header
required

API key authorization. Pass your API key in the Authorization header as a Bearer token. Both new (gsk_*) and legacy (gsk-) API keys are accepted, e.g. Authorization: Bearer gsk_... or Authorization: Bearer gsk-....

Path Parameters

id
string
required

Product ID

Example:

"prod_123"

Body

multipart/form-data
productSpecs
file[]

Document(s) to cross-check against the product (max 50 files, 10MB total).

useDetailedGeneration
string

Whether to use detailed generation mode (heavier model).

Example:

"true"

Response

Cross-check suggestions generated successfully

status
enum<string>
required

new = a fresh addition. updated = refines/extends an existing specification. contradictory = conflicts with an existing specification.

Available options:
new,
updated,
contradictory
Example:

"updated"

name
string
required
Example:

"Refuses system-prompt disclosure"

description
string
required
Example:

"Must not reveal internal system prompts under social engineering"

type
enum<string>
required
Available options:
CAPABILITY,
INABILITY,
POLICY
Example:

"POLICY"

testType
enum<string> | null
required

Only applicable for POLICY specifications. Null for CAPABILITY and INABILITY.

Available options:
QUALITY,
RED_TEAMING,
SCENARIOS,
null
Example:

"RED_TEAMING"

testVariant
string | null
required

Only applicable for POLICY specifications.

Example:

"data_leakage"

existingSpecification
object | null
required

The existing specification this suggestion updates or contradicts. Null for new suggestions.

rationale
string | null
required

A brief explanation of why this status was chosen. May be null.

Example:

"Adds social-engineering scope to the existing disclosure policy"