WF Pay — Payments That Fit the Workflow
Exploring a common payment experience for connected agents and services.
Why Explore x402?
Bring the cost of a request into the conversation.
An agent may need several paid resources to finish one assignment. Understanding
each resource's cost and keeping spending within a budget should be a consistent part of the experience.
Our starting point is the request.
WF Pay explores payment flows that sit close to service discovery and use. The aim is to make a resource's price and conditions visible before the workflow commits to it.
Open protocols can provide a common language for these interactions. Wanted Family is interested in a practical experience that participants can understand, inspect, and control.
1
A Consistent Payment Experience
Bring payment details into a shared format so a workflow can understand the cost of a service and apply the appropriate spending rules.
2
Routing for the Task
Different assignments can involve different participants. Keep the intended recipient, the approved amount, and the payment conditions connected to each request.
3
Access That Matches Usage
Explore payment models suited to a single request, a working session, or an ongoing relationship between services and their users.
Designed Around
Agent Workflows.
A direction for open, programmable payment flows
Participation & Recognition
Explore incentives with clear eligibility and published conditions.
Connected networks
A common experience across participating services
Practical integrations
Build around the payment options a workflow needs
Room to extend
Support specialized use cases through reusable components
Resource discovery
Make paid services easier to identify and evaluate
Bring WF Pay into the Conversation.
Start with a useful connection.
We are exploring a straightforward path from a service request to an approved payment.
The intended experience keeps pricing, permissions, and spending limits close to the task. Contact Wanted Family to discuss access and integration plans.
Understand the rules for any future participation program.
Keep payment status connected to service delivery.
Use open standards to describe the payment interaction.
Plan integrations around supported networks and availability.
Connected Commerce
Resources for people and their agents.
A workflow may bring together research, processing, and specialist help. WF Pay explores how to
make those costs understandable within the overall assignment.
Controlled Agent Spending
Allow agents to work within an approved budget. Keep the purpose, amount,
and recipient of a payment connected to the task that needs it.
Keep account permissions visible
Understand the settlement method
Choose where approvals are required
Align resource cost with actual usage
Connect payments to the relevant service
Give Digital Resources a Clear Price
Explore paid access for useful content and services.
Different resources need different access models. Wanted Family is exploring how websites, data providers, APIs, and
agent tools can describe their price and conditions consistently.
