mcpField
C
cuopt-server-common

cuopt-server-common

github.com/nvidiaData & databases3.8k1.3k installsUpdated today
Repository

About cuopt-server-common

cuOpt Server の REST API concepts and workflow を説明する Agent Skill です。cuOpt の最適化 API を利用する際の問題種別、デプロイ方式、リクエストとポーリングの流れを整理します。

Key features

  1. 01REST API の概念整理
  2. 02Routing、LP、MILP の対応範囲
  3. 03reqId による結果ポーリング
  4. 04主要エンドポイントの案内

Use cases

  1. 01cuOpt REST リクエストの設計
  2. 02最適化 API の利用条件確認

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nvidia/skills --skill cuopt-server-common

After installing, type/cuopt-server-commonin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

BENCHMARK.md
skill-card.md
skill.oms.sig
evals/
evals.json

Details

From the project README

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 typeSupported
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).

Comments

Markdown supported