# Proxy402 Paywalled Resource (POST /yRFgesLFaw)

> Proxy402 Paywalled Resource (POST /yRFgesLFaw) is a paid API for AI agents from proxy402.com, paid per call via x402, $1/call, status down (last checked 2026-10-13).

Accepts a micropayment via x402 protocol and proxies a POST request to the paywalled resource at proxy402.com/yRFgesLFaw for $1 USDC per call.

## Facts

- Endpoint: POST https://proxy402.com/yRFgesLFaw?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: down
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/proxy402-paywalled-resource-post-yrfgeslfaw-cb7f0ad1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4z-Fh5mNpNMx-f2HmEsmL

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 proxy402-paywalled-resource-post-yrfgeslfaw-cb7f0ad1 -d '<json body>'
```

Example prompt: Pay the $1 USDC access fee via x402 and send my POST request to the Proxy402-protected endpoint at yRFgesLFaw so I can retrieve the response.

## When to prefer this

Use this endpoint when you need to access the specific paywalled resource at proxy402.com/yRFgesLFaw via a POST method and are willing to spend $1 USDC per call. Prefer this over other Proxy402 siblings when your target resource specifically requires a POST method rather than GET.

## Known failure modes

- Insufficient USDC balance — payment rejected, 402 Payment Required returned
- Invalid or missing x402 payment header — request blocked
- Network timeout accessing the proxied upstream resource
- Upstream resource unavailable — 502 or 503 returned after payment
- Payment already used / replay detected — payment rejected

## How this service works

Payment for GET https://proxy402.com/yRFgesLFaw

## Output

After the $1 USDC micropayment is processed via the x402 protocol, the agent receives the HTTP response from the proxied POST endpoint — including status code, headers, and body content returned by the underlying protected resource.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/proxy402-paywalled-resource-post-yrfgeslfaw-cb7f0ad1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from proxy402.com](https://www.zero.xyz/host/proxy402.com/llms.txt)