Canonical integration knowledge for Talaria. Humans read this on www.newtalaria.com/docs. Coding agents read the same pages via MCP docs_list, docs_search, and docs_get.
For agents
Start here: Add Talaria with an agent.
Then:
- Detect the stack from the local repo (
pubspec.yaml, package.json, composer.json).
docs_search with an sdk filter (for example flutter) and query install or init.
docs_get the stack hub and configuration page.
- Wire DSN + API key (
tal_live_… keys are public client ingest credentials — env / dart-define are fine). The key decides the environment. setup_project returns a development key. Do not pass environment in SDK init. Send release as <ref>@<shortsha> (for example main@a8f31c2). See Releases. Server SDKs fill that from CI when TALARIA_RELEASE is unset.
- Tell the human which Project settings to enable (or use MCP
get_project / update_project_settings when authorized).
- Verify with
search_events / search_errors and environment: development. get_project_stats countsByEnvironment is analytics volume and stays 0 when analytics is off.
Browse
Learn guides and product narrative stay on the marketing site (/learn, /product). This repo is install and how-to only.