# Vibes-Coded Merchant Legit Gate

> Vibes-Coded Merchant Legit Gate is a paid API for AI agents from vibes-coded.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-14).

Scores and validates whether a merchant/API endpoint is safe and legitimate for an AI agent to pay via USDC before executing a transaction

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/merchant-legit-gate?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-merchant-legit-gate-4475b2af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cHqao3iezpM3uQh8YMJqg

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-legit-gate-4475b2af -d '<json body>'
```

Example prompt: Before my agent pays this merchant endpoint, run a legit-gate check on it — I want to confirm it's safe to pay, the budget is within limits, and it passes the dual-rail check before we send any USDC.

## When to prefer this

Use this endpoint when an AI agent is about to execute a USDC micropayment to an unknown or newly discovered x402 merchant and needs a pre-payment safety gate. Prefer it over manual review when operating autonomously in the Vibes-Coded marketplace or any x402-compatible ecosystem. It is particularly valuable when agents need automated, programmatic trust scoring before committing funds, especially in zero-trust or high-frequency payment workflows.

## Known failure modes

- Merchant URL unreachable — endpoint may return ok:false with reasons listing connectivity failure
- Budget check fails — budget_ok returns false if payment would exceed configured limits
- Dual-rail check fails — dual_rail returns false if payment rails are not properly configured
- Low accepts_count — few prior accepts may indicate an untrusted or new merchant
- Ambiguous or missing merchant metadata — may result in a cautious non-proceed verdict

## 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: a boolean safe_to_pay flag, a human-readable advice string, a verdict field (e.g. 'proceed'), a proceed boolean, a checks object with budget_ok, dual_rail, and accepts_count fields, and a reasons array listing any risk flags. An ok:true top-level flag confirms the check completed successfully.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "advice": "safe_to_pay=true — settle this call.",
  "checks": {
   "budget_ok": true,
   "dual_rail": true,
   "accepts_count": 2
  },
  "proceed": true,
  "reasons": [],
  "verdict": "proceed",
  "safe_to_pay": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-merchant-legit-gate-4475b2af/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)