documentation

Database

The ZAUTHX402 Database is a live registry of x402 protocol endpoints across the ecosystem. Our AI agents continuously discover, test, and monitor x402 endpoints, recording success rates, pricing, and response data. Query the database to find working endpoints before your agents pay.

Every endpoint in the database has been verified by our agents making real payments. We track which endpoints actually work, which are failing, and which have inconsistent behavior. This verification data helps agents make informed decisions about which services to use.

Database Explorer — x402 Endpoint Monitoring

Explore Database

Endpoint Tracking

Each endpoint in the database includes comprehensive metadata: the URL, HTTP method, network (Solana, Base, etc.), protocol name, and pricing information. We record the 402 Payment Required response headers that define how to pay for each endpoint, along with the actual request payloads and responses from successful calls.

Endpoints are automatically discovered when our agents encounter them during research tasks. Once discovered, we periodically retest endpoints to ensure the data stays current. Stale endpoints that stop responding are flagged, and their status updates in real-time as our agents continue testing.

Status Types

Every endpoint is assigned a status based on recent test results. This status helps you quickly assess reliability before integrating an endpoint into your workflow.

Working

Endpoint is responding correctly after payment. High success rate in recent tests.

Failing

Endpoint is returning errors or not responding. Recent tests have failed.

Flaky

Endpoint works sometimes but fails intermittently. Mixed success rate.

Over Budget

Endpoint price exceeds our testing budget. Not verified recently.

Verification

Endpoints in the database can be Verified or Unverified. Verified endpoints have been manually reviewed and tested through our verification platform by their providers. They include additional metadata like uptime percentages, test parameters, and guaranteed response formats.

Verified

Provider-verified endpoint with tracked uptime, test parameters, and LLM-validated responses.

Unverified

Discovered by our agents, tested automatically. May work but no provider guarantees.

Providers can verify their endpoints at /provider-hub. Verification includes domain ownership proof, endpoint testing with customizable parameters, and ongoing uptime monitoring.

x402 API

We offer two public API endpoints for agents and developers. The directory endpoint is free, while the health check endpoint requires payment via the x402 protocol.

GET/api/verification/directoryFREE

# Endpoint

GET https://back.zauthx402.com/api/verification/directory

# Query Parameters

category - Filter by category (AI, data, compute, etc.)

search - Search by URL or description

activeOnly - Only show active endpoints (default: true)

limit - Results per page (default: 50)

offset - Pagination offset

# Response

{
  "endpoints": [
    {
      "url": "https://api.example.com/v1/data",
      "method": "POST",
      "description": "AI inference endpoint",
      "category": "AI",
      "tags": ["llm", "inference"],
      "pricePerCall": 50,
      "priceCurrency": "USDC",
      "uptime": 99.5,
      "isActive": true,
      "lastVerifiedAt": "2026-01-12T..."
    }
  ],
  "total": 42,
  "limit": 50,
  "offset": 0
}

POST/api/verification/check$0.005 USDC

# Endpoint

POST https://back.zauthx402.com/api/verification/check

# Request Body

{
  "url": "https://api.example.com/v1/data"
}

# x402 Payment

This endpoint returns 402 Payment Required with payment options. Your agent must complete the payment and include the X-PAYMENT header with the payment proof to receive results.

# Timeout

Fresh tests may take up to 60 seconds as we make real x402 payments to verify the endpoint. Set your client timeout to at least 60-90 seconds. Cached results return instantly.

# Response Fields

url - The endpoint URL checked

verified - Always true (endpoint is in verified registry)

working - Whether the endpoint is currently working (null if unknown)

meaningful - Whether the response was validated as meaningful by LLM

llmReason - Explanation of the LLM validation result

responseTime - Response time in milliseconds

checkedAt - ISO timestamp of when the check was performed

checkedAgo - Human-readable time since last check

cached - Whether this result was served from cache

stale - (optional) True if returning historical data

staleReason - (optional) Why data is stale (e.g., "provider_insufficient_credits")

warning - (optional) Human-readable warning message

uptime - Historical uptime percentage

pricePerCall - Cost per call in minor units

priceCurrency - Currency (e.g., "USDC")

tags - Array of endpoint tags

description - Endpoint description

# Example Response

{
  "url": "https://api.example.com/v1/data",
  "verified": true,
  "working": true,
  "meaningful": true,
  "llmReason": "Response contains valid JSON with expected structure",
  "responseTime": 245,
  "checkedAt": "2026-01-12T...",
  "checkedAgo": "5m ago",
  "cached": true,
  "uptime": 98.5,
  "pricePerCall": 50,
  "priceCurrency": "USDC",
  "tags": ["blockchain", "data"],
  "description": "On-chain data API"
}

# Stale Response (provider out of credits)

{
  "url": "https://api.example.com/v1/data",
  "verified": true,
  "working": true,
  "stale": true,
  "staleReason": "provider_insufficient_credits",
  "warning": "Provider has insufficient credits...",
  "checkedAt": "2026-01-10T...",
  "checkedAgo": "2 days ago",
  "uptime": 98.5,
  ...
}

Accepted payments:

USDCon

Use this endpoint to verify that a provider's endpoint is working before committing to use it. Results are cached for up to 1 hour. When a provider has insufficient credits, you'll receive historical data with a stale: true flag instead of an error.

On this page