# PermitVerdict Crypto Price Event Oracle

> PermitVerdict Crypto Price Event Oracle is a paid API for AI agents from permitverdict.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Resolves whether a crypto asset traded or closed above/below a price threshold in a given time window, returning a YES/NO/DISPUTED/UNRESOLVED verdict with per-venue evidence and confidence score for prediction-market settlement.

## Facts

- Endpoint: GET https://permitverdict.com/v1/oracle/resolve
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/permitverdict-crypto-price-event-oracle-d6f54520
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1_0m0mGs2z3wYEx2mCamV

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 permitverdict-crypto-price-event-oracle-d6f54520
```

Example prompt: Did BTC close above $65,000 at any point between January 10 and January 15, 2025? I need a settlement verdict with per-venue evidence and confidence score — I'm resolving a prediction market contract using close-not-touch mode.

## When to prefer this

Use this endpoint when you need a definitive, evidence-backed settlement verdict for a crypto price event — especially for prediction market resolution, conditional order verification, or dispute arbitration. Prefer it over raw price feeds when you need a structured YES/NO answer with multi-venue corroboration, confidence scoring, and explicit handling of touch-vs-close semantics.

## Known failure modes

- UNRESOLVED returned when insufficient venue data exists for the time window
- DISPUTED returned when venues disagree significantly on price
- Missing or invalid asset symbol returns an error
- Time window out of range of available historical data
- Ambiguous touch-vs-close parameter causes unexpected verdict interpretation
- Venue data gaps during low-liquidity periods may reduce confidence score

## How this service works

Settlement verdict for a crypto price event: did the asset trade or close above/below a threshold in a window? Returns YES/NO/DISPUTED/UNRESOLVED with per-venue evidence, touch-vs-close handling, and stated confidence. Built for prediction-market settlement and conditional-order agents.

## Output

Returns a verdict of YES, NO, DISPUTED, or UNRESOLVED indicating whether the price condition was met, along with per-venue evidence showing individual exchange price data, a touch-vs-close determination, a confidence score, and metadata supporting the settlement decision.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/permitverdict-crypto-price-event-oracle-d6f54520/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from permitverdict.com](https://www.zero.xyz/host/permitverdict.com/llms.txt)