AgentTrust Verify

Service status

Everything on this page is either read from the running configuration or marked pending verification. Nothing here is claimed as confirmed on the basis of configuration alone.

Loading live configuration…

Readiness checklist

Every step is externally verifiable and stays pending until it is proven outside this application.

  1. 01Deploy the service and confirm /.well-known/x402, /openapi.json and /llms.txt all return the same payTo, price and challenge tag.Pending
  2. 02Confirm the payTo address is opted in to the USDC asset of the network in use (see the receiving address panel above).Pending
  3. 03Make one paid Testnet request end to end and open the returned transaction id in the Algorand explorer.Pending
  4. 04Confirm the USDC balance at the payTo address increased by the request price.Pending
  5. 05Switch ALGORAND_NETWORK to mainnet and re-check that the config panel above reports no errors.Pending
  6. 06Confirm the payTo address is opted in to Mainnet USDC asset 31566704 before taking Mainnet payments.Pending
  7. 07Make one real Mainnet paid request and confirm the settled transaction on the Mainnet explorer.Pending
  8. 08Confirm the endpoint is listed in the x402 Bazaar with extra.tag = x402-global-challenge.Pending
  9. 09Confirm the request is attributed to the challenge and appears on the leaderboard.Pending

Competition state

Current state: NOT TESTED. A state advances only on recorded external evidence — never because the code or the configuration exists.

  1. 01NOT TESTED

    Not proven

    Current state. The configuration validates and the endpoint serves a real HTTP 402, but no settled payment has been recorded.

    The default state. The service exists and its configuration validates, but no payment has been proven.

  2. 02TESTNET VERIFIED

    Not proven

    No Testnet settlement has been recorded. Nothing here is inferred from the code being complete.

    Requires an actual successful Testnet x402 payment through GoPlausible and a paid /api/verify response.

  3. 03MAINNET READY

    Blocked

    The Mainnet configuration does not validate, so the service is not ready to take Mainnet payments.

    Requires the complete Mainnet configuration to validate: Mainnet CAIP-2, USDC asset 31566704, payTo, facilitator, challenge tag and Bazaar discovery.

  4. 04MAINNET LIVE

    Not proven

    No Mainnet settlement has been recorded.

    Requires a real Mainnet payment through GoPlausible, a successful paid /api/verify response, and confirmation that USDC reached the payTo address.

  5. 05BAZAAR VERIFIED

    Not proven

    Discovery documents are published, but a Bazaar listing is confirmed by the Bazaar, not by this service.

    Requires the endpoint actually appearing in the x402 Bazaar.

  6. 06LEADERBOARD VERIFIED

    Not proven

    No leaderboard attribution is claimed. A payment can settle and still not count if the tag is not attached.

    Requires the merchant or payment actually appearing under the x402-global-challenge source/filter.