▸case-01 I have an existing Python backend application handling inventory management for items and warehouses. I need to generate a complete, valid OpenAPI 3.1 specification in YAML format for these REST endpoints. Please output the full YAML schema along with clear, actionable setup steps to validate our API routes against this spec. | fail→fail | 34,013 | 35,022 | +3% | 1 | 1 | 0% | 8,075 | 5,144 | -36% | 0 | 0 | — |
▸case-02 We are taking a design-first approach for a new subscription billing API. Can you produce a initial OpenAPI 3.1 YAML contract containing routes for plan management and invoice processing? I need the output to include the structured YAML document and verification guidelines for testing route compliance. | fail→fail | 27,970 | 24,045 | -14% | 1 | 1 | 0% | 6,101 | 5,543 | -9% | 0 | 0 | — |
▸case-03 We are building a new GraphQL service for client user profiles and post feeds. Can you design the GraphQL SDL schema file with query types, mutation types, and custom directives? | pass→pass | 18,191 | 16,282 | -10% | 1 | 1 | 0% | 3,882 | 3,562 | -8% | 0 | 0 | — |
▸case-04 We need to define a high-performance gRPC service for real-time order matching in protobuf format. Please write the `.proto` file defining the service methods, RPC request/response messages, and stream options. | pass→pass | 21,881 | 16,111 | -26% | 1 | 1 | 0% | 4,367 | 3,366 | -23% | 0 | 0 | — |
▸case-05 We are migrating our user table to PostgreSQL and need SQL DDL migration scripts to add index constraints and foreign key relationships for payment records. Please output the SQL migration statements. | pass→pass | 12,674 | 8,847 | -30% | 1 | 1 | 0% | 2,298 | 1,881 | -18% | 0 | 0 | — |
▸case-06 In OpenAPI 3.0, developers used `nullable: true` for optional payload attributes. We are upgrading our user profile schema to OpenAPI 3.1.0 where `nullable: true` is obsolete. How should a nullable string field be defined in the schema component? | fail→pass | 7,787 | 7,944 | +2% | 1 | 1 | 0% | 1,471 | 1,763 | +20% | 0 | 0 | — |
▸case-07 We are building an event notification system that sends HTTP POST payloads to subscriber URLs when an invoice status changes to paid. We want to document this outbound callback in our OpenAPI 3.1 spec using the top-level standard feature instead of path objects. How should this be declared? | pass→pass | 10,864 | 12,904 | +19% | 1 | 1 | 0% | 2,241 | 2,685 | +20% | 0 | 0 | — |
▸case-08 We want to enforce a custom JSON Schema dialect for component schemas across our enterprise API standard in OpenAPI 3.1. Which top-level keyword in the spec allows setting the default schema dialect for all contained schemas? | pass→pass | 4,108 | 4,354 | +6% | 1 | 1 | 0% | 759 | 974 | +28% | 0 | 0 | — |
▸case-09 We have a notification API that sends either email, SMS, or push notifications. In our OpenAPI 3.1 schema, we want to combine `oneOf` with a field called `channelType` to determine which schema to validate against. Show the exact schema structure for this polymorphic schema using `discriminator`. | pass→pass | 9,724 | 9,968 | +3% | 1 | 1 | 0% | 2,099 | 2,380 | +13% | 0 | 0 | — |
▸case-10 We have completed our OpenAPI 3.1 specification file `api-spec.yaml`. What standard open-source CLI tooling command should we use to automatically generate a TypeScript client SDK from this file? | pass→pass | 7,148 | 7,555 | +6% | 1 | 1 | 0% | 1,330 | 1,595 | +20% | 0 | 0 | — |
▸case-11 We need to set up a static web portal to render our OpenAPI 3.1 contract interactively for external developers. We prefer a zero-build static HTML embed tool that renders OpenAPI 3.1 cleanly without running a complex server stack. What solution and HTML snippet should we use? | fail→fail | 15,670 | 12,084 | -23% | 1 | 1 | 0% | 2,949 | 2,477 | -16% | 0 | 0 | — |
▸case-12 We want to automate CI/CD validation of our OpenAPI 3.1 YAML files to catch missing operation IDs, unhandled error responses, and invalid types. What standard CLI tool and rule file format should we integrate into GitHub Actions? | pass→pass | 10,388 | 12,770 | +23% | 1 | 1 | 0% | 1,968 | 2,670 | +36% | 0 | 0 | — |
▸case-13 How do we define an OAuth2 Authorization Code security scheme with PKCE in the `components.securitySchemes` section of an OpenAPI 3.1 document? | pass→pass | 10,542 | 11,929 | +13% | 1 | 1 | 0% | 1,945 | 2,536 | +30% | 0 | 0 | — |
▸case-14 We want our OpenAPI 3.1 spec to support dynamically switching between sandbox and production hostnames with a configurable port variable. How should the `servers` array be structured? | pass→pass | 11,257 | 7,346 | -35% | 1 | 1 | 0% | 2,072 | 1,614 | -22% | 0 | 0 | — |
▸case-15 We need to configure an API key authentication mechanism where client apps send `X-API-Key` in the request headers. How do we declare this in `components.securitySchemes` and apply it globally? | pass→pass | 9,300 | 4,723 | -49% | 1 | 1 | 0% | 1,396 | 1,133 | -19% | 0 | 0 | — |
▸case-16 In an OpenAPI 3.1 specification, we have a reusable `ErrorResponse` model defined under `components.schemas`. How do we reference this schema inside a 400 Bad Request response body for a REST endpoint? | pass→pass | 8,603 | 6,710 | -22% | 1 | 1 | 0% | 1,758 | 1,597 | -9% | 0 | 0 | — |
▸case-17 How do we model a file upload endpoint accepting `multipart/form-data` with a binary file field `document` and a text field `description` in OpenAPI 3.1? | fail→pass | 8,987 | 11,104 | +24% | 1 | 1 | 0% | 1,739 | 2,477 | +42% | 0 | 0 | — |
▸case-18 We are designing a REST API contract for managing customer orders. We need to document endpoints for listing customer orders (`GET /customers/{customerId}/orders`) and fetching a specific order (`GET /customers/{customerId}/orders/{orderId}`). How should the path parameters be declared in OpenAPI 3.1? | pass→pass | 11,072 | 9,889 | -11% | 1 | 1 | 0% | 2,282 | 2,270 | -1% | 0 | 0 | — |
▸case-19 Our API endpoint returns rate limit information via custom response headers `X-RateLimit-Limit` and `X-RateLimit-Remaining`. How should these headers be defined in an OpenAPI 3.1 response object? | pass→pass | 9,714 | 6,989 | -28% | 1 | 1 | 0% | 2,033 | 1,579 | -22% | 0 | 0 | — |
▸case-20 We are sunsetting an old v1 user search endpoint `GET /v1/users/search`. We want OpenAPI readers and API documentation tools to mark this route as deprecated without removing it from the contract. Which field flags this? | pass→pass | 3,901 | 5,709 | +46% | 1 | 1 | 0% | 609 | 1,126 | +85% | 0 | 0 | — |
▸case-21 An endpoint `GET /reports/{id}` can return either `application/json` or `application/pdf`. How do we document multiple content types for a 200 OK response in OpenAPI 3.1? | pass→pass | 8,161 | 7,671 | -6% | 1 | 1 | 0% | 1,568 | 1,810 | +15% | 0 | 0 | — |
▸case-22 When initializing an OpenAPI 3.1 document, what required top-level fields must be present inside the `info` object according to the OpenAPI specification? | pass→pass | 4,435 | 3,553 | -20% | 1 | 1 | 0% | 838 | 894 | +7% | 0 | 0 | — |