Documentation Index
Fetch the complete documentation index at: https://docs.vh3.ai/llms.txt
Use this file to discover all available pages before exploring further.
Agent Starter Kits
VH3 AI exposes the full intelligence layer — graph, semantic index, aggregation, sentinels, reports — through a standard API and an MCP surface. These starter kits give your AI tools the exact configuration they need to use that surface correctly from day one. Each kit is self-contained. Pick the one that matches how your team works.AGENTS.md
A drop-in context file for AI coding agents (Cursor, Claude Code, GitHub Copilot). Tells the agent which endpoint to call for which question, the correct field names, and the API conventions.
Cursor Rules
Three
.cursor/rules/ files that shape every VH3-related code generation in Cursor — domain vocabulary, API call patterns, and n8n workflow conventions.MCP Server
Connect any MCP-compatible client (Claude Desktop, Cursor, custom agents) directly to the VH3 intelligence layer. No middleware required.
Claude.ai Projects
Project instructions for Claude.ai — for operations managers who want to query VH3 in plain English without writing code.
n8n Agent Prompts
System prompt and HTTP Request Tool definitions for n8n AI Agent nodes. Wire up a VH3-fluent agent inside any n8n workflow.
Which kit should I use?
| Your situation | Recommended kit |
|---|---|
| You’re a developer using Cursor | AGENTS.md + Cursor Rules |
| You want to connect Claude Desktop or another MCP client | MCP Server |
| You’re building an AI-powered Claude.ai workspace for your ops team | Claude.ai Projects |
| You’re building automations in n8n with an LLM decision layer | n8n Agent Prompts |
| You want everything | Start with AGENTS.md, add MCP, then layer in the tool-specific kits |
What the kits don’t do
These kits configure AI tools to use the VH3 API correctly. They do not replace the API itself — you still need a validcompany_id and api_key to make calls. See Authentication for how to obtain those.
The kits reference endpoints from the API Reference. If an endpoint behaves unexpectedly, cross-check the spec there — the starter kits are tuned for the current API version.