Sell to agents with one well-known file.
No account, email, API key, wallet custody, or manual registry review is required for domain-controlled enrollment. Publish the AgentResolver provider manifest on the same origin as your x402 service.
1. Publish
Serve /.well-known/agentresolver-provider.json from your domain. It declares your same-origin routes, Base-USDC payment identity, and acceptance of the provider success-fee contract.
2. Get routed
When your route is discovered through a supported capability catalog, AgentResolver can verify the manifest and return your route in constrained procurement. Hard buyer constraints still win.
3. Prove the sale
A selected domain provider receives an x-agentresolver-attribution-id handoff. After a routed sale, submit the buyer transaction for independent Base-USDC verification.
4. Pay on success
The provider success fee is 2% of verified routed GMV with a $0.001 minimum. AgentResolver adds no extra buyer fee. The exact provider fee amount is attribution-bound to prevent simple proof replay.
Proof, not claims
AgentResolver verifies the buyer-to-provider Base-USDC settlement and the provider-to-AgentResolver success-fee transfer independently. The buyer's wallet remains outside AgentResolver custody and only the caller can authorize provider spend.
Optional deeper verification
The paid /api/provider-launch-check remains available for a deeper x402 readiness/payment-contract audit. It is not an admission gate for domain-controlled enrollment.
Manifest example · Machine onboarding · Commercial contract · Provider API