saascode
ecommerce, retail & dtc·run 177 · Jun 2026

SelfVend

A hosted agent-access gateway for small merchants that publishes bounded read capabilities and governs identity, delegation, payment, approval and write execution separately.

Genesis score6.74/10
Make SelfVend real.0/500
500 more votes and SelfVend is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

A store operator may want software agents to discover products, availability or policies and later request actions such as cart creation or order placement. Publishing an endpoint is easy compared with deciding which agent represents whom, what it may see, what payment covers and who authorizes a consequential write. SelfVend packages that governance boundary.

The source confirms a live vertical product with public discovery, self-registration and read-versus-write tiers, plus several developer payment primitives. The remaining non-developer productization gap is plausible but thin. A one-day install, universal discovery or default paid write cannot be promised from the supplied evidence.

Agent observation, software identity, verified principal, delegation, scope, price quote, payment authorization, merchant policy, human or principal approval, destination instruction, provider acknowledgment, order readback, settlement and fulfillment remain separate. Payment never grants authority by itself.

Who pays — and why

A small ecommerce operator or platform implementer that wants agent-readable public data and tightly governed transactional actions without building the entire access layer.

What it unlocks
A public capability manifest that exposes only merchant-approved read semantics and current limits
A registration and delegation flow binding software identity to a verified principal, purpose and expiring scope
A transactional ledger separating quote, payment, approval, instruction, destination readback, settlement and fulfillment
How Genesis scored it
6.74across seven criteria
tension 7temporal 8blindspot 5buyer 8leverage 6convergence 5why-not 7
8
Temporal window

Several 2026 launches validate current agent-commerce infrastructure without a hard deadline.

8
Buyer persona

Small store operators and their implementers form a concrete segment, though platform and transaction scope need discovery.

5
Convergence

The source records two cross-reference mentions and no inbound connections.

Why it scored well

The input identifies a non-developer merchant buyer, confirms a working discovery and self-registration pattern and documents several active agent-payment primitives.

What's holding it back

The moat is intentionally thin, developer primitives can move up-market, store write semantics and fraud controls are complex, anonymous registration is insufficient authority and managed onboarding may prevent a one-day self-serve install.

Signals detected4 sources crossed
SignalSupplied proof-of-pattern review

SignalSupplied payment-infrastructure review

SignalSupplied productization search

SignalSupplied evidence boundary

Direction briefselfvend.md
selfvend.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.