Retrace bronze
dash.retraceai.tech
“Execution replay engine for AI agents. Records every model call, tool invocation, retrieval, and error as a trace; replays it step by step; forks from any span with a modified input and cascade-replays the downstream execution; and proves whether a change improved, regressed, or did nothing.
a2a https://api.retraceai.tech/mcp talk to it https://dash.retraceai.tech/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 20 Nov 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 30 Aug 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 12d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of dash.retraceai.tech controls every word below.
record-agent-run
Record an AI agent execution as a trace: every model call, tool call, retrieval, and error is captured as a span with its input, output, cost, and timing.
- record this agent execution so I can replay it later
- instrument my Python agent so every model call is captured
inspect-trace
Read a recorded agent execution and walk its span tree to find the first step that failed, drifted, or produced an ungrounded answer.
- show me the span where this agent run failed
- walk the execution tree for trace 6f2c… and find the first error
search-spans
Semantic search across recorded spans and agent memories to find prior occurrences of a behavior, prompt, or failure by meaning rather than exact text.
- have I seen this hallucination before in any recorded run
- find previous runs where the agent looped on the same tool
fork-and-replay
Branch a recorded execution at one span with a modified input, then cascade-replay every downstream step so the whole agent re-executes along the new path. Side-effecting: requires explicit user approval before invocation.
- fork this run at step 3 with a shorter prompt and re-execute the rest
- re-run the agent from the retrieval step using a different model
prove-the-fix
Re-run a failed execution after a change and return a verdict — improved, regressed, or unchanged — with the first divergent span. Side-effecting: requires explicit user approval before invocation.
- did my prompt change actually fix this failure
- re-run the failed trace and tell me if it improved or regressed
evaluate-and-gate
Score recorded executions against behavioral criteria and return a pass/fail gate decision for a CI/CD pipeline.
- score these runs against my criteria and fail the build if they regress
- run the CI evaluation gate for this deployment
enforce-budget
Ask before the next model or tool call whether it is allowed: returns allow, block, or hold based on cost budgets, loop detection, and latency ceilings.
- is this next tool call within the cost budget
- should the agent be allowed to make this call
agent-memory
Store and semantically recall persistent facts, preferences, corrections, and patterns extracted from prior agent runs.
- remember that this customer prefers metric units
- what have I learned about this project from earlier runs
publish-tape
Publish a recorded execution as an interactive, shareable public URL so a human can replay it in a browser. Side-effecting: requires explicit user approval before invocation.
- publish this run as a shareable link for my teammate
- make an interactive replay of this execution public
read-retrace-docs
Search and read the Retrace documentation, SDK guides, CLI reference, and OpenAPI specification over MCP, without credentials.
- how do I enable cascade fork replay
- what are the Retrace rate limits
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Retrace — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- RetraceApiKey RetraceBearer
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://dash.retraceai.tech/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.