Nexez Agentic Commerce

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Find Nexez sellers, inspect offers, and validate checkout or negotiation before buyer approval.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Nexez Agentic Commerce": {
      "url": "https://nexez.app/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• nexez_search read-only

  Find services or products for a specific buyer request. Returns JSON text with ranked results, structured offers, listing slugs, agent.json URLs, and applied filters. Use nexez_directory for broad browsing, then nexez_get_page to inspect an exact offer before a dry run.

  Parameters:

  • q (required) — string — What the buyer is looking for
  • lat — number — Optional latitude context metadata. Does not filter or rerank results; use location for geographic filtering.
  • lng — number — Optional longitude context metadata. Does not filter or rerank results; use location for geographic filtering.
  • limit — number — Maximum results; defaults to 10 and is rounded down and clamped to 1-50.
  • category — string — Marketplace category; omit or use all to include both professional and consumer listings.
  • industry — string — Case-insensitive substring filter on the published industry, for example plumbing.
  • location — string — Optional city/region filter
  • verified — boolean — Filter by seller verification signal: true requires a signal, false requires its absence; omit to include both.
  • min_trust — integer — Minimum marketplace trust score (0-100); omit for no trust threshold. Not a guarantee of seller performance.
  • price_band — string — Filter by the listing marketplace price band. Inspect the exact offer for its price and currency; this is not a checkout quote.
  • min_readiness — integer — Minimum listing readiness score (0-100); omit for no readiness threshold.
  • supports_checkout — boolean — Deprecated compatibility filter: any actionable offer or provider handoff
  • nexez_checkout_ready — boolean — Owner payout state confirms Nexez-settled checkout readiness
  • supports_negotiation — boolean — Filter by negotiation availability: true for eligible listings, false for non-negotiable listings; omit to include both.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• nexez_directory read-only

  Browse published Nexez listings without requiring a buyer query. All filters are optional. Returns directory JSON text with listing summaries and readiness information. Use nexez_search when you need ranked matches for a specific buyer request.

  Parameters:

  • q — string — Optional case-insensitive text filter across listing name, description, audience, and location.
  • category — string — Marketplace category; defaults to all.
  • location — string — Optional city or region filter matched against published location and service-area information.
  • min_readiness — number — Minimum listing readiness score, normally 0-100; defaults to 0 (no threshold).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• nexez_get_page read-only

  Fetch one listing's structured agent manifest as JSON text, including seller profile, offers, configuration requirements, and published actions. Use a slug returned by search or directory; inspect exact offer identifiers and requirements before validation.

  Parameters:

  • slug (required) — string — Exact published listing slug returned by nexez_search or nexez_directory, not a full URL.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• nexez_validate_checkout read-only

  Dry-run checkout for an exact published offer. Returns validation JSON text with offer readiness or errors and missing requirements. Inspect the offer with nexez_get_page first. Never charges or creates an order; a successful check is not a completed purchase.

  Parameters:

  • slug (required) — string — Exact published listing slug returned by discovery, not a full URL.
  • offer (required) — string — Exact offer key from the listing manifest, for example services-0 or products-1. Do not invent an index.
  • query — string — Optional buyer context
  • buyerEmail — string — Optional buyer-provided email for checkout context. Omit when unnecessary; never invent personal details.
  • buyerReference — string — Optional buyer-provided reference for checkout context; omit if none was supplied.
  • offerConfiguration — object — Buyer-selected configuration values keyed exactly as defined by the target offer configuration schema from nexez_get_page. Supply required fields for that offer; do not invent values or use a generic schema.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• nexez_validate_negotiation read-only

  Evaluate proposed terms against an exact offer and the seller's published rules in a forced dry run. Returns rules-evaluation JSON text or validation errors. Inspect the offer first and supply its required terms. Never submits a proposal, contacts a seller, or writes a negotiation.

  Parameters:

  • slug (required) — string — Exact published listing slug returned by discovery, not a full URL.
  • offer (required) — string — Exact offer key from the listing manifest, for example services-0 or products-1.
  • query — string — Buyer request describing the desired work or product and relevant context.
  • budget — string — Buyer-proposed budget or range as text, using the offer currency, for example USD 500. Do not invent a budget.
  • contact — string — Optional buyer contact route.
  • timeline — string — Buyer-proposed delivery timing as text, for example within 4 weeks. Use requestedTerms.projectWeeks for a numeric duration rule.
  • requestedTerms — object — Structured buyer proposal. Published seller rules may require scope (text or list of deliverables), revisionCount (whole number 0-1000), and projectWeeks (whole number 1-1000). Example: {"scope":"Logo and brand guide","revisionCount":2,"projectWeeks":4}. Inspect the offer rules; omit unknown terms rather than inventing them.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.