▸case-01 Our company is launching a public developer hub built with Next.js on top of our Kong gateway. External developers need to register webhook endpoints, monitor their rate limits and monthly quotas, and generate sandbox keys. Deliver a comprehensive developer portal specification that covers the user onboarding journey, webhooks management UI, and admin panel config. | fail→fail | 44,256 | 36,955 | -16% | 1 | 1 | 0% | 8,253 | 7,200 | -13% | 0 | 0 | — |
▸case-02 We are building a multi-tenant portal for our B2B SaaS customers to browse our REST endpoints, manage environment keys for production and sandbox, and track API calls by organization. Please generate the setup artifacts including service catalog organization, multi-tenant security configuration, usage visualization specs, and documentation integration plan. | pass→pass | 43,464 | 42,776 | -2% | 1 | 1 | 0% | 8,250 | 8,630 | +5% | 0 | 0 | — |
▸case-03 We need to optimize upstream routing latency in our Kong API Gateway by writing custom Lua plugins to strip custom headers and rewrite URIs before proxying to internal gRPC microservices. Provide the Kong Lua plugin source code and plugin schema definition. | pass→pass | 21,910 | 18,438 | -16% | 1 | 1 | 0% | 3,184 | 3,986 | +25% | 0 | 0 | — |
▸case-04 Provide a backend Node.js Express implementation for an OAuth2 authorization server handling the `/oauth/v2/token` endpoint with authorization_code grant type, authorization header validation, and database token persistence. | pass→pass | 20,338 | 31,536 | +55% | 1 | 1 | 0% | 4,599 | 6,166 | +34% | 0 | 0 | — |
▸case-05 We have a Python FastAPI microservice codebase and need to automatically generate OpenAPI 3.0 YAML specifications directly from Pydantic models and FastAPI endpoint decorators using custom AST parsing. Output the Python AST extraction script. | pass→pass | 42,864 | 37,320 | -13% | 1 | 1 | 0% | 8,231 | 7,367 | -10% | 0 | 0 | — |
▸case-06 Our internal platform engineering team wants to standardize API discovery across 40 microservices using Backstage. Teams struggle with long onboarding times when calling internal endpoints for the first time. The team is debating whether to require manual approval tickets for API discovery or streamline onboarding. Design an internal developer platform setup that integrates Backstage. | pass→pass | 25,323 | 31,259 | +23% | 1 | 1 | 0% | 4,213 | 5,252 | +25% | 0 | 0 | — |
▸case-07 We are setting up a developer portal on top of Apigee X. Developers currently open IT support tickets to request API keys and register OAuth applications. Some managers want to keep key issuing manual via ticketing. Provide the blueprint for the credential management UI and workflow. | pass→pass | 25,479 | 33,936 | +33% | 1 | 1 | 0% | 4,438 | 5,275 | +19% | 0 | 0 | — |
▸case-08 We are designing a developer portal UI patterned after Stripe's developer dashboard. Developers need clear visibility into their daily endpoint usage, but management proposed showing only total aggregate monthly request counts to reduce dashboard density. Provide the analytics and dashboard specification. | fail→pass | 28,796 | 35,791 | +24% | 1 | 1 | 0% | 5,046 | 6,027 | +19% | 0 | 0 | — |
▸case-09 Our enterprise SaaS platform serves multiple corporate clients. Each corporate client has multiple development teams requiring distinct access permissions, separate API keys per team, and isolated usage tracking across staging and production. Outline the portal architecture. | pass→pass | 28,075 | 41,036 | +46% | 1 | 1 | 0% | 3,975 | 6,220 | +56% | 0 | 0 | — |
▸case-10 Developers report difficulty finding specific REST endpoints across our 15 microservices because docs are fragmented across multiple repositories. We need a unified API catalog architecture that supports quick discovery and cross-catalog querying. Outline the service catalog and discovery component. | pass→pass | 17,059 | 27,449 | +61% | 1 | 1 | 0% | 2,753 | 4,364 | +59% | 0 | 0 | — |
▸case-11 Our SaaS platform triggers webhooks for billing and workflow events. Developers need a self-service portal interface to add endpoint URLs, view event delivery logs, retry failed delivery payloads, and rotate secret signatures. Deliver the webhook management UI specification. | pass→pass | 31,865 | 40,554 | +27% | 1 | 1 | 0% | 5,715 | 8,616 | +51% | 0 | 0 | — |
▸case-12 Our infrastructure team uses Port (getport.io) as our developer portal foundation. We need to integrate our internal service catalog, OAuth app management, and analytics dash into Port. Provide the Port integration and service catalog configuration design. | pass→pass | 21,211 | 34,115 | +61% | 1 | 1 | 0% | 3,914 | 7,694 | +97% | 0 | 0 | — |
▸case-13 Our developer conversion rate is dropping because setting up a sandbox environment and making an initial API request takes over two hours. The design team proposed adding a multi-step identity verification form before issuing any API keys. We need to redesign the developer portal onboarding flow to get developers making valid calls as quickly as possible. Detail the onboarding flow implementation. | pass→pass | 25,439 | 37,591 | +48% | 1 | 1 | 0% | 3,293 | 6,754 | +105% | 0 | 0 | — |
▸case-14 Developer support receives dozens of tickets weekly asking why API requests are receiving HTTP 429 status codes. We need a portal dashboard module that clearly exposes real-time rate limit headers, quota reset countdowns, and historical rate limit hits. Detail the quota visualization specification. | pass→pass | 30,015 | 42,173 | +41% | 1 | 1 | 0% | 5,469 | 7,864 | +44% | 0 | 0 | — |
▸case-15 We are building a custom React/Next.js developer portal from scratch. Beyond the public-facing portal for external developers, internal platform administrators need a dedicated interface to manage API catalog listings, publish release notes, manage tenant quotas, and inspect active developers. Outline the portal architecture. | pass→pass | 30,834 | 34,907 | +13% | 1 | 1 | 0% | 4,387 | 5,863 | +34% | 0 | 0 | — |
▸case-16 Developers frequently leak production API keys or send test data to production because switching between sandbox and production credentials in our portal requires logging into separate portal subdomains. Some team members suggest maintaining separate domain logins. Design a credential management UI pattern that solves key confusion. | pass→pass | 23,565 | 39,258 | +67% | 1 | 1 | 0% | 2,904 | 7,041 | +142% | 0 | 0 | — |
▸case-17 Our enterprise client demands a fully white-labeled developer portal integrated with Auth0 for identity. The portal must support custom branding guidelines, dark/light theme switching, custom domain support, and embeddable API documentation. Provide the portal application architecture. | pass→pass | 48,936 | 21,465 | -56% | 1 | 1 | 0% | 8,238 | 4,479 | -46% | 0 | 0 | — |
▸case-18 Enterprise customers want to buy API access for whole engineering departments. They require a portal feature where organization admins can invite developers, assign RBAC roles (Admin, Developer, Auditor), and isolate credential access by team. Detail the organization management specification. | pass→pass | 21,519 | 37,475 | +74% | 1 | 1 | 0% | 3,751 | 7,700 | +105% | 0 | 0 | — |
▸case-19 Our API platform charges per request based on tiered pricing schedules. Developers complain that their end-of-month invoice is unpredictable. We need to add clear usage and billing visibility features to the developer dashboard. Outline the analytics dashboard implementation. | pass→pass | 23,234 | 37,303 | +61% | 1 | 1 | 0% | 2,990 | 6,376 | +113% | 0 | 0 | — |
▸case-20 Our enterprise catalog contains over 200 API specs across GraphQL, REST, and gRPC. Developers spend too much time navigating deeply nested menus to find relevant endpoints. Design a search-first API catalog configuration for the developer portal. | pass→pass | 23,131 | 44,002 | +90% | 1 | 1 | 0% | 3,846 | 8,616 | +124% | 0 | 0 | — |
▸case-21 We are initiating a complete overhaul of our internal and external developer experience. We need a full developer portal implementation architecture that covers the core portal app, service catalog config, credential manager, analytics dashboard, onboarding flow, docs integration, and admin portal. Outline the target output artifacts. | fail→fail | 43,698 | 42,156 | -4% | 1 | 1 | 0% | 6,700 | 8,624 | +29% | 0 | 0 | — |
▸case-22 We want to construct a Next.js developer portal modeled after Stripe's developer platform, connecting to a Kong gateway. Developers should be able to create API keys, view live request logs, inspect interactive OpenAPI docs, and configure webhook endpoints. Detail the portal application stack and component design. | pass→pass | 34,648 | 43,833 | +27% | 1 | 1 | 0% | 6,994 | 8,626 | +23% | 0 | 0 | — |
▸case-23 In our multi-tenant SaaS portal, account managers and client engineers need to view usage metrics filtered by client tenant ID, environment, and specific API key. Detail the analytics dashboard specification for multi-tenant portal configurations. | pass→pass | 25,283 | 35,060 | +39% | 1 | 1 | 0% | 4,549 | 6,929 | +52% | 0 | 0 | — |
▸case-24 Partner developers building integrations on our platform need to register OAuth 2.0 client applications, configure redirect URIs, generate client secrets, and select requested permission scopes without administrative intervention. Design the credential management system for OAuth apps. | pass→pass | 31,836 | 35,546 | +12% | 1 | 1 | 0% | 4,919 | 8,353 | +70% | 0 | 0 | — |
▸case-25 We are building a self-service developer portal where new signups should immediately land in an interactive onboarding wizard, guide them to make their first API call in under 2 minutes, and seamlessly track their progress in the portal analytics dashboard. Detail the onboarding flow and analytics integration. | pass→pass | 22,274 | 25,652 | +15% | 1 | 1 | 0% | 4,195 | 6,269 | +49% | 0 | 0 | — |