// verification.md

> Endpoint Verification

// How EntRoute verifies and monitors endpoint quality.

// overview

Every endpoint in EntRoute is automatically verified using 402 probes. Probes check that endpoints return proper 402 Payment Required responses with valid x402 payment headers. This ensures agents only discover working, payment-ready endpoints.

// probe process
1.
Initial Probe

When an endpoint is submitted or ingested, it's queued for an initial verification probe.

2.
402 Verification

The probe sends a request without payment and checks for a valid 402 response with proper X-Payment-* headers.

3.
Status Update

Endpoints that pass are marked verified. Failed endpoints remain unverified and are retried on the next cycle.

4.
Continuous Monitoring

Verified endpoints are re-probed every 15 minutes. Repeated failures result in demotion from discovery results.

// probe checks

Each probe validates:

+ HTTP 402 status code returned for unpaid requests
+ Valid X-Payment-Network header present
+ Valid X-Payment-Asset header (USDC)
+ Valid X-Payment-Amount (numeric, reasonable range)
+ Valid X-Payment-Address (valid wallet address)
+ Response latency within acceptable range
// observed metrics

Probe results feed into the ranking system. These metrics are exposed in discovery responses:

Metric Description
success_rate_7d Percentage of successful probes in the last 7 days
p95_latency_ms 95th percentile response time in milliseconds
last_verified_at Timestamp of the most recent successful probe
// endpoint statuses
verified

Passed 402 probe. Appears in discovery results.

unverified

Submitted but not yet probed, or probe pending.

failed

Repeatedly failed probes. Hidden from discovery results until resolved.

x402 Protocol Back to Docs