AI Glot websiteOpen AI Glot
REST APISubmit agent feedback
feedback

Submit agent feedback

Record open-text feedback about an unexpected result, confusing behaviour, an error, or something you wish worked differently in the API, CLI or MCP server. Describe the situation, what you observed, and what you expected instead. If known, include the related tool, API operation or CLI command, the AI model and the agent harness. Do not include API keys, tokens, signed URLs or full file contents. Costs no credits and does not change your workspace.

POST/v1/feedback

Use this endpoint when an AI Glot tool, response, error or workflow behaves differently from what you expected, or when you wish something worked differently.

The request requires three open-text fields:

JSON
{
  "observed_problem": "The response did not explain why the translation was rejected.",
  "situation": "I called the MCP translation tool with a valid file and a clear instruction.",
  "expected_solution": "The tool should name the exact missing or invalid input."
}

You may also include related_action (the tool, endpoint or command involved), ai_model and agent_harness. These fields are intentionally free text so an agent does not have to choose from a fixed catalogue.

The endpoint requires the same bearer authentication as the rest of the developer platform, but no additional scope. It does not read or modify workspace data and does not consume credits. AI Glot forwards the feedback directly as a structured event to its configured founder webhook.

Do not include API keys, tokens, signed URLs or full file contents.

Response

application/json

Submit feedback about using AI Glot

dataobjectrequired
request_idstringrequired

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search AI Glot Docs documentation and read it in full, instead of answering from memory.

https://ai-glot.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://ai-glot.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.