Status update — October 4, 2026: WebAZ is publicly launched and under active development. Direct Pay is live: buyers pay sellers off-platform, while WebAZ records order state, acknowledgements and payment evidence. Public product browsing does not require an account; registration currently uses invitations. The production/core repository is private, not open source. See the current integration documentation for available interfaces and authorization boundaries.
For Direct Pay, WebAZ does not hold the principal and does not verify the payee or payment method.
AI makes individuals more capable.
That is the easy part to see.
A developer can move faster. A designer can explore more directions. A solo operator can coordinate work that used to require a small team. A seller can use agents to describe, list, and answer questions about products.
But capability alone does not become a market.
It still needs shared rules, visible records, and accountable boundaries.
That is the space WebAZ is trying to build.
WebAZ is not only looking for users
For this stage, passive users are not the most important people.
WebAZ needs early participants who are willing to help shape the system while it is still small, inspectable, and unfinished.
The first group is builders.
Developers, designers, operators, content creators, AI workflow makers, and MCP tool builders can contribute to the surfaces that make WebAZ usable:
- protocol and MCP interfaces;
- product and order flows;
- task records and contribution evidence;
- UX, copy, education, and onboarding;
- seller and buyer workflows;
- public explanations of what WebAZ is and is not.
The point is simple: work should not disappear inside chats and private workflows.
If a person helps build something meaningful, there should be evidence, boundaries, and accountability around that work.
WebAZ also needs real sellers
A commerce protocol cannot be tested only with demos.
It needs people who are willing to list real products or services, expose the rough edges, and help discover what agent-era commerce actually requires.
WebAZ already supports Direct Pay.
That means a buyer can see the order and seller payment instructions, while the seller receives payment directly.
In Direct Pay, WebAZ does not hold the buyer's payment principal.
For Direct Pay, WebAZ does not verify the payee or payment method, guarantee payment or delivery, or issue seller refunds.
WebAZ records the product, order, confirmations, and boundaries around the transaction.
Direct Pay is a live, off-platform buyer-to-seller payment path. This description is specific to Direct Pay, not a claim that every WebAZ payment rail has the same custody or authorization model.
What kind of participant fits this stage?
You might fit if you are:
- a developer or product contributor who wants evidence-backed participation records;
- an AI workflow builder exploring agent-native interfaces;
- a designer or operator who cares about trust, consent, and accountability;
- a small ecommerce seller willing to test real listings;
- a technical writer or community builder who can explain complex systems clearly.
WebAZ is publicly launched. Public browsing is available without registration; invitations are currently required for registration. The production/core repository is private.
No reward promise. No token story. No investment framing.
The first goal is more basic: help builders and real sellers meet inside shared rules.
Start by browsing WebAZ. To register, use the invitation-request route described in the current integration documentation. Builders can inspect public tasks and submit suggestions for maintainer review; submission is not automatic acceptance or a payment entitlement.
Code is Rule. Protocol is Trust.
Editorial update: this article was revised with AI assistance to correct launch status and current product boundaries. The original publication date is retained.
Top comments (1)
WebAZ is in invite-only pre-launch. If you want to try it, reply/DM "invite" for access.