# Livecheck Confirm

> Livecheck Confirm is a paid API for AI agents from livecheck.fly.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Independently verifies that a lead/contact form submission succeeded by fetching the thank-you or result page and returning a confirmed/failed/unknown verdict with evidence

## Facts

- Endpoint: POST https://livecheck.fly.dev/v1/confirm
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/livecheck-confirm-9cb0f3ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bA0EzQkY-ayOqHtIwSkRq

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 livecheck-confirm-9cb0f3ed -d '<json body>'
```

Example prompt: After I submitted that contact form, can you independently verify the submission went through by checking the thank-you page at https://example.com/thank-you?ref=ABC123 — I need a confirmed verdict with a real reference ID before we move to the next step?

## When to prefer this

Use this endpoint when an AI agent has just submitted a lead or contact form and needs independent, cookieless verification that the submission succeeded before taking a costly or irreversible next step (e.g. triggering a payment, sending a follow-up, or logging a conversion). Prefer this over self-grading (checking your own session/cookie-based result) because the actor and verifier are separate. Do not use this for general URL liveness checks (use /v1/verify instead), payment settlement confirmation, or classifying thank-you page content without a specific lead_submit intent.

## Known failure modes

- Page returns HTTP non-200 status — verdict likely failed or unknown
- Thank-you page has no reference/confirmation ID — evidence_strength stays below Level 2, verdict may be unknown rather than confirmed
- Page requires cookies or session state from original submission — cookieless fetch cannot access content, returns unknown
- URL is a URL-encoded redirect or short link that does not resolve — returns failed
- Intent other than lead_submit is provided — request rejected, only lead_submit is accepted in v0
- Network timeout or DNS failure fetching the provided URL — returns failed or unknown

## How this service works

Livecheck Confirm — use after your agent submits a lead/contact form (intent=lead_submit): POST {url, intent} where url is the thank-you or result page. Returns confirmed|failed|unknown with Level-2+ evidence (confirmation/ref/ticket id required for confirmed). Independent cookieless verifier — actor ≠ verifier — so you do not grade your own homework before the next paid or irreversible step. Not URL/stock liveness (use /v1/verify), not payment/tx settlement, not a thank-you-page classifier.

## Output

A JSON object containing the verdict (confirmed, failed, or unknown), the effect type and ID (e.g. confirmation/reference/ticket number), a list of evidence signals (e.g. cookieless_fetch, confirmation_id, level_2), evidence strength level (integer), whether evidence is independent, the fetched URL and canonical URL, HTTP status, fetch timestamp, and a unique evidence_id for audit purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Absolute http(s) URL. lead_submit: thank-you or result page. listing_published: specific job, product, or eBay item URL."
  },
  "claim": {
   "type": "object",
   "description": "Optional. Not required. lead_submit ignores claim. listing_published: title/sku/id may match or veto; not required for L2."
  },
  "intent": {
   "enum": [
    "lead_submit",
    "listing_published"
   ],
   "type": "string",
   "description": "Payable on POST /v1/confirm: lead_submit ($0.10), listing_published ($0.10). listing_published claim.title/sku/id optional. order_placed uses POST /v1/confirm/order."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "cfm_01J8Z0K3N4P5Q6R7S8T9V0WXYZ",
  "url": "https://example.com/thank-you?ref=ABC123",
  "effect": {
   "id": "ABC123",
   "type": "lead_submit"
  },
  "receipt": {
   "hash": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
   "verify_url": "https://livecheck.fly.dev/v1/receipt/cfm_01J8Z0K3N4P5Q6R7S8T9V0WXYZ"
  },
  "signals": [
   "cookieless_fetch",
   "confirmation_id",
   "level_2"
  ],
  "verdict": "confirmed",
  "price_usd": 0.1,
  "confidence": 0.92,
  "fetched_at": "2026-09-06T17:00:00Z",
  "evidence_id": "ev_01example",
  "http_status": 200,
  "canonical_url": "https://example.com/thank-you?ref=ABC123",
  "evidence_level": 2,
  "evidence_strength": 2,
  "independent_signals": 1,
  "independent_evidence": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/livecheck-confirm-9cb0f3ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from livecheck.fly.dev](https://www.zero.xyz/host/livecheck.fly.dev/llms.txt)