APIs and artifacts for agent-native commerce.
Nexez publishes machine-readable artifacts for discovery, search, verification, and action. Developers can inspect public listings, call APIs, and build agents that understand real business offers.
REST
Public APIs
MCP
Per-listing manifests
JSON
Agent-readable offers
{
"business": "Nexez Agency",
"offers": [
{ "name": "Strategy Session",
"price": 450,
"action": "checkout" }
],
"readiness": 92
}Discovery
Find listings and offers by intent.
Agents and tools can search the public runtime for structured offers instead of scraping arbitrary websites. The response is designed for ranking, comparison, and handoff.
Agent search
Query by buyer intent, service type, product phrase, or category.
Directory API
Pull public listings with filters such as category and readiness threshold.
Global index
Use the public index for broad crawling and periodic sync.
Listing artifacts
Every listing exposes structured context.
A public page is only one representation. Nexez publishes multiple machine-readable formats so different agents can choose the surface they understand best.
agent.json
Canonical business, offer, action, trust, and readiness data for a listing.
llms.txt
Plain-language context optimized for LLM ingestion and retrieval.
MCP manifest
Optional per-listing manifest for tools and resources where enabled.
Action
Move from recommendation to handoff.
Developers can validate checkout handoffs, link users to specific offers, or route high-value requests into negotiation and review flows.
Checkout links
Offer-specific checkout paths make the selected action explicit.
Dry-run validation
Agents can verify a checkout path before starting a real purchase flow.
Buyer approval UX
Render clear consent before checkout, booking, contact sharing, or negotiation submission.
Questions
FAQ
Are public APIs authenticated?
Public discovery APIs are open by design. Account and management APIs require authentication.
Can I build an agent on top of Nexez?
Yes. Nexez is designed to be a clean offer source for agents, search tools, and buying assistants.
How should agents ask for approval?
Use the buyer approval pattern to show seller, offer, price, terms, risk notes, and the exact next action before side effects.
Where should crawlers start?
Start with https://nexez.app/llms.txt, /agent-pages.json, and /openapi.json.
Stop scraping. Start with structured intent.
Build against listings that were designed to be read by agents from day one.