cuopt-server-common

$npx mdskill add NVIDIA/skills/cuopt-server-common

Submit optimization problems and retrieve solutions via REST.

  • Handles routing, linear, and mixed integer programming requests.
  • Requires problem schemas and solver configurations for execution.
  • Returns request IDs for clients to poll solution status.
  • Delivers routes, objectives, and primal values on completion.

SKILL.md

.github/skills/cuopt-server-commonView on GitHub ↗
---
name: cuopt-server-common
version: "26.06.00"
description: cuOpt REST server — what it does and how requests flow. Domain concepts; no deploy or client code.
---

# cuOpt Server (common)

Domain concepts for the cuOpt REST server. No deploy commands or client code here.

## What the server does

- Accepts optimization requests (routing, LP, MILP) over HTTP.
- Returns a request ID; solution is obtained by polling with that ID.
- Does **not** support QP via REST.

## Problem types supported

| Problem type | Supported |
|--------------|:---------:|
| Routing      | ✓         |
| LP           | ✓         |
| MILP         | ✓         |
| QP           | ✗         |

## Request flow (conceptual)

1. Client sends problem data in the required schema (matrices, tasks, fleet, solver config).
2. Server returns a `reqId`.
3. Client polls the solution endpoint with `reqId` until the job completes.
4. Response contains status and, on success, solution (routes, objective, primal values, etc.).

## Required questions (deployment and usage)

Ask these if not already clear:

1. **Problem type** — Routing or LP/MILP? (QP not available.)
2. **Deployment** — Local, Docker, Kubernetes, or cloud?
3. **Client** — Which language or tool will call the API (e.g. Python, curl, another service)?

## Key endpoints (conceptual)

- Health check.
- Submit request (POST).
- Get solution by request ID (GET).
- OpenAPI spec (e.g. for payload format).

More from NVIDIA/skills

SkillDescription
accessing-mlflowQuery and browse evaluation results stored in MLflow. Use when the user wants to look up runs by invocation ID, compare metrics across models, fetch artifacts (configs, logs, results), or set up the MLflow MCP server. ALWAYS triggers on mentions of MLflow, experiment results, run comparison, invocation IDs in the context of results, or MLflow MCP setup.
ad-add-fusion-transformation>
ad-conf-check>
ad-graph-dump>
ad-model-onboard>
ad-pipeline-failure-pr>
add-benchmark>
aiq-deploy|
aiq-research|
byobCreate custom LLM evaluation benchmarks using the BYOB decorator framework. Use when the user wants to (1) create a new benchmark from a dataset, (2) pick or write a scorer, (3) compile and run a BYOB benchmark, (4) containerize a benchmark, or (5) use LLM-as-Judge evaluation. Triggers on mentions of BYOB, custom benchmark, bring your own benchmark, scorer, or benchmark compilation.