# Polygon Bridge Withdrawal Inspector

> Polygon Bridge Withdrawal Inspector is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Analyzes caller-supplied evidence for a Polygon PoS bridge withdrawal to determine its observed stage, amount consistency, and whether completion can be claimed — without inferring finality beyond what evidence supports.

## Facts

- Endpoint: POST https://signalharness.ai/api/agent/services/polygon_bridge_withdrawal_inspect/invoke
- 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/polygon-bridge-withdrawal-inspector-4523ff74
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u3Te8Myqo7HLNQhdHy24F

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 polygon-bridge-withdrawal-inspector-4523ff74 -d '<json body>'
```

Example prompt: I need to verify my Polygon bridge withdrawal — I have the burn event data including token address 0x000...0002 and an atomic amount of 100. Can you inspect the evidence and tell me what stage was observed, whether the amounts are consistent, and whether completion is actually claimed?

## When to prefer this

Choose this endpoint when you need a conservative, evidence-bound analysis of a Polygon PoS bridge withdrawal that never infers finality beyond what the caller explicitly supplies. It is ideal for agents or DeFi applications that must avoid prematurely releasing funds or confirming exits before on-chain checkpoint evidence is verified. Prefer it over generic blockchain explorers when you need structured, machine-readable stage analysis with explicit warnings about missing proofs.

## Known failure modes

- Malformed or unparseable request_json causes validation error
- Evidence JSON missing required fields returns incomplete analysis
- No checkpoint or finality evidence supplied — completion will never be claimed and a warning is returned
- Unsupported chain ID in evidence may result in rejection or unrecognized network context
- Service returns succeeded status even when evidence is insufficient — caller must check completion_claimed and warnings fields

## How this service works

Explore 330 pay-per-call x402 API services and 27 agent-native digital products, with Base USDC pricing, secure Polar checkout, and free discovery.

## Output

Returns a structured analysis JSON including: the observed withdrawal stage (e.g. burn_event), whether amounts are consistent across stages, whether completion is claimed, network context (accepted chain IDs, bridge model, completion policy), a list of observed evidence types, per-record details (amount, token, ID), and any warnings about missing or insufficient proof. Also returns the evidence scope and analyzed network name.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request_json": {
   "type": "string",
   "maxLength": 65536,
   "minLength": 2
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "replay": false,
  "result": {
   "warnings": [
    "Does not claim checkpoint inclusion, exit success, or finality without supplied evidence."
   ],
   "service_id": "polygon_bridge_withdrawal_inspect",
   "analysis_json": "{\"amount_consistent\":true,\"amounts\":[{\"amount_atomic\":\"100\",\"stage\":\"burn_event\"}],\"completion_claimed\":false,\"network_context\":{\"accepted_chain_ids\":[\"137\",\"80002\"],\"bridge_model\":\"root-child state sync plus checkpoint evidence\",\"completion_policy\":\"never inferred without supplied evidence\",\"protocol_family\":\"Polygon PoS\"},\"observed_evidence\":[\"burn_event\"],\"observed_stage\":\"burn_event\",\"records\":{\"burn_event\":{\"amount_atomic\":\"100\",\"id\":\"1\",\"token\":\"0x0000000000000000000000000000000000000002\"}}}",
   "evidence_scope": "caller_supplied_data",
   "analyzed_network": "polygon"
  },
  "status": "succeeded",
  "receipt": {
   "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "usage": [],
   "status": "succeeded",
   "network": "eip155:8453",
   "artifacts": [],
   "endedAtMs": 0,
   "latencyMs": 0,
   "paymentId": "example-payment",
   "receiptId": "example-receipt",
   "requestId": "example-request",
   "serviceId": "polygon_bridge_withdrawal_inspect",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "20000",
   "resultSha256": "79c0a2ac29a75d7bc2d84b856b6515936825e7488fd742fd2e781017344f24d7",
   "serviceVersion": "1.0.0",
   "settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
  },
  "artifacts": [],
  "requestId": "example-request",
  "executionId": "example-execution"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/polygon-bridge-withdrawal-inspector-4523ff74/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from signalharness.ai](https://www.zero.xyz/host/signalharness.ai/llms.txt)