Price the outcome, not the rail
Agents can parse a deterministic quote, but they still need a useful result. Keep the endpoint description, schema, amount, asset, and network aligned.
Set an x402 price agents can understand before you publish it.
Model your infrastructure cost, retry overhead, facilitator fee, desired gross margin, and agent budget. Then verify that the resulting price is consistent across your manifest, OpenAPI, and HTTP 402 challenge.
This is a planning estimate, not a revenue guarantee. It does not certify an endpoint, predict demand, or replace accounting, tax, facilitator, or network review.
Provider inputs
Use successful billable calls as volume. Enter your actual facilitator fee if applicable.
Suggested starting price
-
Enter assumptions
-break-even per successful call
-cost per successful call
-estimated monthly gross
-estimated monthly net after fee
Next actions
- Run the calculator to see provider-specific actions.
Stay inside the buyer policy
If the price exceeds a realistic task budget, consider a smaller response tier, lower-cost route, or a supported upto/batch design.
Prove the published price
Run Ontario’s free catalog scorecard after changing pricing so public metadata and payment challenge evidence do not drift.
Protocol references: x402 pricing guidance and network and settlement schemes. Ontario does not endorse a pricing level or guarantee demand.