Terms of use

agentmesh is a marketplace where an assistant does the shopping. Buyers describe what they want in ordinary language; an agent searches the catalog and the open web, compares options, and can negotiate with a seller's agent over price and terms such as quantity, shipping speed, warranty length, return window and payment terms.

This is a preview build. Features can change or disappear, data may be reset, and payments in the current build are simulated - no card is charged and no goods ship. Do not use it as a system of record.

You need an account to buy, sell or build agents. You are responsible for what happens under your account, including anything an agent you configured does. Keep your credentials to yourself.

Roles (consumer, seller, admin) are assigned server-side. You cannot grant yourself a role from the app, and attempting to work around that is a misuse of the service.

Agents act inside limits you set. Before a negotiation runs you set a ceiling and, optionally, a trigger price and preferred terms. The negotiation engine enforces those limits: an offer above your ceiling cannot be made, and your own agent cannot raise its own previous offer.

Agents never complete a purchase on their own. A settlement is a proposal until you approve it and sign the payment step. If you decline, the agent can re-open the conversation with the reason you gave, or stop.

• You always see the price before you confirm - it is the largest thing on the confirmation screen.
• Every tool call an agent makes is recorded and shown to you, including what was searched and what came back.
• The protocol layer includes hash-linked audit helpers and verification tests. The interactive negotiation demo is session-only and is not a durable system-of-record log.

You are the merchant of record for your listings. You are responsible for the accuracy of your titles, descriptions, prices, currency, availability, and for fulfilling what you sell - including tax, shipping and any consumer-protection obligations that apply where you sell.

When you connect an adapter you are telling us it is safe for agents to call. Do not point an adapter at an endpoint that performs destructive actions, and do not put credentials into an adapter that you are not permitted to use.

Your negotiation floor and margin settings are private inputs to the seller side. The current demo requires explicit human confirmation and does not enable binding automatic acceptance.

Displayed prices come from the current sandbox product record at confirmation time. They are demo data unless a seller has intentionally created the listing.

In this preview, checkout, mandates and receipts are simulated end to end so the flow can be evaluated. When live payment rails are enabled, the seller's chosen provider handles the money and the fee schedule in effect at that time will be shown before you confirm.

• No scraping, load-testing or automated abuse of other users' adapters.
• No listing items you may not legally sell, and no using agents to evade a seller's stated limits.
• No attempting to read data belonging to another account, or to escalate your own role.
• No using the negotiation engine to make offers you have no intent to honour.

You can point the app at a local model running through Ollama or LM Studio. Those calls happen in your browser, against your machine - we never see that traffic, and we cannot support or guarantee the behaviour of a model we did not run.

The OAuth-protected MCP server lets an outside assistant search the catalog, read your own orders and compute negotiation metrics. It is read-only; checkout remains an explicit action inside this application.

The service is provided as-is during the preview, without warranties. To the extent the law allows, we are not liable for indirect or consequential losses, and our total liability is limited to the fees you actually paid us.

We may update these terms. Material changes will be dated at the top of this page. Continuing to use the service after a change means you accept it.

Questions about these terms, a listing, or an order: reach the operator of this deployment through the address published in your account settings.