x402basequality 0.62

Check any x402 server's health: latency, availability, protocol compliance, and payment endpoint validation.

Price
0.01 USDC / call
Protocol
x402
Verified
no

What it does

The `get_api_health` endpoint from x402-secure (by t54 Labs) performs a live health check against any x402-compatible server. You supply a target URL and the service probes it, returning response latency, payment amount, protocol compliance status, and validation details. This is useful for monitoring the uptime and correctness of x402 payment-gated APIs before routing agent traffic to them.

The endpoint itself is x402-gated at $0.01 USDC on the Base network (exact payment scheme). It accepts a POST request with a JSON body containing a single required field `url` — the x402 server you want to check. The response includes the server name, a status enum (success, failed, pending, no_data, error), detailed validation results (response time in ms, payment amount in USDC, result data, error messages), and a last-validated timestamp.

The service is part of the broader x402-secure platform, an open-source SDK and proxy that adds risk assessment and security layers on top of the x402 protocol. The platform supports both Base and Solana chains. No OpenAPI spec or dedicated docs page was found for this specific endpoint; the schema is derived entirely from the x402 challenge's `outputSchema` field.

Capabilities

x402-health-checkapi-monitoringlatency-measurementprotocol-compliance-validationpayment-endpoint-testingx402-protocolbase-network

Use cases

  • Monitoring the health and latency of x402-gated APIs before routing agent requests
  • Validating that a newly deployed x402 server correctly implements the payment protocol
  • Periodic availability checks on x402 endpoints to detect outages or degraded performance
  • Integration testing to confirm payment challenge responses are well-formed
  • Building dashboards that track x402 ecosystem service reliability

Fit

Best for

  • Agent developers who need to verify x402 server availability before making payments
  • Platform operators monitoring a fleet of x402-gated services
  • Integration pipelines that require pre-flight health checks on payment endpoints

Not for

  • General HTTP health checks on non-x402 APIs
  • Deep security auditing or penetration testing of payment infrastructure
  • Free-tier monitoring — every call costs $0.01 USDC

Quick start

curl -X POST https://x402-secure-api.t54.ai/x402/tools/get_api_health \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-encoded-payment-payload>" \
  -d '{"url": "https://mesh.heurist.xyz"}'

Example

Request

{
  "url": "https://mesh.heurist.xyz"
}

Response

{
  "url": "https://mesh.heurist.xyz",
  "status": "success",
  "server_name": "Heurist Mesh",
  "last_validated": "2025-01-15T12:34:56Z",
  "validation_details": {
    "result_data": {},
    "error_message": null,
    "response_time_ms": 342,
    "payment_amount_usdc": 0.01
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0x0495d60c927B97d67D5018C6AA65C9b2bebaeED9
CurrencyUSD COIN

Quality

0.62/ 1.00

The x402 challenge is live and includes a detailed outputSchema with input/output definitions, giving a clear picture of the endpoint's contract. However, there is no OpenAPI spec, no dedicated documentation page (all /docs, /api, /pricing, /README return 404), and no real response examples. The response JSON above is inferred from the outputSchema, not observed.

Warnings

  • No OpenAPI specification or dedicated API documentation found — /docs, /api, /pricing, /README all return 404.
  • Example response is inferred from the outputSchema, not from an actual observed response.
  • Pricing is only known from the x402 challenge description ($0.01 USDC); no formal pricing page exists.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 18:55:08Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access