# x402 Resource Signed Attestation

> x402 Resource Signed Attestation is a paid API for AI agents from 5.75.142.199.sslip.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Returns a tamper-evident signed attestation for a specific x402 Bazaar resource, including its observed record, trust score, Merkle inclusion proof, daily hash-chain root, and Ed25519 signature.

## Facts

- Endpoint: GET https://5.75.142.199.sslip.io/paid/x402/attest/4
- 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/x402-resource-signed-attestation-353f7539
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q_1Q7OwZiOzTZ183o751v

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 x402-resource-signed-attestation-353f7539
```

Example prompt: Can you get me a signed cryptographic attestation for x402 Bazaar resource ID 4 — I need the Merkle inclusion proof, the trust score, and the Ed25519 signature so I can verify what was observed about that resource at this point in time?

## When to prefer this

Use this endpoint when you need cryptographically verifiable, tamper-evident proof of what an x402 Bazaar resource looked like at a specific point in time — especially for auditing, dispute resolution, or compliance checks. Prefer this over the plain trust dossier endpoint when you specifically need the Merkle proof and Ed25519 signature for independent verification, not just a readable summary.

## Known failure modes

- Resource ID not found — returns 404 or error if resource 4 does not exist in the Bazaar
- Payment not completed — returns 402 if x402 micropayment of $0.02 USDC is not provided
- Signature verification failure — attestation may fail to verify independently if keys have rotated
- Service unavailability — bare IP-based host may have uptime issues

## How this service works

Signed attestation for one x402 resource: its observed record, observed trust score, a Merkle inclusion proof into that day's root, the daily hash-chain root (previous_root linked) and an Ed25519 signature, plus independent verify steps. Tamper-evident evidence of what was observed at a point in time. Free preview: https://5.75.142.199.sslip.io/x402/trust/4

## Output

A signed attestation object containing: the observed record of the x402 resource, its trust score with evidence, a Merkle inclusion proof into the day's root, the daily hash-chain root (with previous_root link for chain verification), and an Ed25519 signature. Together these constitute tamper-evident proof of what was observed about the resource at the time of the call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-resource-signed-attestation-353f7539/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 5.75.142.199.sslip.io](https://www.zero.xyz/host/5.75.142.199.sslip.io/llms.txt)