Who is acting?
A technical identifier does not always explain who operates the agent or what its purpose is.
Verify the context before exposing a sensitive action.How we evaluate contextAn AI agent is an assistant that searches, compares, or buys by following a person's instructions. You decide what it may do in your store, when it needs approval, and what is recorded if a question arises.
Before you see what is ready · During you apply your rules · After you consult the available evidence.
checkoutScope: Trusteed does not process payments, is not merchant of record and does not replace your own records or legal obligations. See full limits
An agent can be authenticated and still act against your commercial interests. Control evaluates the actions it covers and can allow them, ask for review or block them, depending on the surface and the state of the pilot. Where issuance exists, Evidence keeps a signed record of the context and of the decision available at that moment.
A technical identifier does not always explain who operates the agent or what its purpose is.
Verify the context before exposing a sensitive action.How we evaluate contextA request that is valid on its own can lock inventory, drain promotions or split orders.
Apply limits, risk and human review.How we apply limits and human reviewPrice, stock, seller or terms may no longer match what was approved.
Revalidate authoritative state where the capability is operational.See revalidation in the flowA dispute requires joining intent, decision, order, delivery and return.
Keep verifiable records and detect evidence gaps.See the sample TrustReceiptFirst you see what is ready. Then you apply your rules while the assistant acts. And, when the capability is available, you can consult a record of what happened.
A reproducible diagnosis of what you already have: which control and evidence signals exist today, and what is missing to open the channel.
Verify who is acting, apply your economic limits, ask for human confirmation when it matters and block what you do not accept.
When the pilot scope supports it, a signed TrustReceipt helps verify what was recorded and which evidence is still missing.
TrustReceipt keeps the available context of identity, consent, policies and operation. Its signature lets you check who issued the record and whether it changed afterwards; on its own it does not prove that the underlying fact happened.
It is not a complete lifecycle chain nor a universal legal guarantee. Evidentiary weight depends on the jurisdiction, the process and the concrete evidence available.
tr_01JY7E4M8X...A92FIndividual signed record, issued in production. That every checkout generates one, or any volume, cannot be claimed: the last known receipt is from 2026-08-13 and the last 24h are zero. The lifecycle graph remains planned.
Score for merchant: agenticmcpstore
The public v4.1 surface already takes part in ranking and eligibility. It is not a customer review, and it is not a score for Trusteed: it is this merchant's.
confidence: cold_startThe number is computed by v4.1. The per-component breakdown and the methodology document are still v2.0, which is why they do not explain the figure on their own.
How the Trust Score is measured ↗Change the scenario. The result explains which rule was applied and what has to happen next.
{ "tool": "complete_checkout", "amount": 6400, "agent_status": "verified"}The operation may continue. The user confirms before checkout.
No. Trusteed is designed as a layer on top of existing systems.
Yes. Identity answers who is requesting the action; on its own it does not explain whether the sequence is economically abusive.
No. The current corpus contains individual receipts. The causal lifecycle graph is still behind flags that are off: it is not available today.
No. It strengthens traceability and evidence readiness. Evidentiary weight depends on the case, the recipient, the process and the jurisdiction.
Control and Evidence are offered through guided pilots. Assurance helps evaluate the starting point.
Intelligent Discovery
Natural-language search over this site, served by NLWeb.
Not available today: the route and search pipeline are deployed, but the embedding step is failing upstream. Try it and you'll see the real error.
MCP endpoint
POST https://trusteed.xyz/{slug}/mcpJSON-RPC 2.0 — replace {"{slug}"} with any merchant slug (e.g. demo-store)
Available tools