🤖AI & LLM tools

Use Inqud documentation and API specs from any AI agent or chat client

Inqud publishes machine-readable resources so you can work with our docs and API from any AI agent or chat client.

Everything below is public. No API key, no VPN.

What's available

Resource	URL	Best for
MCP server	https://mcp.inqud.com/v1/mcp	AI agents and IDEs that support tool use (Claude Code, Cursor, Codex, Windsurf, etc).
llms.txt	https://docs.inqud.com/llms.txt	A short index of our docs (this website), formatted for LLMs.
llms-full.txt	https://docs.inqud.com/llms-full.txt	The full content of this website as one plain-text file.
OpenAPI spec	https://cdn.inqud.com/api/openapi.yml	Machine-readable API contract — for codegen or for handing schemas to an LLM.

Pick the right one

Building an integration with AI assistance in your editor → set up the MCP server once. The agent will look up endpoints and docs on demand.

Asking ChatGPT or Claude a one-off question about Inqud → paste the llms-full.txt URL into the chat.

Generating a typed API client or describing the API schema to a model → use the OpenAPI spec.

---

Plain-text exports

If your AI client doesn't speak MCP, you can still feed it Inqud's docs and API spec as plain text.

llms.txt — docs index

A compact, LLM-friendly index of every page in our documentation.

https://docs.inqud.com/llms.txt

Paste the URL into a chat and ask the model to use this index to find the right page. Good for short conversations where you want the model to navigate, not memorise.

llms-full.txt — full docs dump

The full content of every public doc page concatenated into one file.

https://docs.inqud.com/llms-full.txt

Paste into a chat for any longer integration session — the model gets the entire docs corpus in its context and can answer without follow-up fetches.

Both files are regenerated automatically whenever docs change.

OpenAPI spec

The machine-readable contract for the Inqud public API.

https://cdn.inqud.com/api/openapi.yml

Common uses:

• Generate a typed client — feed into openapi-generator, openapi-typescript, or any equivalent tool.

• Describe the API to an LLM — paste the URL or download and attach the file. Models handle OpenAPI 3.x natively.

• Diff against your integration — pin the spec in your repo and re-pull on releases to detect contract changes.

Example prompt

Here are Inqud's docs: https://docs.inqud.com/llms-full.txt And the API spec: https://cdn.inqud.com/api/openapi.yml

I want to charge a recurring subscription monthly. What endpoints do I call, in what order?

Most chat models will fetch both URLs and answer with concrete request examples.