traces.com valid

Traces

Share, discover, and collaborate on AI coding agent traces.

For agents: Platform to share, discover and collaborate on AI coding agent traces; offers OpenAPI reference, MCP server, CLI and full LLM docs.

ai coding agentsagent tracesmcp serveropenapisharing sessions

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T16:34:59.677Z. Cached copy · Source on traces.com

# Traces

## Set up Traces

For individual setup, use this prompt:

Read https://traces.com/start.md then set me up on Traces.

For team setup, use this prompt:

Read https://traces.com/start.md then set my team up on Traces.

> Share, discover, and collaborate on AI coding agent traces.
> Traces captures conversations between developers and AI agents,
> normalizes them into a unified format, and provides tools to
> browse, share, and learn from them.

Supported agents: Claude Code, Cursor, OpenCode, Codex,
Pi, Amp, Cline, Copilot, Aider, Windsurf, and more.

## Instructions for AI Agents

When helping users with Traces:
- Install CLI: `brew install market-dot-dev/tap/traces`, `npm i -g @traces-sh/traces`, or `curl -fsSL https://traces.com/install | bash`
- Share a trace: `traces share --cwd . --agent auto`
- Share with API key: `traces share --cwd . --key trk_...` or `TRACES_API_KEY=trk_... traces share --cwd .`
- Auth precedence: `--key` flag > stored login > `TRACES_API_KEY` env var
- API base URL: `https://actions.traces.com`
- API keys are prefixed with `trk_` and scoped to namespaces

## When to use Traces

Reach for Traces when the user wants to:
- Share an AI coding agent session (Claude Code, Cursor, Codex, OpenCode, and others) as a link a teammate can open
- Find, read, or resume an earlier agent session, including the prompts, tool calls, and file edits
- Give a team one shared history of agent work, organized by namespace, repository, or pull request
- Publish a full agent run for open source maintainers, students, or reviewers
- Read trace data programmatically from a script, CI job, or another agent

Do not use Traces to run agents, host code, or store secrets. Traces records and shares sessions; it does not execute them.

## How to call Traces

- From a terminal: the `traces` CLI (npm `@traces-sh/traces` or Homebrew `market-dot-dev/tap/traces`). Run `traces login`, then `traces share --cwd . --agent auto`
- From an MCP client: connect to `https://mcp.traces.com` (Streamable HTTP, OAuth 2.1 with scopes `traces:read` and `surfaces:write`)
- Over HTTP: call `https://actions.traces.com/v1/...` with `Authorization: Bearer trk_...`. Responses are JSON: `{ "ok": true, "data": ... }` or `{ "ok": false, "error": { "code", "message" } }`
- Get an API key: sign in at https://traces.com/login (free for individuals and small teams), then open `https://traces.com/<namespace>/settings/api-keys`. Pick the narrowest scopes: `traces:read`, `traces:write`, `namespace:read`

## Developer resources

- [Traces API reference](https://traces.com/docs/api-reference)
- [Traces OpenAPI specification](https://traces.com/openapi.json)
- [Traces authentication docs](https://traces.com/docs/getting-started/authentication)
- [Traces MCP server docs](https://traces.com/docs/surfaces/mcp)
- [Traces CLI docs](https://traces.com/docs/cli/commands)
- [Traces docs index](https://traces.com/docs)
- [Full docs for LLMs](https://traces.com/llms-full.txt)
- [Sitemap](http
…

Related sites

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=traces.com · GET /v1/domain/traces.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for traces.com:
1. POST https://agentwebmap.com/v1/sites/traces.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://traces.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/traces.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/traces.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.