# Vino & Views Transaction Preflight Check

> Vino & Views Transaction Preflight Check is a paid API for AI agents from api.vinoandviews.online, paid per call via x402, $0.2/call, status unknown (last checked 2026-10-10).

Validates and previews an HTTP transaction before execution, returning a spend-policy verdict and evidence receipt for the request.

## Facts

- Endpoint: POST https://api.vinoandviews.online/v1/tx-preflight?utm_source=zero.xyz
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vino-views-transaction-preflight-check-99bab62b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e5gkFBXOwptsLbI1k7rcc

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 vino-views-transaction-preflight-check-99bab62b -d '<json body>'
```

Example prompt: Before I fire off that POST request with the JSON body to update the order, can you run a preflight check through Vino & Views to make sure it passes the spend policy and get me back an evidence receipt?

## When to prefer this

Choose this endpoint when you need a deterministic, read-only safety check on a state-changing HTTP request before executing it — especially in agentic workflows where spend policies, approval ceilings, or audit trails are required. It is ideal as a pre-execution gate in automated pipelines handling payments or sensitive mutations.

## Known failure modes

- Missing required 'input' object returns validation error
- Invalid HTTP method (must be POST, PUT, or PATCH) causes rejection
- Unsupported bodyType value causes schema validation failure
- Malformed body object may result in policy evaluation failure
- Request exceeds spend ceiling, returning a denial verdict
- Network timeout or service unavailability returns non-200 status

## How this service works

Source-backed API reports for wallet-enabled agents. Pay per successful call in Base USDC.

## Output

Returns a JSON object with a 'status' field (e.g. 'ok') and an 'evidence_receipt' containing a SHA-256 hash of the preflighted transaction, serving as a cryptographic record that the request was checked against spend policy before execution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "string",
   "title": "Data",
   "default": "0x",
   "maxLength": 8194
  },
  "chain": {
   "enum": [
    "robinhood",
    "ethereum",
    "base",
    "bsc"
   ],
   "type": "string",
   "title": "Chain"
  },
  "sender": {
   "type": "string",
   "title": "Sender",
   "description": "Address whose state and balance will be simulated"
  },
  "target": {
   "type": "string",
   "title": "Target",
   "description": "Destination contract or account"
  },
  "value_wei": {
   "type": "integer",
   "title": "Value Wei",
   "default": 0,
   "maximum": 1.157920892373162e+77,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vino-views-transaction-preflight-check-99bab62b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vinoandviews.online](https://www.zero.xyz/host/api.vinoandviews.online/llms.txt)