# ContextIQ Agent Protocol Inspector

> ContextIQ Agent Protocol Inspector is a paid API for AI agents from contextiq.trango-compute.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Scans a target URL or domain for agentic protocol support (MCP, A2A, ARD) and llms.txt presence, returning detection results with evidence per protocol.

## Facts

- Endpoint: POST https://contextiq.trango-compute.com/api/v1/agent-protocol-inspector/x402-v2
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/contextiq-agent-protocol-inspector-064f7eb6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9yt_PpcDDpyMnD1RjLUQE

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability contextiq-agent-protocol-inspector-064f7eb6 -d '<json body>'
```

Example prompt: Scan https://api.example.com to check whether it supports MCP, A2A, or ARD agent protocols and whether it has an llms.txt file — I want to know which agentic protocols are confirmed, indicated, or not detected there.

## When to prefer this

Use this endpoint when you need to programmatically discover which agentic interoperability protocols (MCP, A2A, ARD) a remote service exposes, rather than manually inspecting headers or well-known paths. Prefer it over generic HTTP scanners because it has purpose-built detection logic for agentic standards including evidence collection and distinction between confirmed vs indicated presence.

## Known failure modes

- Target URL unreachable — connection timeout or DNS failure
- No agentic protocols detected at any endpoint (detectedCount: 0)
- Protocol indicated but insufficient evidence to confirm
- llms.txt not found (returns not_detected status)
- Malformed or missing origin/target fields cause validation errors

## How this service works

Agent Protocol Inspector scan (MCP / A2A / ARD / llms.txt) — per call

## Output

Returns a structured object indicating whether MCP, A2A, and ARD protocols are confirmed, indicated, or not detected at the target, along with supporting evidence, details per protocol, and whether an llms.txt file was found (including its URL). Also includes the total count of detected protocols.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "origin": {
   "type": "string"
  },
  "target": {
   "type": "string"
  },
  "llmsTxt": {
   "type": "object",
   "description": "Whether an llms.txt file was found, and its URL"
  },
  "protocols": {
   "type": "object",
   "description": "mcp, a2a, and ard detection results, each with status (confirmed/indicated/not_detected), evidence, and details"
  },
  "detectedCount": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/contextiq-agent-protocol-inspector-064f7eb6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from contextiq.trango-compute.com](https://www.zero.xyz/host/contextiq.trango-compute.com/llms.txt)