verify-claim

# verify-claim

Verify factual claims against live data before using them in responses, calculations, or decisions. Returns structured verdicts with confidence scores and current truth values.

## When to Activate

Use this skill whenever:

- A user states a number as fact ("the exchange rate is 0.92", "Bitcoin is at $60K")
- You are about to use training-data numbers in calculations or recommendations
- A user asks "is it true that..." or "can you verify..."
- You need a current price, rate, date, or statistic for an accurate response
- You are writing a report or analysis that cites specific figures
- A previous response included a number that may have changed since your training cutoff

**Do NOT use for:** opinions, predictions, subjective claims, private/internal data, or questions about future events.

## Workflow

### Step 1: Extract the claim

Identify the specific factual assertion. Be precise — "Bitcoin price is above $60,000" is better than "Bitcoin is expensive."

### Step 2: Check via MCP tool (preferred)

If `@agentutil/verify-mcp` is available as an MCP tool, use it directly:

```
verify_claim({ claim: "The USD to EUR exchange rate is 0.92" })
```

### Step 3: Fall back to HTTP

If no MCP tool is available, call the API:

```bash
curl -X POST https://verify.agentutil.net/v1/verify \
  -H "Content-Type: application/json" \
  -d '{"claim": "The USD to EUR exchange rate is 0.92"}'
```

Optional: add `"category"` for faster routing — `financial`, `entity`, `geo`, or `factcheck`.

### Step 4: Interpret the verdict

| Verdict | Confidence | What to do |
|---------|------------|------------|
| `confirmed` | > 0.9 | Safe to use. Cite `current_truth` as the verified value. |
| `confirmed` | 0.7-0.9 | Likely correct but note the uncertainty to the user. |
| `stale` | any | The claim WAS true but data has changed. Use `current_truth` instead. Tell the user: "That was previously correct, but the current value is X." |
| `disputed` | any | Sources disagree. Present...