# Polygon Bridge Timeline Reconstructor

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

Analyzes and reconstructs the event timeline of Polygon PoS bridge transactions from caller-supplied event data, identifying missing stages and ambiguous ordering.

## Facts

- Endpoint: POST https://signalharness.ai/api/agent/services/polygon_bridge_timeline_reconstruct/invoke
- Price: $0.025/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-timeline-reconstructor-ca9fb1e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fdwzqSt02ynqTgk2fXTfT

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-timeline-reconstructor-ca9fb1e5 -d '<json body>'
```

Example prompt: I have a list of Polygon PoS bridge events including block numbers, chain IDs, log indices, and addresses — can you reconstruct the timeline, tell me which stages like lock, mint, burn, checkpoint, or exit are missing, and flag any ambiguous ordering?

## When to prefer this

Choose this endpoint when you have raw Polygon PoS bridge event data and need to understand the sequential lifecycle of a bridge transaction — specifically to identify missing stages, detect ordering ambiguity, or audit whether a transfer reached completion. Prefer this over generic blockchain explorers when you need structured stage-by-stage analysis of the lock→mint→burn→checkpoint→exit flow specific to the Polygon PoS bridge model. Note that this endpoint operates purely on caller-supplied data and does not fetch on-chain data itself.

## Known failure modes

- Caller supplies incomplete or malformed event JSON — analysis proceeds but missing_stages list will be extensive
- Timestamps and event authenticity are not verified — the service explicitly warns these are caller-supplied and unvalidated
- Unsupported chain IDs may result in incomplete network context or rejection
- Malformed request_json string (not valid JSON within the string) may cause a parsing error
- Completion is never inferred without explicit supplied evidence — agents should not assume completion even if many stages are present

## 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 JSON analysis containing an ordered list of bridge events, a list of missing stages (from lock, mint, burn, checkpoint, exit), a flag indicating whether event ordering is ambiguous, a completion_claimed boolean, a count of events processed, and network context including accepted chain IDs, bridge model description, and completion policy. Also returns the evidence scope (always 'caller_supplied_data') and analyzed network ('polygon').

## 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": [
    "Timestamps and event authenticity are caller supplied."
   ],
   "service_id": "polygon_bridge_timeline_reconstruct",
   "analysis_json": "{\"ambiguous_order\":false,\"completion_claimed\":false,\"count\":1,\"events\":[{\"_source_index\":0,\"address\":\"0x0000000000000000000000000000000000000001\",\"block_number\":1,\"chain\":\"137\",\"log_index\":0,\"transaction_index\":0}],\"missing_stages\":[\"lock\",\"mint\",\"burn\",\"checkpoint\",\"exit\"],\"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\"}}",
   "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_timeline_reconstruct",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "25000",
   "resultSha256": "3a834c73e0261dbc6609aeb957e56b0eca593c914efb514f1f2e234609096017",
   "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-timeline-reconstructor-ca9fb1e5/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)