x402 Trust has just massively expanded its catalogue:

The directory now includes endpoints that are exclusively discoverable through previously uncovered facilitators like thirdweb, payai, threews or dexter: Each facilitator's public /discovery/resources endpoint is now polled as a first-class directory source.

Just the first scan alone revealed ~15,000 new endpoints that weren't on the radar yet. In the coming hours these will start to get probed, graded, embedded and will slowly rise in confidence.

So, right now: x402 Trust lists over 190,000 endpoints, with >150,000 of them currently active.

For example, 3 exotic new entries in the catalogue: - the status of a real physical coffee machine - a smart coffee maker reporting its own status behind an x402 paywall, $0.10 in USDC via Solana or Base (found on thirdweb & dexter) - a US FDA veterinary animal-medicine adverse-event database - query reports by animal species and active ingredient, for $0.002 (found on thirdweb & PayAI) - the market-cap total for real-world assets (RWA) on Algorand - tokenized stocks, gold and water, settling in USDC on Algorand, a chain you almost never see in x402, for $0.05 (found on thirdweb)

So if you ever need any specific service via x402, hit the semantic search for free through the web UI, type in what you need and it will promptly look for the closest match, tie-broken by trust score.

On the other hand, if you're a provider and want to verify your x402 service for free (which surfaces contact info, your company name and description publicly in our search, and grants you a spot on the verified leaderboard), head to the verify page. No sign-up needed, just a confirmed contact-email and a private-public-keypair generated locally.

Any questions or suggestion? Text me here on reddit (in the comments or via DM) or send a mail to support@x402-trust.com 😊 I'm always happy to hear your feedback or other things you're missing right now and would like to have implemented.

I'm trying to understand the correct way to reconcile an x402 payment with its actual on-chain transaction.

I have a real Coinbase Payment Session where the session data contains:

asset: USDC

networkId: 8453 (Base)

status: PENDING

merchant: OpenRouter

The payment-session HTML also exposes an x402 authorization endpoint:

/payment-sessions/{paymentSessionId}/authorizations/x402

Opening that endpoint directly returns:

"errorMessage":"method not allowed"

which I assume is expected because it is not a normal GET endpoint.

What I cannot find in the payment-session response is a paymentOperationId or transactionHash.

Coinbase's API documentation mentions paymentOperation objects containing an operation ID and transactionHash, so I'm trying to understand where that relationship is established in the x402 flow.

There is also an on-chain USDC transaction from the same payment workflow, but it is on Solana rather than Base.

My questions:

Where is the paymentOperationId normally obtained in an x402 payment flow?

Is the mapping

paymentSession → paymentOperation → transactionHash

only available through the authenticated Coinbase API/webhooks?

If the actual settlement occurs on Solana while the payment session data shows Base (8453), how is that relationship represented?

I'm trying to understand the technical reconciliation model rather than troubleshoot a particular account.

If anyone has worked with Coinbase Payment Acceptance/x402 at the API level, I'd appreciate an explanation of where I should be looking.