> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aient.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Aient docs from AI assistants and coding agents

> Point Cursor, Claude Code, and other AI tools at Aient docs through generated Markdown, llms.txt, and skill.md so agents instrument apps from the same source.

# AI tools

Mintlify exposes documentation content as Markdown for agents, hosts `llms.txt`, and can publish a `skill.md` capability file. Use those generated surfaces so AI tools answer from the same docs users read.

## Recommended use

* Point coding agents at this docs site before instrumenting an app.
* Use the webhook event pages as schema context for consumer implementations.
* Prefer the SDK quickstarts over raw OTLP setup unless you need a custom OpenTelemetry pipeline.
* Use the [Aient CLI](./ai-tools/cli) to run a local workspace in an isolated Aient sandbox.
* Use [Agentic x402 onboarding](./agentic-x402) when an autonomous agent needs to discover Aient, pay with x402, and request remediation through wallet-backed routes.
* Use [Agent-assisted setup](./agent-commerce) when an assistant helps prepare setup for a human or team.

## Discover the MCP server

Aient's hosted MCP server is listed in the official MCP Registry as `ai.aient/mcp` and is reachable at `https://aient.ai/mcp`.

Use registry metadata when your assistant supports registry-based installation. Otherwise, configure the remote MCP URL directly. Request read scope for context lookup, and request write scope only when the assistant needs to report onboarding progress, retry setup steps, or control remediation workflows.

## Reopen a resolved problem

If new production evidence changes the conclusion for a resolved problem, an assistant with MCP write scope can call `reopen_problem`. Include a fresh request ID and a short reason grounded in that evidence. Then re-read it with `get_problem` before making a separate remediation request.

Reopening keeps the existing evidence and remediation history intact. It is for a new conclusion, not for undoing an accidental manual resolution. `reopen_problem` is available through the OAuth MCP server, not the wallet-backed `/mcp-x402` endpoint.