Jiddu API & MCP

Use Jiddu's four reading tools from your own code or agent — a documented REST API and an MCP server.

Endpoints

Jiddu exposes its four analysis pipelines as a public REST API. Every endpoint takes a JSON body with a text field (40–2000 characters) plus an optional lang (en / pt / es), and returns structured JSON.

POST /api/v1/detect-fallacies
POST /api/v1/fact-check
POST /api/v1/assess-neutrality
POST /api/v1/explain

detect-fallacies, assess-neutrality and explain are fast. fact-check extracts each claim and verifies it against live web search, so it is slower and metered.

Authentication

Send your API key in the X-Jiddu-Key header. Keys are issued by the operator — see “Getting a key” below.

curl -X POST https://jiddu.app/api/v1/detect-fallacies \
  -H "content-type: application/json" \
  -H "X-Jiddu-Key: YOUR_KEY" \
  -d '{"text": "Everyone agrees this is best, so critics must be fools."}'

MCP server

For agents, connect to the hosted Jiddu MCP server by URL — nothing to install or clone. It exposes the same four tools and bridges to your MCP client (e.g. Claude Desktop) via the public mcp-remote helper:

{
  "mcpServers": {
    "jiddu": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://jiddu.app/api/mcp", "--header", "X-Jiddu-Key:your-key-here"]
    }
  }
}

Machine-oriented docs — when to use each tool, response shapes, and how to chain them — live in AGENT.md.

Limits & reliability

Text is capped at 2000 characters per request. Rate limits are per key; exceeding them returns HTTP 429 with a retry_after_seconds field. Outputs are automated and can be wrong — treat them as signals to prompt verification, not as final authority.

Quality is measured against fixed test sets published in the repo: evals/report.md.

Getting a key

Keys are issued manually for now. Open an issue on GitHub to request one.