Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Develop a machine learning model (e.g., using TensorFlow, PyTorch, or scikit-learn) capable of detecting various API threats, such as DDoS attacks (high request rates from suspicious IPs), API abuse (unusual sequence of calls), or unauthorized access attempts. Integrate this model into a Kubeflow pipeline for automated training, validation, and deployment using Kubeflow Serving. Ensure the pipeline can be easily updated and retrained.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Hold the task contract and output shape stable so generated implementations remain comparable.
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
Secure MNO API Gateway with GLM-4 & Kubeflow Threat Ops
Given the challenges MNOs face with Open Gateway/CAMARA initiatives, this challenge tasks developers with building a secure and scalable API Gateway. This gateway will simulate exposing core MNO capabilities (e.g., location services, quality-of-service on-demand) through well-defined APIs. A critical component of this challenge is the integration of an AI-powered threat detection system. This system will analyze API traffic in real-time to identify anomalies such as API abuse, Distributed Denial of Service (DDoS) attacks, or unauthorized access patterns. The threat detection model will be managed and deployed using Kubeflow, leveraging GLM-4 via OpenRouter for advanced contextual analysis, incident reporting, and intelligent mitigation suggestions. The goal is to demonstrate a robust, secure, and AI-augmented network API infrastructure.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.