# Signature Verification & Dual-Chain Attestation

> Signature Verification & Dual-Chain Attestation is a paid API for AI agents from 1c09pdnrx1.execute-api.us-east-1.amazonaws.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Verifies a cryptographic signature over (input_hash, output_hash, decision) tuple and anchors the attestation result on both Base and Solana mainnets

## Facts

- Endpoint: POST https://1c09pdnrx1.execute-api.us-east-1.amazonaws.com/v1/attest
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signature-verification-dual-chain-attestation-1ccdbb68
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zVUVMY4WUVTzCNLFGnacZ

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 signature-verification-dual-chain-attestation-1ccdbb68 -d '<json body>'
```

Example prompt: Verify the signature over this decision tuple — input_hash 0xabc123..., output_hash 0xdef456..., decision 'approved' — and anchor the attestation on both Base and Solana so we have a permanent dual-chain proof.

## When to prefer this

Use this endpoint when you need both cryptographic signature verification AND immutable dual-chain (Base + Solana) anchoring in a single call. Prefer it over the plain hash-anchor endpoint when you have a signed (input_hash, output_hash, decision) tuple and need provable attestation of an AI or agent decision, not just a raw hash commitment.

## Known failure modes

- Invalid or malformed signature returns verification failure without anchoring
- Malformed or non-32-byte hashes cause a 400 bad request
- Blockchain congestion or RPC failure on Base or Solana may cause partial anchor failure
- Payment not included or insufficient USDC ($0.01) causes 402 Payment Required
- Replay of identical (input_hash, output_hash, decision) may succeed but creates a duplicate anchor record

## How this service works

Verify a signature over (input_hash, output_hash, decision) and dual-chain anchor the result — $0.01 USDC

## Output

Returns signature verification status (valid/invalid), plus transaction IDs from both Base and Solana mainnets confirming the attestation has been anchored on-chain, providing a tamper-proof dual-chain audit record of the signed decision.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "title": "DatetimeParseRequest",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string",
   "title": "Input",
   "maxLength": 500,
   "minLength": 1,
   "description": "Freeform datetime string in any format."
  },
  "timezone": {
   "type": "string",
   "title": "Timezone",
   "default": "UTC",
   "description": "IANA tz name (e.g. 'America/New_York')."
  },
  "base_time": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ],
   "title": "Base Time",
   "description": "ISO 8601 reference; defaults to now UTC."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signature-verification-dual-chain-attestation-1ccdbb68/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 1c09pdnrx1.execute-api.us-east-1.amazonaws.com](https://www.zero.xyz/host/1c09pdnrx1.execute-api.us-east-1.amazonaws.com/llms.txt)