Documentation

Give your agent a trust layer

EVIDIQ verifies an agent's capability, scores its risk, checks its on-chain reputation, and returns a signed Trust Report — anchored on 0G and analyzed in a TEE — before you transact. Connect it in one line.

Quickstart

Connect the EVIDIQ MCP server to any MCP-capable agent (Claude Code, Cursor, custom):

claude mcp add --transport http evidiq https://evidiq.dev/mcp

Or drop the open skill straight into your agent:

curl -s https://evidiq.dev/skill.md

MCP server

The remote MCP endpoint is https://evidiq.dev/mcp (Streamable HTTP). It exposes three tools:

• how_to_install — onboarding instructions (free)
• get_evidiq_skill — the latest skill in open-skill format (free)
• verify_agent — the core trust check (x402-paid)

{
  "mcpServers": {
    "evidiq": { "url": "https://evidiq.dev/mcp" }
  }
}

verify_agent

Pass everything you know about the counterparty. The more anchors you supply, the sharper the verdict.

{
  "agentId": "weather-oracle",
  "endpoint": "https://agent.example/mcp",
  "declaredCapabilities": ["weather-data", "price-feed"],
  "framework": "LangChain",
  "identity": {
    "address": "0x…",
    "erc8004Id": "42",
    "domain": "example.com"
  },
  "context": "pay-per-call weather API, $2 / 1k calls"
}

It returns a Trust Report: a score (0–100), a tier, a per-dimension breakdown (identity, capability, reputation, risk), an explicit recommendation (proceed, proceed_with_escrow, caution, do_not_proceed), a TEE-verified AI analysis, and an attestation.

x402 pay-per-call

verify_agent is metered with x402 (scheme exact, EIP-3009 on X Layer). Unpaid calls receive an HTTP 402 challenge; sign it and retry with a PAYMENT-SIGNATURE header (the OKX Payment SDK / OnchainOS does this automatically). Pricing discovery lives at /x402.

curl -s https://evidiq.dev/x402

Attestation & 0G

Every paid report ships an attestation you can independently verify:

• reportHash — keccak256 of the canonical report.
• 0G Storage root + tx — the full evidence anchored on 0G mainnet (audit trail).
• 0G TEE — the risk analysis runs on 0G Compute (GLM-5.2) in a TEE; the provider address + request id are recorded.
• signature — the verdict is signed (EIP-191) by the EVIDIQ key so anyone can recover the attester.