cuopt-server-common

Configure and operate a cuOpt REST server for optimization requests.

2.8k|332|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill cuopt-server-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cuopt-server-common
Source: https://github.com/NVIDIA/skills/tree/main/skills/cuopt/cuopt-server-common
Command: npx skills add https://github.com/NVIDIA/skills --skill cuopt-server-common

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines optimization workloads by exposing a REST interface for cuOpt that accepts problems and returns a request ID for asynchronous solution retrieval.

Core Features & Use Cases

  • Supports routing, LP, and MILP workloads via HTTP for scalable logistics and operations planning tasks.
  • Defines a straightforward request flow from submission to solution retrieval, including status checks.
  • Provides domain concepts and endpoints without client deployments or example code to keep integration lightweight.

Quick Start

Start the cuOpt REST server locally and submit a problem via the REST API to receive a request ID and subsequently fetch the solution.

Frequently Asked Questions about cuopt-server-common

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run routing and MILP optimization workloads over HTTP?

You can run routing and MILP optimization workloads over HTTP by configuring a cuOpt REST server. It accepts optimization problems via a submit endpoint and returns a request ID for asynchronous processing.

What is the request flow for retrieving a routing optimization solution from a REST server?

The routing optimization retrieval flow uses a submit endpoint to return a request ID, a health check endpoint for status, and a solution retrieval endpoint to fetch results asynchronously.

Can I use a REST API to solve logistics LP problems asynchronously?

Yes, you can solve logistics LP problems asynchronously by sending an HTTP request to the cuOpt REST server's submit endpoint to generate a request ID and fetch the solution later.

Does the cuOpt REST server require client-side deployment code to handle operations research tasks?

No, the cuOpt REST server defines domain concepts and endpoints without requiring client deployments or example code, keeping operations research integration lightweight and straightforward.

What is the best way to check server health before submitting operations research problems?

The best way to check server health before submitting operations research problems is to use the provided health check endpoint to verify the cuOpt REST server is active and ready.

What limitations exist when using a REST server for logistics optimization request handling?

A limitation of this logistics optimization REST server is that it returns a request ID for asynchronous solution retrieval rather than providing immediate synchronous results for submitted problems.