Marketplace

Trust is the product on a platform you do not stock yourself. An assistant that answers listing questions, order queries and payout tickets touches records that belong to strangers. This starter keeps that assistant inside a narrow lane. Screening, masking, three flat refusals and a scored answer are the whole of it.

A marketplace assistant serves two parties with opposing interests. A seller wants demand data. A buyer wants proof that a listing is real. Both talk to the same assistant, and neither should receive the records of the other. Teams reach for this starter when that boundary has to hold at platform volume.

The block list is the sharpest edge in this configuration. Three phrases stop a request before the model runs: a private key, a bulk customer export and a gift card pin. The first two match a scraping attempt, where a participant asks the assistant to hand over a list of counterparties. The third matches an effort to read stored value codes out of an order thread. A blocked request comes back as a refusal, with no partial answer.

Injection screening sits ahead of everything else, because listing text and chat messages are input that a stranger controls. A pasted instruction inside a product description gets inspected before the model reads it. Redaction then masks payment and card token strings between eight and sixty four characters. The mask keeps the conversation usable while the raw token stays out of the model call.

Generated replies pass a quality gate before delivery. The gate requires at least 120 characters and two sentences. The combined score must reach 0.78, and accuracy alone must reach 0.80, with both metrics weighted evenly against relevance at 0.78. A reply that misses any floor is blocked, so a participant sees nothing rather than a thin answer. Keyword safety screening uses the built-in term list only, since no custom terms are configured.

Roles are the gap to close yourself. One policy applies to every caller, and the starter does not separate a buyer from a seller. Add that split in your own identity layer before you route sensitive queries. Audit marking flags each evaluated request and blocks nothing, and retention stays a separate choice. Payout, dispute and fraud logic belong to your platform. Choose the E-commerce starter when a single merchant catalog is the whole sales context.