Integrate with an AI agent
Building your integration with an AI assistant or coding agent? Three ways to feed it accurate, current Invofox docs — a ready-to-paste prompt, the llms.txt docs index, or the MCP server — plus a copy-paste AI context briefing at the end for product-level grounding.
Option A · Copy a prompt
No setup required. Copy the prompt below and paste it into ChatGPT, Claude, Gemini or your coding agent. It turns the assistant into a guided Invofox onboarding — it asks you what it needs (API key, document type, how you want results) and walks you through the integration one step at a time.
Option B · Point it at llms.txt
Invofox publishes its documentation in the llms.txt format — a plain-text index built to be read by language models. Hand either URL to any assistant that can fetch a link and it pulls accurate, current docs with nothing to paste. No setup, and it never goes stale the way a hand-written prompt can.
Docs index — a curated map of the docs with links and short descriptions. Best when the agent can follow links.
Full docs — the entire documentation concatenated into one markdown file. Best when you want to drop everything into the model’s context at once.
Option C · MCP server
The Invofox MCP server exposes a searchDocs tool that lets any MCP-compatible agent query this documentation in real time. Works with Claude Code, Cursor, and any agent that supports the Model Context Protocol.
Claude Code:
Cursor, or manual setup — add to .mcp.json / .cursor/mcp.json:
AI context
The llms.txt index (Option B) and the MCP server (Option C) already give an assistant the full technical reference — endpoints, schemas, concepts, webhooks. What they don’t cover is the product-level picture: how accurate Invofox is, how it’s priced, and how it handles security. This briefing fills exactly that gap, so it complements the docs rather than duplicating them. Paste it as background context.