# x402 Verifiable Intent & Solana Payment Binding Verifier

> x402 Verifiable Intent & Solana Payment Binding Verifier is a paid API for AI agents from x402-secure-api.t54.ai, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-28).

Verifies Verifiable Intent evidence and validates the binding between agent intent and a Solana x402 payment before executing an agent payment

## Facts

- Endpoint: POST https://x402-secure-api.t54.ai/x402/solana/tools/verify_verifiable_intent?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-verifiable-intent-solana-payment-binding-verifier-2b27f003
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YOnXPkjAUDXbPaXaXgMb1

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-verifiable-intent-solana-payment-binding-verifier-2b27f003 -d '<json body>'
```

Example prompt: Before I send this 0.5 USDC Solana payment, verify that my Verifiable Intent evidence is properly bound to the x402 payment — here's the intent proof and the payment reference — and tell me if it's safe to proceed.

## When to prefer this

Use this endpoint when an AI agent is about to execute a Solana-based x402 payment and needs to verify that the declared Verifiable Intent evidence is cryptographically bound to that specific payment — particularly to guard against prompt injection, intent hijacking, or unauthorized payment redirects. Prefer this over generic payment validation when the x402 protocol and Verifiable Intent framework are in use together.

## Known failure modes

- Intent evidence does not match payment binding — returns mismatch/invalid status
- Malformed or missing intent evidence payload — returns 400 validation error
- Solana x402 payment reference not found or expired — returns not-found error
- Cryptographic signature on Verifiable Intent fails verification — returns authentication failure
- Upstream Solana RPC or x402 protocol timeout — returns service unavailable
- Payment already executed or replayed — returns duplicate/stale binding error

## How this service works

Verify Verifiable Intent evidence and Solana x402 payment binding before an agent payment. Price: $0.1 USDC (Solana)

## Output

Returns a verification result indicating whether the Verifiable Intent evidence is valid and correctly bound to the specified Solana x402 payment, along with a binding validity status and any risk signals that would indicate the payment should not be executed.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-verifiable-intent-solana-payment-binding-verifier-2b27f003/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-secure-api.t54.ai](https://www.zero.xyz/host/x402-secure-api.t54.ai/llms.txt)