# Vibes-Coded Facilitator Payload Lint API

> Vibes-Coded Facilitator Payload Lint API is a paid API for AI agents from vibes-coded.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Validates and lints an x402 facilitator payload, checking compliance for CDP and stripping non-conformant keys to return a lean, safe payload.

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/facilitator-payload-lint
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-facilitator-payload-lint-api-4c86ce6b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rLkkKVigd34Fgtfcoefni

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-facilitator-payload-lint-api-4c86ce6b -d '<json body>'
```

Example prompt: Can you lint this x402 facilitator payload and tell me if it's valid for CDP, what's failing, and give me back the stripped lean version without the bad keys?

## When to prefer this

Use this endpoint when you need to pre-validate or debug an x402 facilitator payload before sending it to a live facilitator or CDP integration. Prefer this over manual inspection when you need a machine-readable list of fail reasons and a ready-to-use lean payload with bad keys already stripped. Ideal for agents that construct x402 payment flows dynamically and need a compliance gate before relay.

## Known failure modes

- Payload missing required x402Version field causing validation error
- Malformed JSON body rejected before linting begins
- HTTP 402 returned if USDC payment header is missing or insufficient
- Payload with no issues returns ok:true but stripped_keys may still be populated if optional fields were cleaned
- Unknown fail_reason codes if payload structure is deeply malformed

## 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 overall validity), `ok_for_cdp` (boolean CDP-specific compliance), `fail_reasons` (array of string codes like 'sibling_resource' or 'sibling_extensions' explaining failures), `lean_payload` (cleaned payload object with only compliant fields), and `stripped_keys` (list of keys that were removed for non-compliance).

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "ok_for_cdp": false,
  "fail_reasons": [
   "sibling_resource",
   "sibling_extensions"
  ],
  "lean_payload": {
   "payload": {},
   "accepted": {},
   "x402Version": 2
  },
  "stripped_keys": [
   "resource",
   "extensions"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-facilitator-payload-lint-api-4c86ce6b/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)