# KEVAREMESH x402 Client Test (CDP) Endpoint

> KEVAREMESH x402 Client Test (CDP) Endpoint is a paid API for AI agents from kevaremesh-web.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-28).

Executes a paid end-to-end diagnostic ping via the x402 payment protocol, echoing the input message and confirming the x402 payment flow is working correctly.

## Facts

- Endpoint: POST https://kevaremesh-web.vercel.app/api/x402/x402-client-test-cdp-x402-client-test?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kevaremesh-x402-client-test-cdp-endpoint-22ae5dee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dkUFt2gpb9OfTWWBUC2pl

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 kevaremesh-x402-client-test-cdp-endpoint-22ae5dee -d '<json body>'
```

Example prompt: Send a test message 'hello' to the KEVAREMESH x402 client test endpoint so I can confirm my x402 payment flow is working end to end.

## When to prefer this

Use this endpoint when you need to verify that your x402 payment client (especially CDP-based) is correctly configured and able to complete a real micropayment cycle. It is the lowest-cost, lowest-risk way to confirm end-to-end x402 connectivity before invoking more expensive or consequential paid endpoints. Prefer this over production endpoints for initial integration testing and ongoing health checks.

## Known failure modes

- Payment not received or insufficient USDC balance — x402 gateway rejects request before processing
- Malformed message exceeding 500 characters — input validation error
- Network or Vercel cold-start timeout — no response or 5xx error
- Invalid x402 payment header — gateway returns 402 without processing
- Message field missing — may return error or empty echo depending on implementation

## How this service works

Buyer-first MCP procurement gateway that discovers, compares and routes live x402 APIs without making the buyer choose a provider.

## Output

Returns a JSON object confirming the echo of your input message, a boolean ok flag, the endpoint purpose label ('end_to_end_x402_client_test'), the UTC server time at execution, a paid_x402_endpoint flag, the product name, service name, tool name, a limitations array noting no external action is taken, and a generated_at timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "message": {
   "type": "string",
   "maxLength": 500
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "ok": true,
   "echo": "hello",
   "purpose": "end_to_end_x402_client_test",
   "server_time_utc": "2026-09-20T09:00:00.000Z",
   "paid_x402_endpoint": true
  },
  "product": "kevaremesh_x402_client_test_cdp_x402_client_test_v2",
  "service": "KEVAREMESH",
  "tool_name": "kevaremesh_x402_ping",
  "limitations": [
   "Diagnostic paid endpoint; no external action"
  ],
  "generated_at": "2026-09-18T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kevaremesh-x402-client-test-cdp-endpoint-22ae5dee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kevaremesh-web.vercel.app](https://www.zero.xyz/host/kevaremesh-web.vercel.app/llms.txt)