E-commerce
August 19, 2026
The profile “VendeeX Review: Identity & Governance for AI Shopping Agents” positions the product between the consumer and AI shopping agents: mandates, caps, category rules, portable identity, audit trail, delegated restocking without giving up all payment authority. Surface absent from the hook. Capabilities: spend governance, returns, audit trail, product search, automated checkout. Retailers: all merchants. Regions: global. Directions: sign up, create an identity, set rules, let "the" agents search and buy without purchase-by-purchase confirmation, review the log, manage returns in the platform. Autonomy on the checkout tunnel side, in the parent directory: automatic purchase. No Gross Merchandise Volume (GMV). No perfect order rate. No ChatGPT or Gemini audits. This article either. Putting VendeeX in an "agent channel" indicator means budgeting for an identity kit for other LLMs, or a Magento, which the two publisher pages do not document. Here, VendeeX is the agent. It is not yet the promised computer: Coming soon.
Vendee Labs presents VendeeX as its first product: a shopping agent that runs on the buyer's computer. Ranking that cannot be paid for to rise. Signed trace, owned by the user. Identity, memory, cart, and history remain on the machine. Avatar: preferences, caps, rules, folder. Free, forever, no account, no email, Mac, Windows and Linux, card Coming soon. Target revenue: affiliate and a share of payment provider fees already paid by the merchant, not an extra cost to the buyer. The commission figure is, she says, removed from the ranking engine and only opens after the decision. The vendeex.com website announces that the beta is closed: a private VendeeX, initially local, on your machine. Specs (Apple Silicon, Windows 11 plus 8GB GPU, Linux 16GB, about 15GB disk). No ads, no telemetry, commission-blind ranking. Governance engine: every action is checked against your rules before arriving, then written to a sealed folder. OpenJarvis (Hazy Research and Stanford SAIL, Apache 2.0) as local foundation, without Stanford affiliation. Coming soon. Two texts. One logo in the directory. Not UCP. Not ACP. Not a Shopify Agentic button.
If the idea of a software buyer is new: what agentic commerce is. The 2026 calendar: what has been delivered. Other sheets: AI shopping agents. Official totals remain human shopping journeys: e-commerce statistics 2026.
Summary
An identity layer pasted on an agent that hasn't come out
VendeeX, on the publisher's site, is an on-device shopping agent. The directory classifies it as a governance tool for other agents. It is not the same contract.
Layer | What the two publisher pages describe | What the directory does with it |
|---|---|---|
Product | Primarily local shopping agent, Avatar, Coming soon after a closed beta | Identity and governance between the buyer and "the" AI agents |
Account | Free, accountless, no email | Step 1: register, create a digital identity |
Purchase | Pre-action controls, limits the agent cannot exceed, payment partners that settle | Automatic purchase, purchase without order confirmation, returns within the platform |
Scope | Promised dated public ledger, Mac, Windows, and Linux, Jersey | All merchants, global, wallets and agent creators |
The directory is correct regarding the vocabulary: mandates, spending limits, audit. Vendee Labs treats this as the hard problem, ahead of capability. The directory is incorrect if we read "portable across shopping agents" as an intermediary layer for Gemini via UCP or ChatGPT via ACP. The Avatar, on vendeelabs.com, persists "wherever Vendee Labs goes next": their versions, not an OpenAI OAuth. Platform framework: what platforms need to change. Here, you do not enable anything in the Magento admin. A human installs, or does not install, a "Coming soon" software.
Search filters and checkout tunnel are not two VendeeX SKUs: task-specific shopping agents. Product search on the map is not a PIM. Automated payment is not an ACP specification. Expense governance, yes, in the publisher text. Returns via the platform: directory phrasing, absent from the two URLs.
A merchant who "chooses the VendeeX agent" like a payment provider has misread the filter. You are not the merchant of record for a VendeeX chat. At best, later on, a buyer arrives with tokenized authority and post-factum affiliation. This is not a channel you turn on this week.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
vendeelabs.com: the agent, the Avatar, not a merchant kit
The home page is a manifesto rather than a specification. It is enough to dispel the misunderstanding "VendeeX = identity layer for ChatGPT".
Local-first: the agent runs on the buyer's machine. Identity, memory, cart, purchase history stay there. Vendee Labs says it didn't do this for privacy aesthetics: an actor that monetizes attention cannot copy this without breaking its model. Publisher's pitch. Not an exfiltration audit.
Governance: checks before every action. Blind ranking with regard to commission, the engine does not have the figure. Signed dossier, exportable, readable by you. Tokenized authority: the counterparty sees a permission to conclude the purchase, not the identity. Limits and validations that the agent cannot override. "Language-safe" consent (secure regardless of language): claim, all languages supported, no list here.
Avatar: identity within the exchange layer: preferences, limits, rules, dossier. Not a Shopify ID. Not a Merchant Center profile. Vocabulary: glossary of agentic commerce.
"Commerce grew protocols": payment tunnel and cart rails are emerging, what runs on top remains open. This is the only protocol neighborhood of the two URLs. This is not "we implement the UCP". This is not the Stripe ACP. Named rails: how the protocols differ.
The economic model is written in plain text, and it contradicts the directory slogan "neutral trust framework". The buyer does not pay. Vendee Labs aims for affiliation and a share of the merchant's payment provider fees. Rates vary. The incentive to steer exists, it says, "exactly as it does anywhere else". The claimed difference: structurally impossible to act on it, because the ranking does not have the figure. Architectural claim. Not a ranking metric. A dated public registry of every connected network and merchant is promised: scope, not pricing. We do not have this registry on the page. Do not budget for it as an all-merchant graph.
Jersey, data protection law modeled on the GDPR, adequacy recognized by the European Commission: publisher's legal framework, not your impact assessment. Darryl Carlton (governance, signed chain of warrants, file to the buyer) and Ross Gardiner (local-first, 25 years of checks): founder quotes. We do not make this a service commitment.
The architecture lists other types of exchange (sell, give, rent, borrow, barter, ask) and other scopes (organization, B2B, mobile, hosted). The page says: none of this is available today; this is what the architecture must support. Buying is the first product. The product card, on the other hand, says "Coming soon". Hold both phrases. Do not install a fictional B2B kit.
Internal journey: a hosted browser version first (discovery, multi-seller carts, multi-item checkout), public demonstration, then shift to local-first. The beta has done its job, the page says, and is retired. This matches vendeex.com. This is not the directory user guide (registration, agents buying). Flows, if a listing ever reaches you: what a machine needs to compare. Here the machine is not yet at your customers' end.
Three conversations: investors, merchants ("intent, no placement auction"), payment partners (signed permissions, tokenized authority, dossier, "we create the transaction, your infrastructure settles it"). The merchant is not invited to place a VendeeX pixel. They are invited to collect later a flow that a local agent would have decided upon. This is not an Agentic Storefronts integration.
vendeex.com: closed beta, desktop Coming soon, not a web chat
vendeex.com is no longer a James demo. It is a landing page: beta over, thank you, we built a local-first product on your computer. Coming soon. The directory, however, still describes signup and purchases without confirmation. Two calendars. One logo.
Hardware specifications are the most concrete detail of the two URLs, and the directory does not show them. macOS: Apple Silicon M1 or newer (including Pro, Max, and Ultra), 16 GB of memory or more, macOS 13+, about 15 GB disk. Windows: 11 64-bit, 16 GB, dedicated GPU with 8 GB VRAM, Intel 8th generation or Ryzen 2000+, same disk space. Linux: Ubuntu 22.04 or equivalent, same memory, GPU, and processor as Windows. This is not "global" like a payment tunnel map. This is a development laptop. An iPhone buyer is not on this list. The listing does not even label the computer. Treat the surface badge as absent, not as an iOS app.
Three product prohibitions: no ads (purchase data, profile, search history remain on the machine); no tracking (identity, memory, cart, purchases on the device, no telemetry, no cloud sync); no kickbacks (commission-blind ranking, the best result wins, not the one who paid). Claims. This is not a Honey audit. Operator clicks your HTML from a cloud browser. VendeeX, in these pages, rejects the cloud model. Two paths. One same word: agent.
OpenJarvis: local open-source framework, Hazy Research and Scaling Intelligence Lab at Stanford SAIL, Apache 2.0 license. Vendee Labs (Jersey) Limited states it is neither affiliated with, sponsored, nor endorsed by Stanford. They have hardened it: no more cloud model, no more messaging channel, no more path that would send your data off-machine. Then the governance engine, the "our" part: the Avatar answers only to you. Every action, rules first, sealed folder second. MCP is not named. A local foundation is not a merchant tool server: MCP and API for e-commerce.
"Coming soon, more from VendeeX": the page does not date the general availability. vendeelabs.com doesn't either (Coming soon on the product card). Do not copy the directory's instructions like a 2026 specification sheet. Verify, on launch day, a Mac, Windows, or Linux software, not a directory signup.
We do not have, in these two links, a figure of "1 billion products" nor a named concierge. If an old web demo displayed them, it is not the source cited here. Do not recycle them.
At home: nothing to turn on, a reading list for later
At your end, this week, VendeeX is not dropping any pixels. Three possible artifacts later, none is an admin button today.
A listing in a registry: promised, public, dated, scope criterion. Absent from the page. Without it, all merchants are just a dot. If you enter it one day, price, stock, identifier, variants: the same discipline as elsewhere. This is not Google Merchant Center.
A merchant checkout funnel or a payment provider: "We create the transaction. Your infrastructure settles it." The local agent does not market itself as a VendeeX wallet. Checkout funnel: agents for the checkout funnel. Automatic purchase on the parent sheet is not this phrase. A human, a cap, a provider: three actors. The directory only shows a single verb for it.
Affiliation after ranking: the commission path opens after the decision, says Vendee Labs. You can appear, be chosen, then generate a fee. This is not a placement auction in the ranking, it says. It is still affiliation. Ask for the network, the rate, the cookie. Do not sign "blind to commission" as "free for the merchant".
Magento firewall: out of scope as long as the agent does not retrieve your HTML. First local plus "data never leaves your machine" plus a merchant registry: two phrases that will, one day, have to explain how the catalog reaches the computer. The two URLs do not describe a gateway. We are not inventing one. Store logs: what to log if you are still mixing Operator and VendeeX in the same ticket. Today, the VendeeX ticket has no User-Agent at your end.
Product search on the map: the agent, if it comes out, draws up a short list. Product search is not your raw material FAQ. An empty attribute remains an empty attribute, regardless of the Avatar.
Returns "directly through the platform": user manual for the directory. Absent from vendeelabs.com and vendeex.com. After the purchase, the customer service and the reason code remain yours, or the provider's, not a VendeeX button sourced here. Breakages: where agentic commerce still breaks.
Shopify theme: useful if, later, checkout takes place on your web checkout funnel. A Shopify storefront readable by a LLM does not turn on VendeeX. It helps any agent that still reads a product sheet.
Not UCP, not Operator, not Honey, not a middle layer
Do not merge the logos. Four contracts, one and the same word: governance.
Surface | Where checkout takes place | On your end |
|---|---|---|
VendeeX (publisher) | Payment partner infrastructure or merchant checkout funnel, known as the home page; Coming soon product | Nothing to install. Registry and affiliation, later, if they exist |
VendeeX (directory) | Automatic purchase, platform returns, portable identity to other agents | A kit that the two URLs do not sell |
Gemini via UCP | Google Surface, US listings, waiting list | Merchant Center, not a 15 GB software |
Operator | Your theme, buyer's card, human pause | Web Application Firewall, JavaScript, 3-D Secure. Not primarily local |
Honey and classic affiliation | Your promo field, buyer's card | Codes. The VendeeX ranking is said to be blind to the rate, not out-of-network |
A sales pitch of "we will get you into VendeeX" can sell a directory listing, an affiliation promise, or an identity layer for other LLMs. Three deliverables for a single word. Ask which one. The two URLs only sell the second one, and even then: Coming soon, registry unpublished.
Honey injects a code. VendeeX, here, does not document any coupon. Bargain hunting: bargain hunting is not the job of the manifesto. Klarna is a payment schedule. Tokenized authority is not a Pay in 4. Buy with Pro processes payment in the chat with another operator. Do not paste automatic purchase on all three.
Price comparison, if a local ranking ever exists: price comparison. Blind to commission means: the rate does not influence the ranking order. It does not mean that two up-to-date files exist. An expired price remains an expired price.
What this sheet does not measure
This profile does not measure anything that counts after "Get in Touch" or after "Coming soon".
Volume: no gross merchandise value (GMV), no users, no desktop installation rate. The closed beta is not a published panel.
Ranking accuracy: commission-blind is an input constraint. This is not a "best result" rate. No A/B testing.
Merchant coverage: "all merchants" and "millions" elsewhere at the publisher (page not cited) are not the dated registry promised. We do not have the file.
Returns and disputes: signed audit trail on the buyer side. Card reason code, customer service, 3-D Secure: absent. The directory managing returns "through the platform" has no URL here.
Interoperability: portable identity to ChatGPT, Gemini, wallets: directory hook. Avatar "across every release" Vendee Labs: publisher text. Two scopes.
Do not budget this profile as an agent channel with a known cost per acquisition. We do not publish one. A Verified profile does not buy a ceiling, nor Mac software.
"Works for you. Only you.", "the hard problem isn’t capability", "free forever, no catch": slogans. The homepage admits affiliate incentive. Keep both. Do not make this an ethics prize list.
Automated payment plus automatic purchase on neighboring cards do not constitute an autonomous order volume. "Coming soon" plus pre-action controls are the story consistent with the publisher. The user guide without purchase confirmation is directory-level. We leave it to the directory.
Language-safe consent, sealed file, tokenized authority: serious vocabulary, zero public evidence of third-party implementation. A risk committee copying this into a 2026 policy is copying a marketing site.
Three tickets, not five capabilities
This week, by business, not by logo.
Internal naming: forbid the slide "VendeeX = identity for all agents" without saying: local agent Coming soon, not a ChatGPT intermediate layer. Separate Operator (cloud browser), Honey (coupon), Gemini (via UCP).
Payments and affiliation: if a partner promises VendeeX volume: which network, which rate, which registry, which desktop general availability date. "Blind to commission" does not cancel the affiliation invoice after the fact.
Catalog: nothing VendeeX-specific. Price, stock, identifier, freshness. This work serves the UCP, the ACP, marketplaces, and potential local ranking. It does not depend on Jersey.
The single test: would this work still be useful if VendeeX never left Coming soon and Gemini and ChatGPT remained? A clean feed, yes. An exclusive "identity VendeeX only" connector, no. Postponing a named rail is not postponing a rotten file.
Name the owners: merchandising or feed for readability, payments for an eventual service provider, legal if someone brandishes Jersey as a commercial argument, not a single "VendeeX agent owner".
If you only have one hour: read the Coming soon card and the phrase "no account". Read the directory user guide (registration, automatic purchase, platform returns). The two do not describe the same product. Do not follow the four directory steps as an identity specification sheet.
Investors and "Get in Touch": off-topic for merchants. A ross@ email is not a catalog integration. Do not put it in the operating procedure.
You do not turn on the VendeeX agent
You do not turn on "the VendeeX agent" like a channel. Buyers, if any, will download 15 GB of software onto a 16 GB computer. You maintain a readable catalog and, potentially, an affiliate agreement. The dots are not buttons.
If a seller promises to place you "in VendeeX", ask for: a directory listing, a publisher registry, a payment provider share, an identity layer for other agents, or computer software. Five deliverables for a single word. The two URLs only document a Coming Soon product plus an affiliate and provider model.
The UCP and ACP are chosen elsewhere, if the mechanism is a Google or OpenAI-Stripe mandate. For VendeeX, the public protocol is not named. The homepage says that the rails are being laid and that what rolls on them remains open. Postponing the UCP is not postponing a flow. Postponing VendeeX, today, is postponing a slide.
After a possible provider settlement, it is your after-sales service, your 3-D Secure, your return. The directory did not collect the payment. The sealed file belongs to the buyer, says the publisher. It does not replace your proof of chargeback. Do not attribute an unpaid debt to it that you have not seen in a contract.
Wallets and agent creators in the directory hook: audience. vendeelabs.com speaks to payment partners, not to a publisher who would integrate the Avatar into Claude. Do not build an integration roadmap on a directory sentence.
An on-device governance index, not a ranking
VendeeX is fragmenting: initially a local manifesto, beta web removed, computer Coming soon, confessed affiliation model, directory listing that actually acts as an identity layer for other agents. This listing is a starting point: buyer agent first, governance as the engine of this agent, not an OAuth layer for ChatGPT.
Treat it as an index: which artifact (software, Avatar, registry, affiliation), where the payment takes place (provider or merchant payment tunnel, not a sourced VendeeX wallet), within what timeline (Coming soon, not the four steps of the directory). Three questions. Not an agentic ethics prize list.
You can ignore VendeeX and hold the UCP. You can refuse affiliation and wait for a dated registry. The directory does not decide. Your flow and your named rails, however, do decide.
Next, open ChatGPT (via the ACP) and Gemini (via the UCP). Lay down the contract, not the spending governance badge. VendeeX is not the third rail. For now, it is a promised computer.
The "payment and identity" family of the parent directory mixes Klarna and VendeeX. A split payment and a local agent. Separate from the very first line of the committee. An Avatar cap is not a Pay in 3.
Workflow first, software next
The owner is not "VendeeX growth". It is merchandising or plus feed, if someone signs affiliation, payments. A single owner mixes Coming soon and auto-purchase.
Buyers come according to their machine, not according to the directory. You do not turn on five capabilities. You keep a price that you accept to see in any ranking, including a ranking that claims to be commission-blind.
If the committee wants a figure: there is none here. 15 GB of disk and 16 GB of memory is not gross merchandise value (GMV). Jersey is not a conversion rate. A channel is budgeted on orders and fees, not on a buyer-first slogan.
The test for the following week: a real feed (price, stock, ID), an internal phrase separating VendeeX from the UCP, a question to the partner ("published registry, yes or no"). If you do not have that, you do not have an agent channel. You have a listing.
Get in Touch for merchants, on vendeelabs.com, promises high-intent buyers without placement bidding. This is a commercial argument. It is not a queue that your customer file can see today. Do not create a "VendeeX Q3" campaign on a Coming soon map.
Frequently Asked Questions
Is VendeeX an identity layer for other buying agents?
In the directory, yes: between the consumer and the agents, portable identity, wallets, agent creators. On vendeelabs.com and vendeex.com, VendeeX is the local buying agent, Avatar for their versions, Coming soon. The middle-layer classification is editorial.
Does it handle payments on its own?
The parent directory labels it automatic purchase and describes a purchase without confirmation per order. The publisher describes pre-action controls, non-bypassable caps, and payment partners that settle. Product Coming soon. Do not sign off on automatic purchase as a volume.
Do I need to create an account?
The directory user guide says sign up. The product card says free, no account, no email. Two texts. For the announced computer, the publisher chose the second one.
Is VendeeX UCP or ACP?
No, not in these two URLs. The homepage notes that commerce protocols are emerging. It does not implement Google or Stripe here.
Is VendeeX Operator?
No. Operator controls a remote browser and often stops at the cart. VendeeX promises a local model, without cloud synchronization. Two architectures. One same word: agent.
Are returns managed in VendeeX?
This is step 4 of the directory. It is not in vendeelabs.com or vendeex.com. Treat it as directory-related.
What to do this week?
Separate the identity-intermediary slide from the local agent Coming soon. Do not follow the directory registration. Maintain the flow. Postpone an exclusive VendeeX connector. Check UCP and ACP elsewhere if the rail counts.
Sources
Enzo
August 19, 2026
