# Trust402 x402 Payment-Flow & Trust Drift Snapshot

> Trust402 x402 Payment-Flow & Trust Drift Snapshot is a paid API for AI agents from trust402.vercel.app, paid per call via x402, $0.015/call, status unknown (last checked 2026-09-14).

Runs a one-shot x402 payment-flow test and captures a trust drift snapshot for a given endpoint, without persisting any history.

## Facts

- Endpoint: POST https://trust402.vercel.app/api/monitor/snapshot
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/trust402-x402-payment-flow-trust-drift-snapshot-c02769d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hVd_EvsEMVD4BV6gOVIOK

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 trust402-x402-payment-flow-trust-drift-snapshot-c02769d6 -d '<json body>'
```

Example prompt: Run a one-shot x402 payment-flow snapshot on https://api.myservice.com/data using a GET request — I want to see the trust drift result right now without storing any history.

## When to prefer this

Choose this endpoint when you need a lightweight, stateless, one-shot x402 payment-flow probe and trust drift reading for a single endpoint — ideal when you don't need historical tracking or persistent records. Prefer it over the full diligence report when speed matters and a quick snapshot suffices, or over the live probe endpoint when you specifically need the trust drift dimension alongside payment-flow readiness.

## Known failure modes

- Invalid or unreachable endpoint URI returns an error or timeout
- Malformed URI format in origin or endpoint fields causes validation failure
- Endpoint not implementing x402 protocol returns unexpected response or no challenge
- Network errors or SSL issues on the target endpoint may cause probe failure
- Missing required fields (endpoint) may result in a 400 bad request

## How this service works

Run a one-shot x402 payment-flow and trust drift snapshot without storing history.

## Output

Returns a one-shot trust drift snapshot including the outcome of the x402 payment-flow challenge against the specified endpoint: payment readiness status, trust signals, challenge response details, and drift indicators — without persisting any history to storage.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "enum": [
    "GET",
    "POST",
    "PUT",
    "PATCH",
    "DELETE",
    "HEAD"
   ],
   "type": "string",
   "default": "GET"
  },
  "origin": {
   "type": "string",
   "format": "uri"
  },
  "endpoint": {
   "type": "string",
   "format": "uri"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/trust402-x402-payment-flow-trust-drift-snapshot-c02769d6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from trust402.vercel.app](https://www.zero.xyz/host/trust402.vercel.app/llms.txt)