For coding agents

Coding agents use Nodus the way you do: the same account, projects, budgets and confirmations. Connect one over MCP, or point it at the machine-readable outputs below.

Read in this order

1. Read the compute decision guide to choose the feature that fits the request.
2. If this is a first run, read the quickstart.
3. Use the guide directory to find the relevant guide, then fetch its Markdown.
4. Look up exact commands in the CLI reference, signatures in the Python reference, or request fields in OpenAPI.

Fetch individual pages to keep context small. For example, /docs/guides/jobs/ has its Markdown at /docs/source/guides/jobs.md. Each docs page has a View Markdown link. Use the full corpus only for tasks that need many parts of the product.

Connect over MCP

Nodus runs one MCP server with generic tools over every resource (get, describe, logs, estimate, apply, exec and more). Writes return a dry run first and run only once confirmed.

Client type	Configuration
Hosted (Claude Code, Codex, Cursor and other HTTP clients)	Add the server URL from /mcp-hosted.json and sign in with your browser
Local stdio clients	Run nodus mcp; the configuration is /mcp.json

Step-by-step setup for each client is at /connect, and as Markdown at /connect.md.

Machine-readable outputs

Output	What it holds
/docs/pages.json	Lightweight page manifest: titles, summaries, status and source URLs
/docs/llms.txt	An index of these docs for language models
Start, compute, models, data, billing	Focused bundles with complete pages, examples and source URLs
/llms-full.txt	Guides and concepts in one Markdown file; use the index for exact references
/docs/source/<path>.md	Each page’s Markdown, linked from the page with rel="alternate"
/docs/index.json	Every page with its headings and text, versioned by build
/docs/openapi.json	The HTTP API contract
/skills/<name>/SKILL.md	Task instructions for agents that support skills
/install, /install.ps1	The CLI installer for macOS, Linux and Windows

A good first prompt for an agent that can read URLs:

Read https://nodus-compute.ai/connect.md and help me connect Nodus to this agent. Reuse any existing Nodus
connection. Verify setup by listing my jobs. Do not start paid compute.

Use the current contract

Fetch the relevant guide and its linked reference before writing commands. Keep the resource’s API version and Beta status explicit. Use the published OpenAPI schemas for field names and the CLI or SDK reference for the installed interface; do not invent flags from examples for another tool.

Each Markdown page includes its canonical source URL and build revision. Cite the source page when explaining behavior. Read billing and recovery limits before creating work, and verify the resource status, logs and outputs before reporting success. A submitted request is not evidence that the run completed.