Retrace bronze
docs.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://docs.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 8 Jan 2027 as of our check on 12 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
docs.retraceai.tech. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
-
Well-known document
This host also publishes an ARD catalog (
/.well-known/ai-catalog.json) declaring 5 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified. - AI use policy
-
What this site's
robots.txtsays about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents. - AI-facing documents
-
Publishes
/llms.txt— “Retrace” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 15 Oct 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
- 1d 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 docs.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
agenttru.st compared this card's skill list with every other listing's: 2 other listings declare an identical one, ignoring case, spacing and each card's own hostname. See all 3. That says the cards' text is the same, not who runs them.
What kind of listing
- docs. hostname: Its hostname begins docs.
Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.
What its catalog declares
From the ARD catalog this host publishes at
/.well-known/ai-catalog.json. The operator controls every entry; agenttru.st
verified that the catalog exists and parses, and nothing about what the entries say.
Retrace MCP Server
Product MCP server for recorded AI agent executions: list and read traces, semantic span search, agent memory, fork replay, evaluation updates, and tape publishing.
https://api.retraceai.tech/mcp/server-cardRetrace Docs MCP Server
Documentation MCP server: search and read Retrace docs, SDK guides, CLI reference, and the OpenAPI specification. Read-only, no credentials required.
https://retraceai.tech/.well-known/mcp/docs-server-card.jsonRetrace Agent Card (A2A)
Agent-to-Agent card describing Retrace's skills for recording, replaying, forking, and evaluating AI agent executions.
https://retraceai.tech/.well-known/agent-card.jsonRetrace REST API (OpenAPI 3.1)
OpenAPI 3.1 description of the Retrace REST API: trace ingestion, semantic search, fork replay, batch operations, evaluation gates, runtime enforcement, and OTLP ingestion.
https://retraceai.tech/openapi.jsonRetrace Agent Skills
Index of Retrace agent skills, each with a name, description, and entry point.
https://retraceai.tech/.well-known/agent-skills/index.jsonTechnical 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://docs.retraceai.tech/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.