response-compliance

To validate Response API compliance, run the official OpenResponses test suite against your configured endpoint to detect schema, validation, and behavioral mismatches. The test suite verifies that your api/v1/responses routing and authentication flags produce outputs matching expected schema validation rules.

SSE streaming compliance testing verifies that your Response API endpoint correctly handles the streaming lifecycle, ensuring server-sent events match the expected OpenResponses schema and validation rules. It also checks for typical failure patterns like JSON parsing issues and missing output items during streaming.

Yes, you can execute targeted test filtering to run compliance tests only for selected scenarios such as tool calling, multimodal image inputs, system prompt handling, and multi-turn conversation history. This isolates specific OpenResponses API behaviors for focused validation.

Response API compliance failures often stem from schema field nulls or Zod validation errors where your output deviates from OpenResponses expectations. Debugging common failure patterns involves checking JSON parsing issues, missing output items, and ensuring correct schema field population.

Yes, testing OpenResponses compliance locally requires starting your dev server with the required mock settings and executing the test command against your local APP_URL. This ensures correct routing for api/v1/responses and supported authentication flags so responses match expected validation rules.