Cross-check a document against an existing product's specifications
Uploads one or more documents (PRD, spec, design doc, etc.), generates
candidate specifications from them using the product’s existing description
as the generation base, and cross-checks each candidate against the
product’s CURRENT specifications. Returns classified suggestions —
additions (new), updates to an existing specification (updated), and
contradictions of an existing specification (contradictory).
This endpoint persists NOTHING: it only returns suggestions. Applying them (creating, updating, or removing specifications) is a separate, explicit step the user performs afterwards via the specification endpoints, so nothing changes without confirmation and unaffected specifications remain untouched.
Authorizations
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
Product ID
Body
One or more documents to cross-check, plus optional generation mode
Response
Cross-check suggestions generated successfully
new = a fresh addition. updated = refines/extends an existing specification. contradictory = conflicts with an existing specification.
new, updated, contradictory "updated"
"Must not reveal internal system prompts under social engineering"
CAPABILITY, INABILITY, POLICY "POLICY"
Only applicable for POLICY specifications. Null for CAPABILITY and INABILITY.
QUALITY, RED_TEAMING, SCENARIOS "RED_TEAMING"
Only applicable for POLICY specifications.
"data_leakage"
The existing specification this suggestion updates or contradicts. Null for new suggestions.
A brief explanation of why this status was chosen. May be null.
"Adds social-engineering scope to the existing disclosure policy"