# Vibes-Coded Payment-Required Lint Endpoint

> Vibes-Coded Payment-Required Lint 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-09-15).

Validates an x402 payment-gated API artifact or listing for correctness, including base payment configuration, dual-rail support, and Solana compatibility, returning a structured lint report.

## Facts

- Endpoint: POST https://vibes-coded.com/api/v1/outcomes/payment-required-lint
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibes-coded-payment-required-lint-endpoint-a9c52150
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YQuEwu2KBK2O5ocbZEuUm

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-payment-required-lint-endpoint-a9c52150 -d '<json body>'
```

Example prompt: Can you lint my x402 agent tool artifact to check if it has a valid base payment config, dual-rail support, and Solana compatibility — I want to make sure it passes all checks before I publish it to the Vibes-Coded skill marketplace?

## When to prefer this

Choose this endpoint when you need to programmatically validate an x402 pay-per-call API artifact or skill listing for correctness before publishing to the Vibes-Coded marketplace — specifically when you need structured feedback on base USDC config, dual-rail support, and Solana rail presence. Prefer this over manual review or generic JSON schema validators when the target deployment environment is the Vibes-Coded agent skill marketplace with x402 payment gating.

## Known failure modes

- Payment not provided or invalid USDC amount returns HTTP 402 with payment instructions
- Malformed artifact body returns validation error with fail_reasons populated
- Missing required fields in the submitted artifact causes ok=false and has_base/dual_rail flags set to false
- Network timeout if the artifact is overly large or malformed JSON
- Incorrect content-type header may cause parsing failure

## 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

A JSON object with boolean flags: `ok` (overall pass), `valid` (schema validity), `has_base` (base USDC payment configured), `dual_rail` (dual payment rail supported), `has_solana` (Solana rail present), and `fail_reasons` (array of strings describing any failures). Cost is $0.02 USDC per call via HTTP 402.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "valid": true,
  "has_base": true,
  "dual_rail": true,
  "has_solana": true,
  "fail_reasons": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibes-coded-payment-required-lint-endpoint-a9c52150/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)