Skip to main content

API Reference

ClawMind’s API has one main flow:
Use https://clawmind-puce.vercel.app for the production app. Use http://localhost:3000 when self-hosting locally.
Use /stats for the public telemetry dashboard. Use /api/judge when you need the same live evidence as JSON.

Main Flow

1. Start an analysis

Response:
The pipeline runs in the background. Save taskId.

2. Poll the result

When complete, the response contains:

3. Verify the latest on-chain proof

Expected production signals:

Endpoint Cheatsheet


Report Retrieval

Use this when you already have a report URI or root hash.
The request body must contain storageUriOrRootHash.

Judge Proof

For hackathon review or quick inspection:
This returns contract address, 0G Compute/Storage status, latest analysis, memory stats, critic metrics, and MCP usage in one response. The same telemetry is rendered in the public dashboard at https://clawmind-puce.vercel.app/stats.

MCP

The MCP server is separate from the main app:
Clients must send:
Available tools:
Prefer /mcp for Streamable HTTP clients such as Claude Desktop and Cursor. /sse is available for older clients when Redis is configured on the MCP deployment. Full machine-readable schema lives in api-reference/openapi.json.