Jiddu API & MCP

Machine-readable contracts

Start with the Jiddu OpenAPI description for the complete REST request and response schemas, unique operation IDs, authentication, limits, and error contracts. MCP clients can discover the hosted server through the AI catalog, which points to the canonical server card. The MCP Registry manifest and OAuth protected-resource metadata provide registry and authorization discovery.

Use Jiddu when an agent needs to inspect reasoning, verify factual claims, assess framing, explain dense prose, detect templated writing patterns, or review one complete academic PDF. Do not use an automated verdict as a substitute for reading the source and cited evidence.

Endpoints

Jiddu exposes its five analysis pipelines as a public REST API. Every endpoint takes a JSON body with a text field (40–2000 characters; up to 10000 for fact-check) 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
POST /api/v1/detect-slop

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

Adversarial paper review

Adversarial review uses a persisted asynchronous job contract. Start with multipart POST /api/v1/adversarial-reviews and one file, or JSON with a public pdf_url. Choose depth=standard for the economical pipeline or depth=deep for stronger reasoning and critic models. The 202 response returns an id, a status URL and retry_after_seconds; poll GET /api/v1/adversarial-reviews/{id} until status is complete or failed.

curl -X POST https://jiddu.app/api/v1/adversarial-reviews \
  -H "X-Jiddu-Key: YOUR_KEY" \
  -F "file=@paper.pdf" \
  -F "lang=en" \
  -F "depth=deep" \
  -F "venue_profile_id=neurips-2026-main"

curl -H "X-Jiddu-Key: YOUR_KEY" \
  https://jiddu.app/api/v1/adversarial-reviews/JOB_ID

A completed job returns the structured review, a public methodology audit and source-verification metadata, plus links to its viewer, deterministic Markdown, and print/PDF view. Optional fields are lang, depth, venue_profile_id, venue, venue_year, venue_track, paper_type, and review_date. PDFs are capped at 25 MB and 300,000 extracted characters.

REST API authentication

The REST API is separate from MCP OAuth. Send its API key in the X-Jiddu-Key header. Every key belongs to one verified WorkOS account and follows that account's funding: included platform access or Jiddu Credits. Generate and manage your keys from your account.

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 directly to https://jiddu.app/api/mcp. The server exposes the five text tools plus start_adversarial_review and get_adversarial_review. Compatible MCP clients discover WorkOS AuthKit, open Jiddu sign-in and receive a resource-scoped OAuth token automatically. Accounts on the platform allowlist receive included access; every other tool call reserves and spends Jiddu Credits from the signed-in account.

Clients that still require a local stdio bridge can use mcp-remote without a custom authentication header; it handles the OAuth redirect: `` { "mcpServers": { "jiddu": { "command": "npx", "args": ["-y", "mcp-remote", "https://jiddu.app/api/mcp"] } } } ``

Machine-oriented setup guidance, response contracts and chaining examples are included on this page.

Limits & reliability

Text tools are capped at 2000 characters per request, except fact-check, which accepts up to 10000. Successful and failed runs appear in the authenticated account's analysis history. Review jobs accept one public or uploaded PDF up to 25 MB and reject papers above 300,000 extracted characters rather than truncating them. REST rate limits are per API key; hosted MCP limits are per WorkOS user. 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 internal test sets and the benchmark summaries published on this site.

Create a REST API key

Sign in, open API keys in your account, choose a descriptive label and select “Generate API key.” Copy the secret immediately: it is shown only once, and Jiddu stores only its sha256 hash. You can revoke the key from the same page at any time.