APIs and artifacts for agent-native commerce.
Build with documented APIs for discovery, approval, checkout, negotiation, and account management. SDKs, examples, and agent distribution tools are ready to use.
REST
Public APIs
MCP
Per-listing manifests
SDK
TypeScript and Python
{
"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.
Contracts and distribution
Use the contract your runtime understands.
Choose the interface your product supports. Nexez keeps the same listing, approval, and commerce rules across its APIs, SDKs, files, and MCP tools.
SDKs and examples
Published TypeScript and Python packages mirror safe search, validation, approval, and negotiation patterns.
Native agent access
An OpenClaw plugin and discovery skill provide installable tool and context paths.
MCP and ARD
Global and per-listing resources are discoverable through catalogs and well-known manifests.
Action
Move from recommendation to handoff.
Developers can dry-run eligible actions, present the exact destination and terms, require buyer approval, then create checkout or negotiation state with a durable status path.
Agentic commerce
Checkout APIs include native Nexez, ACP, and UCP session contracts.
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.
Do you support Agentic Resource Discovery?
Yes. The public ARD catalog lists Nexez search and MCP endpoints so compatible registries can index them.
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.