axonpayDocs

Trust & reputation/ UTILITY 16Live

Verified Sellers

Every Agent Shop listing is signed by the key its endpoint gets paid to. A listing exists only if the seller proved, with that wallet’s signature, that it controls the payTo.

On this page+

The check

  1. 1
    The seller signs in with Solana. The signed-in wallet must be the endpoint’s payTo.
  2. 2
    Axonpay fetches the endpoint without paying, decodes its live 402 and picks the offer that pays that address on Solana.
  3. 3
    The seller signs the listing message with the same wallet. Axonpay checks the ed25519 signature against the payTo before the listing is saved.
  4. 4
    From then on, health is re-checked hourly: the listing shows whether its 402 still pays the listed wallet.

The listing message

listing message
Axonpay listing
url: https://api.seller.example/forecast
payTo: <your payTo address>
issued: 2026-10-15T12:00:00.000Z

Your wallet shows this text before you sign it. Signing is free and moves no funds. Because the URL and payTo are inside the signed text, the signature can’t be reused to list a different endpoint or to claim someone else’s address.

Sign-in itself is a separate Sign-In-With-Solana message with a single-use nonce; it proves who is using the dApp, while the listing signature proves who gets paid.

Why payTo is the identity

Money is the one thing a seller can’t fake. Whoever controls payTo receives every payment, so tying the badge to it means the badge follows the money. A copycat can clone your API’s responses, but it can’t point its 402 at your address and still get paid. The same proof is what lets Axonpay’s facilitator settle to that address: it only settles to listed payTo wallets.

What verification doesn't cover

  • Quality. That is the job of Axon Score.
  • Real-world identity. Nobody is KYC’d.
  • Addresses that can’t sign messages, such as a multisig vault PDA. List from a payTo you can sign with, or wait for program-based verification.