# Blackwall x402 Payment-Risk Oracle

> Blackwall x402 Payment-Risk Oracle is a paid API for AI agents from agent-egress-proxy.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns a GO / HOLD / STOP verdict before an agent signs an x402 payment, based on counterparty reputation and price-anomaly signals.

## Facts

- Endpoint: POST https://agent-egress-proxy.onrender.com/v1/forecast-payment
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blackwall-x402-payment-risk-oracle-059b2e7c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_L07WRsYaoXO5TsWVSaEVE

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 blackwall-x402-payment-risk-oracle-059b2e7c -d '<json body>'
```

Example prompt: Before I sign this payment, check if it's safe: I'm paying 0.50 USDC on the Base chain for resource https://api.example.com/data to counterparty 0xAbC123…def456 — give me a GO, HOLD, or STOP verdict.

## When to prefer this

Choose this endpoint when an AI agent is operating autonomously in an x402 payment flow and needs a pre-signature guardrail before committing funds. It is especially valuable when the counterparty is unknown, the requested amount seems anomalous relative to the resource, or the agent policy requires human-level risk gating without a human in the loop. Prefer this over generic blockchain explorers or address checkers when you need a single actionable verdict (GO/HOLD/STOP) combining both reputation and price-anomaly signals in one call.

## Known failure modes

- Missing required fields (asset, chain, amount, or counterparty) returns a 400 validation error
- Unknown or unresolvable counterparty address may result in a HOLD verdict with low confidence
- Network or chain identifier not supported returns an error
- Service unavailable on the rendering host returns a 503
- Amount format mismatch (non-numeric string) causes a parsing error

## How this service works

Pre-signature x402 payment guardrail: returns a GO / HOLD / STOP verdict before an agent signs a payment, from behavioral counterparty reputation and price-anomaly signals.

## Output

A JSON object containing a verdict string ('GO', 'HOLD', or 'STOP') indicating whether the payment is safe to sign, plus a receipt_id string for auditing and tracing the risk assessment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "asset",
  "chain",
  "amount",
  "counterparty"
 ],
 "properties": {
  "asset": {
   "type": "string"
  },
  "chain": {
   "type": "string"
  },
  "payer": {
   "type": "string"
  },
  "amount": {
   "type": "string"
  },
  "resource": {
   "type": "string"
  },
  "counterparty": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "verdict": "GO",
 "receipt_id": "..."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blackwall-x402-payment-risk-oracle-059b2e7c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-egress-proxy.onrender.com](https://www.zero.xyz/host/agent-egress-proxy.onrender.com/llms.txt)