> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/merge-workforce/logs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Logs

> Build once. Connect to every API, tool, and LLM. Ship products and agents to production without owning the integration stack.

## Docs

- [Tool calls](https://docs.merge.dev/merge-workforce/logs/tool-calls.md): What is captured in the Workforce tool call logs, how to filter them, and how to debug a failed tool call end to end from the dashboard.
- [API requests](https://docs.merge.dev/merge-workforce/logs/api-requests.md): What is captured in the Workforce API request logs, when they are the right place to look, and how they relate to the tool call logs.
- [LLM calls](https://docs.merge.dev/merge-workforce/logs/gateway.md): What the LLM calls tab shows for each model request that ran through Gateway, how to filter it, and how payload logging changes what you can read.
- [Audit trail](https://docs.merge.dev/merge-workforce/logs/audit-trail.md): What the Workforce audit trail records: the event catalog across tool access, models, and security, the fields on each entry, how updates render a diff, CSV export, and retention.
- [Stream logs to a SIEM](https://docs.merge.dev/merge-workforce/logs/siem.md): Pull tool call and API request logs from the log endpoints, and push LLM call logs from AI Gateway over OTLP, into your SIEM or observability platform.