AI Agents

This page is the entry point for AI agents (Claude, ChatGPT, Cursor, in-house copilots, …) integrating with Lium. Everything else in the Developers section also applies to agents — this page just stitches the pieces together.

Get started in 5 min

1. Add the docs MCP server (search and read pages over JSON-RPC):

   {
     "mcpServers": {
       "lium-docs": { "url": "https://docs.lium.io/mcp" }
     }
   }
2. Or pull the full markdown bundle for in-context grounding:

   curl -sSL https://docs.lium.io/llms-full.txt
3. Discover every API endpoint from the live OpenAPI 3.1 spec:

   curl -sSL https://lium.io/api/openapi.json
4. Drive the platform from a shell with the CLI:

   curl -fsSL https://lium.io/install.sh | bash && lium init

Pick the right surface

Goal	Use this	Why
Answer questions about Lium docs	MCP endpoint — https://docs.lium.io/mcp	Targeted search + page reads, no token bloat
Ground a long conversation in the full docs	llms.txt / llms-full.txt	One fetch, every page concatenated
Read a single page as raw markdown	Append .md to any URL — e.g. /providers/quickstart.md	No HTML to parse
Call the Lium platform programmatically	OpenAPI spec — https://lium.io/api/openapi.json	Source of truth for every REST endpoint
Drive pods from a shell agent	CLI	Stable subcommands, JSON output, no auth headers to manage
Automate the provider portal (Subnet 51)	lium provider	Same surface as lium.io/portal: node lifecycle, central-miner-server config, sync, billing, machine requests — all --json-able
Write code against typed Python clients	SDK	lium.machine decorator + Lium() client

Stable agent-facing URLs

These URLs are stable and safe to hard-code in agent configurations:

https://docs.lium.io/mcp                  # docs MCP JSON-RPC endpoint
https://docs.lium.io/llms.txt             # docs index + summaries
https://docs.lium.io/llms-full.txt        # all docs concatenated
https://docs.lium.io/<any-page>.md        # raw markdown for any page
https://lium.io/api/openapi.json          # live platform OpenAPI 3.1 spec
https://lium.io/documents                 # Swagger UI for the same spec

Authentication

The platform API and CLI authenticate with an API key from Settings → API Keys at lium.io. Send it in the X-API-Key header on every request. The docs surfaces (MCP, llms.txt, .md URLs) require no auth.

export LIUM_API_KEY=your_api_key_here
curl https://lium.io/api/pods -H "X-API-Key: $LIUM_API_KEY"

Recommended agent loop

1. Bootstrap context from MCP search (or feed llms-full.txt once).
2. Resolve the right endpoint from the OpenAPI spec.
3. Call the API with the user's bearer token.
4. Fall back to the CLI when the workflow is shell-shaped (file uploads, SSH).

Related

• MCP endpoint — JSON-RPC contract and tool definitions
• llms.txt — llmstxt.org-format docs bundle
• OpenAPI spec — code-gen and tool-use examples
• CLI overview — full command surface
• SDK — typed Python client