Aura
402
See what your agent
reveals before it pays.
CA: TBAInspect requests locally.
Follow a public mainnet payment.
The amount is
only one detail.
An API request has a destination, a purpose and sometimes an identifier. Adding a payment can connect that context to a wallet.
Aura starts by making those relationships easier to inspect. Before you sign. Before you forward a header. Before a request becomes a trail.
Open a real-format exampleA local view of request metadata.
No claim of hidden onchain activity.
One request.
A few important decisions.
The x402 conversation, with a place to pause.
Start with the resource.
A client asks for an API resource. That request can already include a path, query parameters and network metadata.
Client ā†’ Resource serverProtocol walkthrough. No payment is submitted by this page.
Keep the terms.
Question the extras.
Query parameters and free-text descriptions can reveal why someone is paying. Inspect them locally, then choose what belongs in a research copy.
Removing fields from a report does not anonymize the original request or the chain.
Inspect a sampleOpen infrastructure.
Explicit boundaries.
Privacy Studio recognizes Solana payment terms, including the mainnet network ID solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp while keeping chain identity separate from payment support.
A working payment route needs an appropriate token, a compatible facilitator and verified settlement. None of those are implied by a chain label.
Useful before
the first signature.
Start with the tools that work in your browser.
Read the header
Decode a PAYMENT-REQUIRED value or inspect its JSON structure using the x402 schema.
Review the context
Find query parameters, descriptions and payment identifiers that deserve a second look.
Keep a research copy
Choose what to omit and export a report. No payload history is stored by Aura.
Does x402 make a payment private?
No. It provides a payment conversation for resources. Confidential settlement needs additional mechanisms. Aura has not deployed those mechanisms.
What happens to text I paste?
Inspection runs in this browser tab using the x402 schema. The app does not transmit your input to a server or save it in local storage. You can clear it or reload. Do not paste private keys or payment signatures.
What does the demo spend?
Payment Lab uses 0.01 real USDC on Solana Mainnet by default. You can switch to Devnet to use test USDC. The service displays its recipient and fee payer before you sign.
What still needs to be built?
Payment Lab supports public settlement on Solana Mainnet and Devnet. Privacy-preserving settlement needs separate implementation and review.
Bring a request.
Leave with more clarity.
Open Privacy StudioNo wallet required for inspection.