# LiveGraph — agent access

Preferred interface: MCP on the API host, one server per published graph.
This website (https://www.livegraph.ai) does not speak MCP.

## Machine interfaces

- Workspace MCP server (control plane for the whole workspace — graphs and runs):
  POST https://api.livegraph.ai/mcp — JSON-RPC 2.0, one POST per request, no SSE.
  Alias: POST https://api.livegraph.ai/.well-known/mcp. X-Api-Key required (no anonymous tier);
  scoped keys keep their graph/action limits inside each tool call.
  Methods: initialize, tools/list, tools/call.
  Tools: list_graphs, get_graph, start_run, get_run, pause_run, resume_run,
  cancel_run, share_run, search_runs, draft_node, create_graph, update_graph_nodes,
  get_canvas_url, get_started, list_templates, instantiate_template,
  provision_credential.
- MCP (per published graph — runs that graph as a tool): POST https://api.livegraph.ai/mcp/serve/{slug}
  Methods: initialize, tools/list, tools/call, resources/read.
  tools/list advertises exactly one tool, run_<graph-name>.
- A request to https://www.livegraph.ai/.well-known/mcp or https://www.livegraph.ai/api/mcp is not either server. It answers with the URLs above.
- OpenAPI 3.1 for the public API: https://www.livegraph.ai/api/openapi.json
  Aliases: https://www.livegraph.ai/.well-known/openapi.json, https://www.livegraph.ai/openapi.json
  The spec's server url is https://api.livegraph.ai.
- Agent card: https://www.livegraph.ai/.well-known/agent-card.json
  https://www.livegraph.ai/.well-known/agent.json redirects there (308).
- MCP server card: https://www.livegraph.ai/.well-known/mcp/server-card.json
- Longer guide: https://www.livegraph.ai/agents.md
- llms.txt: https://www.livegraph.ai/llms.txt
- RSS feed: https://www.livegraph.ai/feed.xml
- Human docs: https://www.livegraph.ai/docs
- This file: https://www.livegraph.ai/agents.txt

## Auth

- Member calls send `X-Api-Key: lgk_…`. The key acts as its owner.
  A member key needs at least viewer on the served graph.
- Public slugs (the owner opted in) take no key. Their output is untrusted
  third-party content. Caps: 20 launches/day per client IP, 50/day and
  12/hour per graph, and $2/day of metered spend per graph.
- Mint a key at https://www.livegraph.ai/settings (shown once).
- REST runs: POST https://api.livegraph.ai/runs with {"graphId","input"}. mode defaults to pinned.

## House rules

- Use the API host above. Do not scrape the app shell for run output.
- https://www.livegraph.ai/mcp is the human page about MCP, not an endpoint.