Price
Set a price for licensed machine access, with optional different prices for specific paths.
AI REVENUE
Turn machine access into measurable commerce.
Set a price for licensed machine access, present an x402 payment request, and count revenue only after the payment is successfully settled.
Settle
Payments are verified and settled through the configured x402 payment facilitator. AIWebSignals never holds customer funds or private keys.
Attribute
Successful settlement evidence becomes measured revenue. Quotes, challenges, verifies, and failed settlements do not.
How a paid request works
1 · ChallengeYour site requests the payment requirement for the protected resource.
2 · VerifyYour site verifies the client's PAYMENT-SIGNATURE before serving the resource.
3 · ResourceYour site serves the protected resource itself. AIWebSignals never proxies the content.
4 · SettleAfter the resource succeeds, your site requests settlement and returns PAYMENT-RESPONSE.
Evidence boundary
AIWebSignals does not call a quote revenue. It does not call a valid signature revenue. It records measured revenue only after the configured facilitator reports successful settlement. Fiat value is not inferred from a token symbol.
Payer wallet addresses and PAYMENT-SIGNATURE payloads are processed transiently and are not persisted. Successful transaction identifiers are retained as settlement evidence.
Set up paid machine access
Use the connection's management key to configure pricing. Keys entered here stay only in this browser tab and are not sent to analytics.
Optional network-specific x402 settings. For EVM EIP-3009, confirm the token name, version, and transfer method required by your payment setup.
One-time revenue key: —
Preview challenge
Status
No request yet.
WHY THIS LAYER EXISTS
A human pageview and a machine request are not the same event.
The difference runs from data and protocols through identity, permission, intent, and value. The foundational explainer shows where AIWebSignals fits in that stack.