# Vibes-Coded Merchant Smoke Test Endpoint

> Vibes-Coded Merchant Smoke Test Endpoint is a paid API for AI agents from vibes-coded.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-13).

Validates that a merchant endpoint is reachable and correctly configured for x402 pay-per-call (HTTP 402 / USDC) payment flows, returning status, dual-rail support, and reachability signals.

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/merchant-smoke?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-merchant-smoke-test-endpoint-5c4e24a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RnN_d5SwsmyYdP0WiDicI

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 vibes-coded-merchant-smoke-test-endpoint-5c4e24a9 -d '<json body>'
```

Example prompt: Can you run a smoke test on my merchant endpoint to check if it's properly set up for x402 pay-per-call — I want to confirm it returns a 402 status, is reachable, and has dual-rail payment support enabled?

## When to prefer this

Use this endpoint when you need to quickly validate that a merchant API is correctly configured for x402 pay-per-call micropayments before listing, debugging, or integrating it. It is the right choice over general HTTP health checks when you specifically need to confirm 402 response behavior, USDC payment acceptance, dual-rail support, and reachability in a single call.

## Known failure modes

- Endpoint unreachable — returns reachable: false with summary indicating connection failure
- Endpoint does not return HTTP 402 — status field reflects actual code, ok may be false
- Dual-rail not configured — dual_rail: false in response
- Payment method misconfiguration — accepts count is 0 or unexpected in summary
- Malformed merchant configuration — error or unexpected JSON structure returned

## How this service works

Pay-per-call JSON for AI agents: skill search, listing optimization, install plans, productization, and artifact risk scoring. HTTP 402 → USDC. Full skill marketplace on-site.

## Output

Returns a JSON object with: ok (boolean), status (HTTP status code, expected 402), summary (human-readable string describing status, accepted payment methods count, and dual-rail mode), dual_rail (boolean indicating dual-rail payment support), and reachable (boolean indicating endpoint availability).

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "status": 402,
  "summary": "status=402, accepts=2, dual_rail",
  "dual_rail": true,
  "reachable": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-merchant-smoke-test-endpoint-5c4e24a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vibes-coded.com](https://www.zero.xyz/host/vibes-coded.com/llms.txt)