# SYNTHORA Transaction Intent Classifier

> SYNTHORA Transaction Intent Classifier is a paid API for AI agents from api.hergertsynthora.com, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-16).

Decodes the real intent of an on-chain Ethereum/Base transaction and returns an Ed25519-signed risk verdict (safe/review/suspicious/dangerous) flagging issues like unlimited approvals, opaque selectors, and reverted transactions.

## Facts

- Endpoint: POST https://api.hergertsynthora.com/v1/txintent
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthora-transaction-intent-classifier-a9cebe51
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mu7E28EmBfwz6c9zlsck8

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 synthora-transaction-intent-classifier-a9cebe51 -d '<json body>'
```

Example prompt: Can you check if this Base transaction is safe — the hash is 0x4a7b9c2d1e3f... — I want to know its real intent and whether it has any unlimited approvals or other red flags before I approve it.

## When to prefer this

Choose this endpoint when you need a cryptographically signed, human-readable risk classification of a specific Ethereum or Base transaction before or after execution — especially when you need to detect unlimited token approvals, obfuscated calldata, unexpected ETH-to-contract transfers, or reverted malicious calls. Prefer this over generic ABI decoders when you need a clear safe/suspicious verdict with a verifiable signature rather than just raw decoded data.

## Known failure modes

- Invalid or unrecognized tx_hash returns an error — transaction may not be indexed yet or may not exist on the specified chain
- Unsupported chain identifier causes a 400-level error
- Missing both tx_hash and to/data fields results in a validation error
- Highly obfuscated or novel contract interactions may result in a 'review' verdict rather than a definitive classification
- Payment failure (x402) blocks the call if USDC balance is insufficient
- Network latency from on-chain RPC lookups may cause timeouts for recently submitted transactions

## How this service works

Tx Intent Classifier: decodes the REAL intent of an on-chain transaction (Base/Ethereum) and returns an Ed25519-signed risk verdict (safe/review/suspicious/dangerous). Catches unlimited approvals, opaque selectors, value-to-contract, reverted tx. POST {"tx_hash":"0x..","chain":"base"} or {"to":"0x..","data":"0x.."}.

## Output

A risk verdict label (safe, review, suspicious, or dangerous) accompanied by a decoded human-readable intent description of the transaction, specific risk flags detected (e.g. unlimited approval, opaque selector, value sent to contract, reverted tx), and an Ed25519 cryptographic signature authenticating the verdict.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "data": {
   "type": "string"
  },
  "chain": {
   "type": "string"
  },
  "tx_hash": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthora-transaction-intent-classifier-a9cebe51/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.hergertsynthora.com](https://www.zero.xyz/host/api.hergertsynthora.com/llms.txt)