Monetization rules determine which matching requests require payment. Each rule defines a domain, URL, price, and audience.
Choose a scheme based on when you determine the charge:
| Scheme | x402 scheme | Behavior |
|---|---|---|
| Fixed | exact |
Charges the same price for each request with fixed inputs. The gateway settles the signed amount. |
| Variable | upto |
Authorizes a maximum price. Your origin discloses and settles the actual amount. |
Prices and settlements use atomic units. One atomic unit equals $0.000001.
Use these conversions when setting prices:
| Amount | Atomic units |
|---|---|
| $0.001 | 1,000 |
| $0.01 | 10,000 |
The minimum settlement amount is $0.001, or 1,000 atomic units. The maximum price is $100, or 100,000,000 atomic units.
Choose which visitors the rule charges:
| Audience | Behavior |
|---|---|
| Everyone | Charges all traffic matching the URL and advanced conditions. |
| Verified Bots | Charges matching bots identified through BotBase. |
By default, a rule charges GET requests. You can select multiple HTTP methods for one rule.
Advanced conditions refine which requests the rule charges. You can match these request properties:
| Property | Match input |
|---|---|
| Header | HTTP request header |
| URI Query String | URL query string |
| User Agent | User agent value |
| X-Forwarded-For | X-Forwarded-For header value |
| IP Source Address | Source IP address |
| Continent | Request continent |
| Country | Request country |
| European Union | European Union location status |
| Cookie Value | Request cookie value |
| Body | Request body (Enterprise only) |
| Body size | Request body size (Enterprise only) |