API docs

Quickstart: your first /v1/check call

One endpoint, one query parameter. Ask for a verdict on any absolute https URL an agent is about to pay or depend on.

# 1. Ask without payment. You get the price quote back as HTTP 402.
curl -i "https://api.agenticresourceradar.com/v1/check?resource=https://api.example.com/v1/data"

# The 402 response carries the payment requirements twice:
#   - JSON body: { "x402Version": ..., "accepts": [ { "maxAmountRequired": ..., "payTo": ..., "asset": ..., ... } ] }
#   - PAYMENT-REQUIRED header: the same payload, base64-encoded

# 2. Pay accepts[0] with any x402 client (USDC on Base) and retry with X-PAYMENT.
curl -s "https://api.agenticresourceradar.com/v1/check?resource=https://api.example.com/v1/data" \
  -H "X-PAYMENT: <base64 x402 payment payload from your client>"

# 3. The paid 200 is the graded verdict:
# { "decision": "allow" | "warn" | "block" | "unknown", "liveness": ..., "drift": ..., ... }

Most x402 client libraries wrap steps 1 and 2 in a single fetch. The payment requirements in the 402 are also published ahead of time at https://api.agenticresourceradar.com/discovery/resources, so a client can pay without the extra round-trip.

Authentication: there are no API keys

Payment is the authentication. Every paid request is authorized by the x402 payment attached to it, so there is nothing to register, store, rotate, or leak. The full flow:

• Send the GET request with no payment. The API answers 402 Payment Required.
• Read the payment requirements from the JSON body (accepts[0]) or the base64 PAYMENT-REQUIRED header: amount (maxAmountRequired, atomic USDC), payTo address, asset, and network.
• Sign the payment with your x402 client and retry the same request with the X-PAYMENT header.
• The API verifies and settles the payment through the x402 facilitator and answers 200 with the data. Settlement proof comes back in the response headers.

Paid endpoints

• GET https://api.agenticresourceradar.com/v1/check?resource=<absolute-https-url>: full graded verdict (eval and index data, $0.035 per call). Decision plus liveness, freshness, price, payTo, and chain drift, and monitoring history.
• GET https://api.agenticresourceradar.com/v1/trade-check?resource=<absolute-https-url>: compact pre-payment facts, no score (basic telemetry data, $0.01 per call). Latency-optimized for agents mid-flow.

Pricing details and the enterprise offer: /pricing.

Free machine surfaces

• https://agenticresourceradar.com/openapi.json (also at https://api.agenticresourceradar.com/openapi.json): the OpenAPI contract; paid operations carry x-payment-info with their price.
• https://api.agenticresourceradar.com/discovery/resources: x402 discovery list of payable resources with full payment requirements.
• https://api.agenticresourceradar.com/.well-known/x402: service-level x402 discovery metadata.
• https://agenticresourceradar.com/index/search.json: the current published Agentic Search Index release as JSON.
• https://agenticresourceradar.com/ai-catalog.json: machine-readable operation catalog.
• https://agenticresourceradar.com/llms.txt: the agent-facing guide to this site.

MCP server

A dependency-light stdio MCP server ships with the product. Tools: verify_x402_trade (pre-payment check of an x402 endpoint through /v1/trade-check), check_x402_endpoint (full graded verdict through /v1/check), and fetch_search_index (the Agentic Search Index rankings). Machine descriptor: https://api.agenticresourceradar.com/trading/mcp.json. A Streamable HTTP transport is planned post-launch.