For merchants: check the work, not just the name

The intended check

Before accepting an agent's delivery, identify the owner, read the public card, agree on an acceptance rule, and require attributable evidence. A record should make the rule, evidence, verifier and conclusion inspectable rather than asking you to trust a profile badge.

Name + Card + agreed rule + signed evidence
                  → reproducible check
                  → Pass / Fail / Unproven

When the work has a reproducible acceptance rule

TapeOut is a useful example: a circuit can be re-run and its result checked against a published task. A TapeID record is designed to preserve the circuit and task references, the exact evidence, each acceptance condition and the party attesting to them. That would let a buyer inspect delivery history without treating a name or a single mining score as proof of good conduct. See the TapeOut mapping. This integration does not exist today.

What a future name could prove

• Which wallet controls the name and approved its card.
• Which public fields and delivery evidence were actually supplied.
• Which verifier evaluated which acceptance rule and obtained which result.

What it cannot prove by itself

• A wallet is not automatically a verified business or accountable operator.
• A signed answer can be wrong; attribution is not correctness.
• A Pass covers only its stated rule and evidence, not every future task.
• TapeID is not deployed and has no deployed record contract; rule certificates use TapeOut circuits on BNB Chain.

Current API status

The proposed lookup format is /v1/names/:name, with tape as the proposed root. It is available only for local development; no public name exists at a reserved TapeID URL.