- Seller's agenttheirs, or ours
- Seller MCP + CLItyped tools
- One validated corecatalogue · escrow · trust
- User MCP + CLItyped tools
- Consumer's agentany MCP host
No consumer app. No seller dashboard. No checkout button. The agent is the interface.
A small business with a few hundred products and nobody to build software. Its agent publishes what is in stock and accepts the orders that arrive.
One shared format for what a product is, money held in escrow until delivery is proven, and refusals precise enough that software can correct itself and try again.
Someone's own assistant, running on their own hardware. It compares every seller at once, and can spend only what its owner already authorised.
That is the whole product. XEKTA is not the assistant a person talks to, and not a shop anyone visits — it is the rail underneath both, so the two programs can trade without a human clicking anything.
a rendered screen · layout, colour, affordance, copy
- cart_id
- string · required
- quantity
- integer · min 1
- substitution
- enum · 2 values
- on_error
- OFFER_INACTIVE …
a typed payload · schema, enum, error code, example
For thirty years the reader was a pair of eyes, so we built pixels. XEKTA is what a marketplace looks like when you build for the other reader instead, and refuse to build for both.
About this many shopping queries a day, ChatGPT alone
Agents field roughly fifty million shopping queries a day on ChatGPT alone, and reach a small share of the sellers behind them.
The storefronts an agent can already buy from are the ones that were already easy to buy from: a modern commerce platform standardised their catalogue and their checkout, and that was their last mile, not their first. A seller without one is not underserved — it is unreadable, and adding an API to a marketplace built for people does not change that. Closing that gap is what XEKTA is being built to do.
Seller's agent — theirs, or ours
- Schema validator
- Canonical registry + seller offers
- Search, ranking, visibility auction
- Escrow and shipment timeline
- Trust, quality and brand safety
Consumer's agent — any MCP host
Both sides speak the same protocol grammar and receive the same typed JSON. XEKTA owns the schema, the escrow and the trust layer, and owns no inventory, no couriers and no screen.
- Search
- Compare
- Cart
- Prepare
- Approve
- Order
- Track
Comparison is deliberately wide and checkout is deliberately narrow: one seller per order keeps escrow, fulfilment and disputes unambiguous. Post-purchase is part of the same protocol, which is what lets an agent close its own loop.
It means no XEKTA-managed screen. The user picks how much authority to delegate, their host enforces it, and the protocol refuses to move money without proof that it happened.
Every spend operation requires a spend token issued by the host under the user's policy.
An eight hour acceptance window.
Counting down · the seller has not accepted yet- Buyer's money is authorised
- Held in escrow, seller unpaid
- Seller accepts, or it is voided
- Shipped, tracking on the record
- Delivered — seller is paid
No acknowledgement in eight hours and the authorisation is voided, the user is notified, and the agent re-routes elsewhere.
- error
- SCHEMA_VIOLATION
- field
- attributes.net_weight_g
- rule
- required for category:specialty_food
- received
- null
- fix
- send an integer in grams, 1–50000
- example
- { "net_weight_g": 340 }
- docs
- /catalog/specialty-food#weight
- Agent builds a call
- Validator rejects, before business logic
- Structured error returns field · rule · fix
- Agent rewrites and retries
Every code ships with the corrective action and a corrected call, so the agent has everything it needs to succeed on the retry. Support cost per transaction trends toward zero because the correction never leaves the machine.
- A consumer app or web storefrontno UI
- A seller dashboardno UI
- Couriers, drivers, fleet, warehousingseller's 3PL
- Our own bankingStripe Connect
- Pre-funded seller walletsintegrators
- Platform-authored substitutionuser policy
- Unbounded autonomous spendhost enforced
Not to operations, storefronts or a design organisation. The positioning is enforced by product reality: no retail UI, ever, and nothing to walk back later.
The headless marketplace agents transact through.