The framework for agent commerce readiness.
ZenBid lets agents discover what a business sells, read a public manifest from the existing website, and start authenticated offer or order workflows through ZenBid.
Existing website page
Manifest URL
/api/v1/agent/manifest/{token}
Agent actions
API rails
The problem
Agents can find a business page, but commerce breaks at the handoff.
Existing websites are built for humans. They rarely tell agents what is for sale, which actions are allowed, or how to complete a bid or order through authenticated rails.
Human website
Agent handoff gaps
No reliable manifest
Agents guess from page text, markup, and stale snippets.
No trusted action path
Offers and orders fall back to forms, emails, or scraped flows.
No transaction record
Payment status, webhooks, identity, and audit trails fragment.
What is ZenBid
An agent layer on top of your digital presence.
Existing business website
ZenBid readiness layer
Manifest
/api/v1/agent/manifest/{token}
Agent commerce rails
Readiness flow
- 1Install
- 2Publish
- 3Expose
- 4Route
- 5Audit
Agent builder flow
From page discovery to trusted action.
Treat the existing website as the discovery surface and ZenBid as the transaction surface. Agents can read public listing context, then switch to authenticated rails when a buyer wants to bid or buy.
Read MCP guideRead a public ZenBid manifest from an installed business page.
Manifest docsChoose a supported action for the listing: view, offer, or order.
Offers APIUse ZenBid auth, API, or MCP routes to create offers and orders.
Orders APIWhat ZenBid is not
Agent access without unsafe shortcuts.
No scraping required
Agents read declared listing and action metadata instead of guessing from page content.
Not another chatbot
ZenBid provides commerce routes for agents, not a conversational widget sellers have to staff.
No exposed API keys
Public pages can publish manifests while authenticated actions stay behind ZenBid rails.
Identity still matters
Business verification, buyer identity, payment state, and audit history remain part of the workflow.