Real
Model Context Protocol: the scenario calls really do go out against the public endpoint.
In production.Live demo · no sign-up
Try how the rule engine behaves without writing a line of integration.
The demo store's public endpoint answers read tools with no authentication. Run a full scenario step by step, or configure an agent profile and watch which merchant rules fire before the transaction reaches checkout.
live Public endpoint:
POST api.trusteed.xyz/demo-store/mcpCall search_products, get_merchant_profile or create_cart directly. Read tools need no key; checkout tools use a temporary sandbox key the page requests for you. Every step shows the JSON-RPC you would send and the response exactly as it arrives.
Here you see what gets blocked and why. Switch any of the thirty rules on or off, move the agent's signals and check the verdict against the specific rule behind it. It is the same family of rules you would apply to your store.
Two minutes: run “Rule engine block” to see an operation stopped before the charge, and “High-value order” to see when the system requires human confirmation. The rest of the page is the technical detail behind those two decisions.
Guided scenarios
A full flow, step by step, against the real endpoint.
Every step runs a demo-store tool and shows the unedited response. Checkout tools need a temporary sandbox key first; the page requests it on its own.
Scenariosreal
Search and buyJSON-RPC 2.0
search_productsSearch for sneakersget_product_detailsProduct detailscreate_cartAdd to cartsandbox keyget_shipping_ratesFetch shipping ratessandbox keypreview_checkoutPreview the ordersandbox keycomplete_checkoutComplete the purchasesandbox key
Run the scenario to see the endpoint's response.
Agent Rules
Configure the agent. Switch rules on. See who gets through.
Thirty of the engine's forty-six rules, grouped by category and evaluated against the profile you define. The verdict arrives with the rule behind it and its threshold, not with an opaque number.
Agent signalsSIMULATED PROFILE
IDENTITY
HISTORY
CART AND CHECKOUT
SHIPPING AND PRODUCT
Merchant rules30 / 30 active
Transaction and policyORDER CONTEXT
Source protocol
VerdictSIMULATED IN YOUR BROWSER
Configure the agent profile and press Evaluate rules.
This simulator measures the agent. The Trust Score measures the merchant. They are two sides of the same decision: the merchant reads the agent's signals to decide whether to accept the operation, and the agent reads the merchant's to decide where to buy.
See how the Trust Score is measuredWhat this demo is not
No payment is real.
The demo store is a public MCP server with a fictional catalogue. Protocols run in sandbox or test mode: no charges are processed and no funds move. Read tools accept twenty requests per minute per IP, and sandbox keys expire after twenty-four hours. If the endpoint does not answer from this browser, the page says so and shows the equivalent curl: the call works the same from your agent or your terminal.
Simulation
The rule simulator runs in your browser. The real engine runs on the server and its endpoint is not public.
It shows the mechanism, not any store's configuration.Sandbox
No payment protocol moves funds here. The scenario's checkout ends in a test session.
No charges.Next step
Connect your real store
The pattern you just ran is the one applied to your catalogue, your policies and your checkout. Rule configuration is scoped to one operation and one metric.