Orcpin · Door Report

The audit of one door

Verifying…

How to read this audit

A seller sees a door from the inside. A buyer sees it once, with no memory. This document records what a third party observed at the door, with a funded wallet and the public chain, in the order a buyer meets it: the quote, then real purchases, then the seller's inbound books, then what a response cost. Every figure is a count, an amount, a share or an HTTP status. Nothing in it is a verdict about the seller.

Quote: what the door asked for when asked without paying, and whether the places it is advertised ask for the same.
Purchase: what happened when Orcpin paid. Quoted, signed, settled, read back from the chain, delivered, then a reused payment and a malformed one.
Books: every incoming USDC transfer to the door's payee over the last thirty days, from the public chain, as counts and amounts only.
Cost: what a delivered response cost here, and where this door's price sits among every priced door in the public catalog.

The signature and the transparency-log entry at the top were checked by your browser when this page opened, against Orcpin's public key registry and log. If you were handed this document by anyone but Orcpin, that check is what tells you it is the one Orcpin issued.

Quote

What the door asks for, and whether everyone agrees

What was doneOne unpaid request to the door, exactly as an agent's first call arrives. The 402 challenge it returns is the binding quote: price, asset, payee, and how long the offer stands.

Why it mattersAgents budget from listings. The seller's own manifest, the public catalog, and Orcpin's weekly crawl each advertise a price and a payee; when they disagree with the door, a buyer is surprised at the moment of paying.

How to read it"Agrees" means the atomic amount matches to the unit. A surface that does not list the door neither agrees nor disagrees. The schema line says whether an agent can learn the request shape from the 402 alone.

Purchase

What happened when Orcpin paid

What was doneReal purchases with Orcpin's own separately funded wallet. Each was captured at both requests of the paid call: the quote the wallet saw, the authorization it signed, the facilitator's settlement receipt, that transaction's USDC transfer read back from the node, and the response. Then the first payment was sent again, and a well-formed header that is not a payment was sent.

Why it mattersThis is the only part of the audit that a listing, a probe, or the seller's own dashboard cannot produce: the four numbers that should be equal, quoted, signed, settled, on chain, and whether a valid response came back for the money.

How to read it"Delivered" is a 2xx with valid JSON. A settlement without delivery is money taken and not delivered for, in this sample. A reused payment that delivers is a response the seller was not paid for. An outcome of "payment not made" is about Orcpin's own wallet, not the door: the facilitator refused the payment, so the door was never asked.

Books

The door's inbound side, from the chain

What was doneEvery incoming USDC transfer to the door's payee over the last thirty days was read from the public explorer and aggregated in memory. Payer addresses were held for the duration of the read and discarded; none appears in this document.

Why it mattersA seller's revenue is public, but its shape is not obvious from an explorer: how many wallets pay, how many come back, how concentrated the traffic is, and how much of it looks like verifiers and probes rather than use.

How to read itA payer who settled exactly once at exactly this door's price left the shape a probe, a verifier or a one-time trial leaves. Repeat payers settled on two or more separate days. Amounts that differ from this door's price belong to the seller's other doors sharing the payee. Zero-value transfers are dust, not revenue.

Cost

What a delivered response cost, and where the price sits

What was doneThe purchases above were reduced to one figure, USDC settled per delivered response, and this door's price was placed among every USDC-priced door in the public catalog, and among the same seller's other doors. Orcpin's own probe history for the door is shown alongside.

Why it mattersA price is only meaningful against what it buys and what the market charges. A door priced above the median that delivers every time is cheaper, per useful response, than a free one that times out.

How to read itThe catalog shares are a position in a distribution, not a ranking of worth. The probe history is Orcpin's independent record of the door's behaviour before this audit; where it is empty, this audit's purchases are the only measurement and should be read as a sample.

Attention

Patterns worth a second look

Each line names a pattern the audit matched and the fact behind it. A pattern is a description, not a finding about any party: a listing may simply be stale; a one-time payer may simply be a one-time customer. The reader draws the conclusion.

Provenance

What this document is, and is not

Method for every figure: the published methodology. Nothing about the request that produced this document is stored by Orcpin beyond the payload hash in the transparency log; this page renders and verifies it in your browser and uploads nothing.

The signed document