---
name: prove_live_before_calling_wired
title: "Prove Live Before Calling It Wired"
description: "Classify and prove a service as reachable, wired or settle proven with outside probes and a smallest real settle before reporting that it can take payments."
version: 1.0.0
author: Script Master Labs LLC
license: MIT
source: https://scriptmasterlabs.com/hive402-skills/prove_live_before_calling_wired/SKILL.md
registry: HIVE402 Skills (https://scriptmasterlabs.com/hive402-skills)
---

# Prove Live Before Calling It Wired

## Classify the state before you claim it

- Sort every service into one state before reporting it. Reachable means an outside request gets a response, wired means the full path works end to end, and settle proven means a real payment moved and settled.

- Keep dark by design and waiting on the user as separate states. Name them instead of counting them as broken or as live.

- Never report a service as wired, active or ready to take payments from a deploy success, a health check alone or an internal checker card alone.

## Probe from outside

- Probe the public address a buyer or another agent would actually use, and record the status, the challenge or response shape and the time of the probe.

- Trust the outside probe over internal checkers, code reads and dashboard cards when they disagree, and say plainly which source won.

- Check shared infrastructure before blaming new code when a deploy and its rollback fail in the identical way. A full disk, a missing persistent disk or a dead credential explains identical failures better than the last commit does.

## Run the smallest real settle

- Validate request arguments before any settlement attempt, so an invalid request fails with an argument error and moves no money.

- Settle the smallest real amount the route allows and record the transaction or receipt handle as the proof.

- Label every self payment as self-proof in the report. Never present a self payment, a free view or an owner test as a stranger sale.

## Report the counts by state

- Report fleet or audit results as counts per state, with probed, settle proven, live but unproven, broken, dark by design and waiting on the user kept separate.

- Name each broken item with the outside evidence that shows it, such as the status code at its public address.

- Carry unproven items forward as an open list with a next probe or settle step, instead of letting a live label stand in for proof.

## Alternatives for better results

- Reprobe from outside after every redeploy before repeating a wired claim, since a deploy can reset in-memory receipts, keys or state.

- Reach for a second independent outside route when the first probe and the internal checker disagree, and let the two outside reads settle the claim.


---

## From Script Master Labs

This skill is listed in [HIVE402 Skills](https://scriptmasterlabs.com/hive402-skills) —
every skill there passed a verification gate before listing: parsed, safety-scanned,
provenance recorded, self-contained. Skills, probed before listed.

Script Master Labs also runs [HIVE402](https://hive402.scriptmasterlabs.com), the
payability-probed catalog of 132 paid agent APIs, [OMNIGATE](https://scriptmasterlabs.com/omnigate-facilitator),
the x402 gateway those payments settle through, and the free
[x402 Starter Kit](https://scriptmasterlabs.com/x402-kit).