# VIBE Shield Transaction Validator

> VIBE Shield Transaction Validator is a paid API for AI agents from api.vibe.airforce, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-15).

Validates EVM transaction data on a specified network, likely screening for smart money or security signals before execution.

## Facts

- Endpoint: POST https://api.vibe.airforce/api/x402/vibe-tools/shield/validate
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibe-shield-transaction-validator-ea2ac957
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EAJlLDI7pqfTiRidB9g09

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 vibe-shield-transaction-validator-ea2ac957 -d '<json body>'
```

Example prompt: Can you run this Ethereum transaction data through VIBE Shield to validate it before I submit it — the network is Base and the tx object has a swap from USDC to ETH for 500 USDC?

## When to prefer this

Use this endpoint when you need to validate EVM transaction data before broadcasting, particularly within the VIBE ecosystem for DeFi smart money workflows. Prefer this over generic validators when you want VIBE's AI-driven smart money screening applied to transaction validation, especially for Base network transactions paid via x402 USDC microtransactions with no API key required.

## Known failure modes

- Missing required tx_data field returns 400 or validation error
- Invalid or unsupported EVM network string causes rejection
- Malformed transaction object triggers schema validation failure
- Payment of 0.012 USDC not included causes 402 Payment Required
- Network mismatch between tx_data chain ID and network field
- Empty or null transaction data object returns error

## How this service works

Top Picks: AI-verified smart money tokens every 30 min. 6-dimension scores, one-sentence thesis, smart money flow data. Plus 50+ crypto-data endpoints via x402 USDC on Base. No API keys, no accounts.

## Output

A validation response indicating whether the transaction data is valid or flagged, potentially including shield/security signals relevant to the transaction on the specified EVM network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "tx_data"
 ],
 "properties": {
  "network": {
   "type": "string",
   "description": "EVM network"
  },
  "tx_data": {
   "type": "object",
   "description": "Transaction data to validate"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibe-shield-transaction-validator-ea2ac957/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vibe.airforce](https://www.zero.xyz/host/api.vibe.airforce/llms.txt)