Nexbid Commerce Agent
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://api.nexbid.dev/v1/a2a
· transport JSONRPC
Product Discovery product-discovery
Find products matching user intent, context, and budget constraints
Category Browsing category-browse
Browse available product categories by geography
Product Detail product-detail
Get comprehensive product information including price, availability, and purchase link
Purchase purchase
Create a purchase intent for a product and return a Task. The task tracks progress via tasks/get; the purchase completes only after the human buyer authorizes it out-of-band through a magic link — that authorization step is not part of the A2A protocol.
2026-10-30 from https://nexbid.dev/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.