--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/librechat-vs-t3-chat/" data_url: "https://onaihq.com/compare/agents/librechat-vs-t3-chat/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # LibreChat vs T3 Chat > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 26 criteria with sourced findings for both products, including 26 that a second agent cross-checked for both. 48 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - LibreChat source checks: 2026-10-21 to 2026-10-26. - T3 Chat source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/librechat-vs-t3-chat/ - Machine-readable JSON: https://onaihq.com/compare/agents/librechat-vs-t3-chat/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The model catalog is configured by the customer across first-party provider integrations and custom endpoints. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - providers: Documented routes include OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock and custom compatible services; selection requires enabled credentials and model access. - current_models: v0.8.8 release notes mention GPT-6/GPT-6.1 Sol, Claude Opus/Sonnet 5.5 and Gemini 3.8 Flash support. Actual selectable IDs still depend on the installed configuration and provider account. - auto_routing: Does the product route between models automatically, and is the chosen model shown? No automatic routing policy showing a chosen model was established, and no configured endpoint was exercised. - multimodal_input: Provider-native files support images/PDFs and some providers accept additional Office/audio/video types. Exact acceptance depends on the selected model and transport; no matrix was tested. - providers — Which model providers are available? [partial]: Documented routes include OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock and custom compatible services; selection requires enabled credentials and model access. Sources: librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex. - current_models — Which current models are selectable on this plan? [partial]: v0.8.8 release notes mention GPT-6/GPT-6.1 Sol, Claude Opus/Sonnet 5.5 and Gemini 3.8 Flash support. Actual selectable IDs still depend on the installed configuration and provider account. Sources: librechat:librechat:releases. - user_choice — Can users pick the model per chat? [supported]: Users choose an endpoint/model unless admins enforce model specs or a fixed Agent. Sources: librechat:librechat:modelspec, librechat:librechat:agents. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: auto_routing: Does the product route between models automatically, and is the chosen model shown? No automatic routing policy showing a chosen model was established, and no configured endpoint was exercised. - multimodal_input — Which models accept images, audio or files? [partial]: Provider-native files support images/PDFs and some providers accept additional Office/audio/video types. Exact acceptance depends on the selected model and transport; no matrix was tested. Sources: librechat:librechat:ocr. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:releases, librechat:librechat:modelspec, librechat:librechat:agents, librechat:librechat:ocr #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid-account vendor replies establish manual model switching and provider routes, while the current plan-specific catalogue is unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 vendor-support context; no Free or Premier catalogue parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - providers — Which model providers are available? [partial]: Pro-context vendor replies discuss Gemini, Claude and GPT routes; the FAQ separately describes OpenAI/Anthropic/Google/OpenRouter data handling. Those policy/provider names are not a complete tier-entitlement or underlying-lab catalogue. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls. - current_models — Which current models are selectable on this plan? [unknown]: A complete current selectable-model list for Pro, Free or Premier is unverified. The FAQ claude-4.6-sonnet URL is an example, and undated support model names are not a current plan catalogue. - user_choice — Can users pick the model per chat? [partial]: In the USD8 context discussion the vendor recommends manually switching to Gemini Flash or summarizing into a new chat with another chosen model. This supports Pro model selection as described there, but not a current all-model, effort or Free/Premier entitlement matrix. Sources: t3-chat:t3-chat:r2-pro-context-byok. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? The public T3 FAQ, Terms, Privacy/Security policies, official feedback statuses and identifiable vendor replies did not establish this detail. No authenticated account, enterprise quote or bounded fixture was used. - multimodal_input — Which models accept images, audio or files? [unknown]: No current Pro model-by-model image/audio/file compatibility matrix was retrieved. The generic privacy upload categories do not establish a plan entitlement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok ### MOD-02: Model freshness Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated releases document model updates, but measured availability lags and retirement notice periods remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - release_lag_days: What was the lag for each of the last three major releases, per provider? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established. - deprecation_notice: How much notice is given before a model is removed? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established. - version_pinning: Admins can name explicit model IDs in endpoints/model specs; continuing remote availability remains under provider control. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: release_lag_days: What was the lag for each of the last three major releases, per provider? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established. - changelog — Is there a dated public model changelog? [supported]: Public releases and the LibreChat changelog date model updates; v0.8.8 was published 2026-10-01. Sources: librechat:librechat:releases. - deprecation_notice — How much notice is given before a model is removed? [unknown]: deprecation_notice: How much notice is given before a model is removed? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established. - version_pinning — Can an admin keep an older model version? [partial]: Admins can name explicit model IDs in endpoints/model specs; continuing remote availability remains under provider control. Sources: librechat:librechat:modelspec, librechat:librechat:custom. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:releases, librechat:librechat:modelspec, librechat:librechat:custom #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public feature-release information is described; plan-specific pinning and version guarantees remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Public T3 Chat release information; no verified Free/Pro/Premier picker/pinning entitlement; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved. - changelog — Is there a dated public model changelog? [partial]: A vendor reply says major-feature changelog lives in Discord and a website version is planned. No accessible dated model-by-model release ledger was retrieved. Sources: t3-chat:t3-chat:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved. - version_pinning — Can an admin keep an older model version? [unknown]: The vendor describes pinning and a Legacy designation in the general picker discussion, without a named individual tier. Plan-specific pinning, retained model versions and admin locks remain unverified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:changelog ### MOD-03: Bring-your-own keys and provider contracts Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer-held provider keys, customer Azure/AWS/Vertex configurations and custom endpoints are documented. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - byo_restrictions: File modalities, tools and other capabilities depend on provider/model support and optional services. A universal BYO feature-parity guarantee was not established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Provider keys can be operator-supplied or user_provided, with user key controls in Settings. Sources: librechat:librechat:firstchat, librechat:librechat:custom. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Customer Azure OpenAI deployments, AWS Bedrock region/credentials and Anthropic Vertex project/region routes are documented separately. Sources: librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Operators can configure a custom compatible API URL and model list. Sources: librechat:librechat:custom. - byo_pricing — Does BYO change the licence price? [supported]: MIT repository use has no per-seat licence fee; customers separately procure provider service usage. Sources: librechat:librechat:license, librechat:librechat:firstchat. - byo_restrictions — Which features stop working with BYO? [partial]: File modalities, tools and other capabilities depend on provider/model support and optional services. A universal BYO feature-parity guarantee was not established. Sources: librechat:librechat:ocr, librechat:librechat:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:firstchat, librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:license, librechat:librechat:ocr, librechat:librechat:code #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Vendor replies support a Pro own-OpenRouter-key route, without establishing universal provider/model coverage. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 with optional customer OpenRouter key; no Free BYOK entitlement asserted; add_ons=Customer-paid OpenRouter/provider usage; model routing and verification prerequisites apply; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - own_api_keys — Can the customer use its own provider API keys? [supported]: In the paid USD8 usage discussion, staff explicitly offers a customer OpenRouter key for direct request billing; the USD8 context discussion describes OpenRouter fallback. No all-provider/all-model BYOK entitlement follows. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unknown]: Can it use its own Azure OpenAI, Bedrock or Vertex deployment? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved. - byo_pricing — Does BYO change the licence price? [partial]: The paid subscription and direct-provider charges are separate in the vendor discussion. A discounted BYOK-only licence and exact customer provider rates are not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls. - byo_restrictions — Which features stop working with BYO? [unknown]: Current all-model BYOK compatibility is unknown: the OpenRouter-coverage request is marked Completed while the vendor says those model routes do not run through OpenRouter and rerouting requires future work. The old OpenAI GPT5 setup reply does not establish a complete current route matrix. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok ### MOD-04: Local and self-hosted models Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Local compatible inference and Ollama embeddings are documented; optional services must also be local for a fully private stack. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - feature_parity: Chat and retrieval can use local endpoints. Tool calling and vision depend on the model; external OCR/search/code services are separate. No complete offline fixture was run. - vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? A vendor-hosted EU/Swiss open-weight model service was not established for the MIT self-hosted project. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Custom endpoints can point at customer-hosted compatible model servers, including Ollama-compatible setups. Sources: librechat:librechat:custom. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [supported]: The RAG configuration documents Ollama embeddings and local Hugging Face through the appropriate full image. Sources: librechat:librechat:ragcfg. - feature_parity — Which features fail with self-hosted models? [partial]: Chat and retrieval can use local endpoints. Tool calling and vision depend on the model; external OCR/search/code services are separate. No complete offline fixture was run. Sources: librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:code. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unknown]: vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? A vendor-hosted EU/Swiss open-weight model service was not established for the MIT self-hosted project. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:custom, librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:code #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Model specs and scoped configuration can limit choices; optional user credit reservations provide a blocking mechanism. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - model_allowlist_by_group: Enforced model specs and role/group configuration overrides can restrict available endpoints/models. The separate management UI is preview; a two-group fixture was not run. - data_bound_models: Can admins restrict which models receive connector or knowledge content? A hard binding between each enterprise content source and a permitted model provider was not established in the Agent and access-control guides. - user_limits: Balance tracking, initial credits/refills and message moderation limits are operator-configurable, rather than a universal vendor allowance. - model_allowlist_by_group — Can admins limit models per group? [partial]: Enforced model specs and role/group configuration overrides can restrict available endpoints/models. The separate management UI is preview; a two-group fixture was not run. Sources: librechat:librechat:modelspec, librechat:librechat:admin, librechat:librechat:access. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: data_bound_models: Can admins restrict which models receive connector or knowledge content? A hard binding between each enterprise content source and a permitted model provider was not established in the Agent and access-control guides. - default_model — Can admins set the default model? [supported]: Model-spec presets can define default endpoint/model configurations. Sources: librechat:librechat:modelspec. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Balance tracking, initial credits/refills and message moderation limits are operator-configurable, rather than a universal vendor allowance. Sources: librechat:librechat:balance, librechat:librechat:mod. - limit_behaviour — What happens when a limit is reached? [supported]: Pinned checkBalance reserves credits and throws a TOKEN_BALANCE error when insufficient. This establishes a blocking code path, not an observed end-to-end quota test. Sources: librechat:librechat:balance-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:modelspec, librechat:librechat:admin, librechat:librechat:access, librechat:librechat:balance, librechat:librechat:mod, librechat:librechat:balance-pin #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individuals have cost-based refill limits; enterprise group governance is unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 cost-limit discussion and Premier account bucket reply; Free excluded from this mechanics finding; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - default_model — Can admins set the default model? [unknown]: Can admins set the default model? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Pro cost-limit replies and a Premier-specific vendor support reply tie paid usage to the FAQ Base/Overage mechanics: four-hour Base refill and monthly Overage refill. No fixed token/message allowance is published;20/200 example points are illustrative, not plan capacities. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets. - limit_behaviour — What happens when a limit is reached? [supported]: For these documented paid-account bucket routes, expected request cost is reserved then settled after completion; when both balances are exhausted the FAQ says to wait for refill. No Free-tier behaviour is inferred. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets, t3-chat:t3-chat:r2-paid-tier-controls. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets ## Company knowledge ### KNOW-01: Files in chat Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Files can be indexed, injected as extracted text or sent directly to compatible model providers. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=New spreadsheet finding at development source a378657583567310c841d652b0f6b00c83e2bd6b; earlier accepted facts retain their cited release pins; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - File counts, sizes and provider acceptance depend on deployment settings. - Spreadsheet parsing yields named sheets and CSV values; layout/formula fidelity and the shared fixture remain untested. - formats — Which formats are accepted? [supported]: Documents include PDF/text/Office formats through configured extraction; provider-native acceptance varies, including Bedrock Office formats and Google audio/video. Sources: librechat:librechat:ocr, librechat:librechat:filecfg. - limits — What size and count limits apply per file and chat? [partial]: File counts, sizes and MIME patterns are operator/endpoint settings; provider limits may be stricter. The shared fixture was not uploaded. Sources: librechat:librechat:filecfg, librechat:librechat:ocr. - ocr — Are scanned PDFs read? [supported]: Optional Mistral OCR, Azure/Vertex Mistral OCR and provider-native file processing are documented. Sources: librechat:librechat:ocr. - spreadsheets — Are Excel tables read with structure intact? [partial]: The inspected built-in XLSX/XLS/ODS parser emits each sheet name and CSV values. The current guide lists a 15 MB built-in parser limit. Workbook formatting, formula recalculation and shared-fixture accuracy were not established. Sources: librechat:librechat:r4-spreadsheet-parser, librechat:librechat:r4-text-current. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: RAG retrieves indexed chunks; Upload as Text and Agent File Context inject extracted full text, subject to context limits. Sources: librechat:librechat:rag, librechat:librechat:text, librechat:librechat:ocr. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: librechat:librechat:ocr, librechat:librechat:filecfg, librechat:librechat:rag, librechat:librechat:text, librechat:librechat:r4-spreadsheet-parser, librechat:librechat:r4-text-current #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Pro context limits and own-key fallback are documented; plan-specific upload formats/caps remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 context restrictions and optional BYOK fallback; exact upload entitlement by tier unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - formats — Which formats are accepted? [unknown]: The privacy policy mentions PDF/images/text and the request is Completed, but no current individual-tier format entitlement was verified. The earlier sentence attributing browser/file-specific PDF upload bugs to a vendor reply is withdrawn because no precise reply locator was reproduced. - limits — What size and count limits apply per file and chat? [partial]: Vendor replies distinguish context restrictions on USD8 Pro from higher-tier allowances and own-key fallback. They do not publish a complete current per-model file size/count or context-cap matrix; no32K or user-suggested MB cap is adopted. Sources: t3-chat:t3-chat:r2-pro-context-byok. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-pro-context-byok ### KNOW-02: Knowledge bases and shared collections Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents and personal Projects keep files across chats; shared Agent access is distinct from personal Project ownership. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - sharing_scope: Agents can share files/knowledge with permitted users/groups/roles; Projects themselves are personal and cannot be shared or transferred. - size_limits: What are the collection limits? No universal collection storage/size allowance was established; limits are deployment and file-configuration dependent. - persistent_collections — Can users keep document collections across chats? [supported]: Agent File Search/File Context and Project reference files persist for later chats. Sources: librechat:librechat:agents, librechat:librechat:projects. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [partial]: Agents can share files/knowledge with permitted users/groups/roles; Projects themselves are personal and cannot be shared or transferred. Sources: librechat:librechat:access, librechat:librechat:agents, librechat:librechat:projects. - size_limits — What are the collection limits? [unknown]: size_limits: What are the collection limits? No universal collection storage/size allowance was established; limits are deployment and file-configuration dependent. - assistant_binding — Can collections be bound to an assistant? [supported]: Agent File Search and File Context bind retrieved or extracted knowledge to an Agent. Sources: librechat:librechat:agents, librechat:librechat:ocr. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:projects, librechat:librechat:access, librechat:librechat:ocr #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-03: Enterprise connectors Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02). #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint and OneDrive have a documented delegated file picker. Other enterprise systems require separately verified tools or connectors. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - microsoft_365: SharePoint Online and OneDrive for Business can be browsed and attached through Entra token reuse/OBO, delegated AllSites.Read and Files.Read.All, and admin consent. Outlook/Teams source access was not established. - google_workspace: Which Google sources are connected? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - atlassian: Confluence and Jira? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - other_systems: Which other business systems? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - on_prem_sources: Custom local MCP stdio servers can reach systems available to the deployment, but a maintained file-share/database connector and its permissions were not verified. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online and OneDrive for Business can be browsed and attached through Entra token reuse/OBO, delegated AllSites.Read and Files.Read.All, and admin consent. Outlook/Teams source access was not established. Sources: librechat:librechat:sharepoint. - google_workspace — Which Google sources are connected? [unknown]: google_workspace: Which Google sources are connected? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - atlassian — Confluence and Jira? [unknown]: atlassian: Confluence and Jira? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - other_systems — Which other business systems? [unknown]: other_systems: Which other business systems? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Custom local MCP stdio servers can reach systems available to the deployment, but a maintained file-share/database connector and its permissions were not verified. Sources: librechat:librechat:mcpcfg. - connector_provider — Who builds and maintains each connector? [supported]: LibreChat documents the Microsoft picker. Other MCP tool integrations are separately configured and maintained by their respective server authors/operators. Sources: librechat:librechat:sharepoint, librechat:librechat:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:sharepoint, librechat:librechat:mcpcfg, librechat:librechat:mcp #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Product resource ACLs and delegated Microsoft file selection are documented. Continuing source permissions for copied content remain untested. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. - enforcement_point: LibreChat ACLs control Agent/file resources; Microsoft delegated OBO limits source downloads as the signed-in user. No query-time source ACL check for previously copied chunks was established. - revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. - admin_scope_controls: Operators can scope Agent/resource grants and its selected files. Site/folder/label exclusion across sources was not established. - sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. - source_permissions_respected — Are source permissions enforced per user? [unknown]: source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: LibreChat ACLs control Agent/file resources; Microsoft delegated OBO limits source downloads as the signed-in user. No query-time source ACL check for previously copied chunks was established. Sources: librechat:librechat:access, librechat:librechat:sharepoint. - revocation_delay — How quickly does a removed permission take effect? [unknown]: revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Operators can scope Agent/resource grants and its selected files. Site/folder/label exclusion across sources was not established. Sources: librechat:librechat:access, librechat:librechat:agents. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:sharepoint, librechat:librechat:agents #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-05: Freshness and sync model Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The RAG API copies uploaded content into PGVector; imported files do not by themselves establish live enterprise synchronization. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - sync_interval: How often does an index refresh? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides. - deletion_propagation: How quickly does a deleted document disappear? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides. - live_or_indexed — Is content searched live or copied into an index? [supported]: The RAG API indexes uploaded documents into PostgreSQL/PGVector; file-context mode stores extracted text in Agent instructions. Sources: librechat:librechat:rag, librechat:librechat:ocr. - sync_interval — How often does an index refresh? [unknown]: sync_interval: How often does an index refresh? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: deletion_propagation: How quickly does a deleted document disappear? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides. - index_location — Where is indexed content stored? [supported]: The operator chooses the RAG database and its location, independently of the inference provider. Sources: librechat:librechat:rag, librechat:librechat:compose-pin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:ocr, librechat:librechat:compose-pin #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-06: Grounding and retrieval quality Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial File-search citations are documented; retrieval accuracy remains unmeasured. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - citation_accuracy: Do the cited passages support the answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - cross_language: Does a question in one language find documents in another? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - no_answer_behaviour: Does it say when the corpus has no answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - observed_accuracy: How many of the question set were answered correctly? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - citations — Are answers linked to specific sources? [supported]: RAG/File Search provides retrieved source references and citation controls. Sources: librechat:librechat:rag, librechat:librechat:access. - citation_accuracy — Do the cited passages support the answer? [unknown]: citation_accuracy: Do the cited passages support the answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - cross_language — Does a question in one language find documents in another? [unknown]: cross_language: Does a question in one language find documents in another? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: no_answer_behaviour: Does it say when the corpus has no answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. - observed_accuracy — How many of the question set were answered correctly? [unknown]: observed_accuracy: How many of the question set were answered correctly? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:access #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-07: Memory and personal context Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: supported Opt-in user memory stores editable key/value context across chats; Projects and Agents provide additional persistent instructions. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. - custom_instructions — Can users set persistent instructions? [supported]: Projects retain instructions across their chats; Agents retain system instructions. Sources: librechat:librechat:projects, librechat:librechat:agents. - cross_chat_memory — Does the product remember facts across chats? [supported]: User Memory injects configured key/value entries across chats and is not semantic search over all past conversations. Sources: librechat:librechat:memory. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users add/edit/remove entries and can toggle memory when permitted. Sources: librechat:librechat:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Memory is disabled until configured and its feature permissions can be restricted by role. Sources: librechat:librechat:memory, librechat:librechat:access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:projects, librechat:librechat:agents, librechat:librechat:memory, librechat:librechat:access #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: supported Agents combine instructions, a model, knowledge and tools, with version history and a permissioned internal catalog. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: The Agent Builder creates reusable instructions/model/files/tools/skills configurations. Sources: librechat:librechat:agents. - creator_permissions — Can admins limit who creates them? [supported]: AGENTS CREATE and sharing permissions can be restricted by role; resource grants control access. Sources: librechat:librechat:access. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agent ACLs support users, groups, roles and all authenticated users when public sharing is permitted. Sources: librechat:librechat:access. - catalogue — Is there an internal assistant directory? [supported]: Agents have a marketplace/catalog and searchable builder tool library. Sources: librechat:librechat:agents. - prompt_library — Are shared prompt templates available? [supported]: Prompt resources have use/create/share/share-public permissions and ACLs. Sources: librechat:librechat:access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:access #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-02: Tools, actions and MCP Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent tools include file search, code, web and Actions, with local/remote MCP and configurable approval boundaries. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Customer-operated or third-party MCP servers, Optional separate Code Interpreter service; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - tool_approval: Agent/code environments document approval modes and individual tool-call approvals. The default policy and every external side-effect boundary were not exercised. - builtin_tools — Which tools are built in? [supported]: Agent capabilities include file search/context, web search, memory and optionally configured code execution/image tools. Sources: librechat:librechat:agents, librechat:librechat:images. - custom_actions — Can admins add API actions? [supported]: Agents support custom API Actions configured in the tool library. Sources: librechat:librechat:agents. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Configured MCP transports include stdio, SSE and Streamable HTTP; YAML and permissioned UI setup are documented. Sources: librechat:librechat:mcp, librechat:librechat:mcpcfg. - tool_auth — Do tools act as the user or as a shared account? [supported]: MCP supports configured credentials/headers and OAuth; credential and resource ownership scope depends on each server configuration. Sources: librechat:librechat:mcp, librechat:librechat:mcpcfg. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Agent/code environments document approval modes and individual tool-call approvals. The default policy and every external side-effect boundary were not exercised. Sources: librechat:librechat:agents, librechat:librechat:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:images, librechat:librechat:mcp, librechat:librechat:mcpcfg, librechat:librechat:code #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Pro search is discussed by the vendor; image-tier entitlement, custom actions and MCP remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 for evidenced search use; image and MCP plan entitlement unknown; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - builtin_tools — Which tools are built in? [partial]: The Pro/Premier pricing discussion explicitly describes frequent search and search-token overhead in the USD8 paid context. An OpenAI image integration has separate support evidence, but its plan entitlement is not verified and is not included as a Pro tool promise. Sources: t3-chat:t3-chat:r2-paid-tier-controls. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - mcp_client — Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - tool_auth — Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls ### AGT-03: Web search and deep research Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search combines configured search, scraping and optional reranking services; source queries can leave the installation boundary. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - deep_research: Agents can perform repeated tool operations and web research. No dedicated report fixture, quality result or preset research SLA was verified. - web_search — Is web search available? [supported]: Tool-capable chats/Agents can use the configured web search capability. Sources: librechat:librechat:web, librechat:librechat:agents. - admin_toggle — Can admins disable it per organisation or group? [supported]: WEB_SEARCH feature permissions control use; operators configure whether its provider stack is available. Sources: librechat:librechat:access, librechat:librechat:web. - search_provider — Which search provider handles queries, and where? [supported]: Documented choices include Serper, SearXNG, Tavily and Keenable, with Firecrawl/Tavily/Keenable scraping and optional Jina/Cohere reranking. Geography depends on the chosen services. Sources: librechat:librechat:web. - deep_research — Is multi-step research with a report available? [partial]: Agents can perform repeated tool operations and web research. No dedicated report fixture, quality result or preset research SLA was verified. Sources: librechat:librechat:agents, librechat:librechat:web. - web_citations — Are web sources cited? [supported]: The web-search guide documents source references/citations from search and fetched content. Sources: librechat:librechat:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:web, librechat:librechat:agents, librechat:librechat:access #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Search is user-selectable, with a documented one-to-five search limit; a separate deep-research product is unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 paid-search discussion; no Free parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - web_search — Is web search available? [partial]: Staff’s paid USD8 discussion confirms search consumes API/query and context costs. The FAQ exposes search on/off and1..5 URL limits, but a complete current tier-specific limit/feature matrix was not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url. - admin_toggle — Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - deep_research — Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - web_citations — Are web sources cited? [unknown]: Are web sources cited? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url ### AGT-04: Workflows and automation Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Experimental Scheduled Chats run saved Agents on cron schedules; beta Agent Events can receive external deliveries. Availability: beta Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Experimental schedules explicitly enabled, Beta Agents API for external Agent Events; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - workflow_builder: Agent Builder supports tool workflows and subagent configurations; no general business no-code flow editor was established. - event_triggers: The beta Agents API includes authenticated Agent Events. A built-in email/form trigger catalog was not verified. - workflow_builder — Is there a workflow or chain builder? [partial]: Agent Builder supports tool workflows and subagent configurations; no general business no-code flow editor was established. Sources: librechat:librechat:agents. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Scheduled Chats supports hourly/daily/weekly/custom cron with time zones, owner scope and execution checks; it is experimental and off by default. Sources: librechat:librechat:schedule. - event_triggers — Can external events start a workflow? [partial]: The beta Agents API includes authenticated Agent Events. A built-in email/form trigger catalog was not verified. Sources: librechat:librechat:api. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Agent Builder is a user UI; API-event and runtime configuration require technical deployment work. Sources: librechat:librechat:agents, librechat:librechat:schedule, librechat:librechat:api. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:schedule, librechat:librechat:api #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-05: Agentic task execution Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent runs expose reasoning/tool activity and optional approval, interruption and cooperative stop controls. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - No gather-documents, draft-summary and propose-email task was run. - Highly experimental attached workspaces are distinct from ordinary Agent tool use. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Agents execute multi-step tool workflows; code/workspace capabilities require a compatible separately deployed service. Sources: librechat:librechat:agents, librechat:librechat:code. - visible_steps — Are steps and tool calls shown? [supported]: Activity groups and tool cards distinguish preparation, execution, completion, cancellation and failure. Sources: librechat:librechat:agents. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Attached environments can expose Ask before changes/Accept edits/Full access, bounded by operator tool rules. This is configurable, not a guarantee that all side effects require confirmation. Sources: librechat:librechat:agents, librechat:librechat:code. - stop_control — Can the user stop a running task? [partial]: The release documents interruption/steering; ordinary background-tool cancellation is optional and cooperative, so an uncooperative tool may still finish. Sources: librechat:librechat:agents, librechat:librechat:releases. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:code, librechat:librechat:releases #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-06: Programmable access Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The beta Agents API provides inference, Agent management and authenticated events; deployment guards and limitations are explicit. Availability: beta Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - knowledge_api: The beta management surface includes Agent/Skill management. A complete public knowledge-ingestion contract and fixture were not verified. - api_governance: Agent access and remote-agent permissions gate APIs, with source identity bound for events. Complete logging/budget/model parity across routes was not tested. - mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established; being an MCP client does not establish that interface. - chat_api — Is there an API for chat and assistants? [supported]: Chat Completions and Open Responses interfaces expose saved Agents, with API-key or configured OIDC authentication. Sources: librechat:librechat:api. - knowledge_api — Can documents be loaded through an API? [partial]: The beta management surface includes Agent/Skill management. A complete public knowledge-ingestion contract and fixture were not verified. Sources: librechat:librechat:api. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Agent access and remote-agent permissions gate APIs, with source identity bound for events. Complete logging/budget/model parity across routes was not tested. Sources: librechat:librechat:api, librechat:librechat:access. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established; being an MCP client does not establish that interface. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:api, librechat:librechat:access #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial No official programmable enterprise interface was established; subscription-backed external-agent API usage was rejected. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_api — Is there an API for chat and assistants? [partial]: An official feedback request asks to apply subscription quota to external coding agents/API; staff closes it because the economics do not work. The FAQ URL launches a browser chat and is not a documented chat API. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url. - knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. - api_governance — Do audit, budgets and model rules apply to API use? [unknown]: Do audit, budgets and model rules apply to API use? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url ## Daily work ### WORK-01: Clients and access points Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The main deployment is a responsive browser client. Native clients, MDM and a supported sidebar extension were not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - desktop_apps: Windows and macOS apps? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - mobile_apps: Docs describe mobile navigation and temporary-chat controls in the web UI. No native iOS/Android client with company SSO was established. - browser_extension: Is there a browser extension or sidebar? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - managed_deployment: Can IT deploy and configure clients through MDM? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - client_feature_gaps: Desktop/mobile layouts expose different navigation controls; no comprehensive parity matrix was tested. - web — Is a full web client available? [supported]: A Docker/npm deployment serves a browser application at the configured server URL. Sources: librechat:librechat:firstchat, librechat:librechat:local. - desktop_apps — Windows and macOS apps? [unknown]: desktop_apps: Windows and macOS apps? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - mobile_apps — iOS and Android apps with SSO? [partial]: Docs describe mobile navigation and temporary-chat controls in the web UI. No native iOS/Android client with company SSO was established. Sources: librechat:librechat:retention, librechat:librechat:insights. - browser_extension — Is there a browser extension or sidebar? [unknown]: browser_extension: Is there a browser extension or sidebar? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: managed_deployment: Can IT deploy and configure clients through MDM? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration. - client_feature_gaps — Which features are missing on mobile? [partial]: Desktop/mobile layouts expose different navigation controls; no comprehensive parity matrix was tested. Sources: librechat:librechat:retention, librechat:librechat:insights. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:firstchat, librechat:librechat:local, librechat:librechat:retention, librechat:librechat:insights #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial A browser client and iOS TestFlight beta are documented; desktop, Android release and managed clients remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application, T3 Chat iOS TestFlight beta; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Browser account plan; iOS TestFlight beta; enterprise SSO unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=iOS. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: T3 Chat is delivered as a browser service; the FAQ documents launching new conversations through public URLs. Sources: t3-chat:t3-chat:faq-url. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - mobile_apps — iOS and Android apps with SSO? [partial]: The vendor’s September10,2026 announcement releases iOS via TestFlight explicitly as beta; Android beta is coming soon. Neither corporate SSO nor a production app-store release was verified. Sources: t3-chat:t3-chat:mobile. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-url, t3-chat:t3-chat:mobile ### WORK-02: Office suite and Teams integration Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02. #### LibreChat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### LibreChat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Configured Agent image tools generate and edit images; model service rights/costs remain separate. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - admin_control: Operators control tool credentials/configuration and Agent creation/access permissions. A dedicated per-group image-spend switch was not established. - usage_terms: What usage rights apply to output? Generated-output rights and complete per-image cost visibility were not established as a LibreChat software entitlement. - image_generation — Can users generate images, with which models? [supported]: OpenAI Image Tools and additional documented provider tools attach to an Agent; the current guide defaults OpenAI tools to gpt-image-2.5-flare. Sources: librechat:librechat:images. - image_editing — Can users edit uploaded images? [supported]: The image guide documents editing/remixing uploaded images using image IDs and compatible tools. Sources: librechat:librechat:images. - admin_control — Can admins restrict image generation? [partial]: Operators control tool credentials/configuration and Agent creation/access permissions. A dedicated per-group image-spend switch was not established. Sources: librechat:librechat:images, librechat:librechat:access. - usage_terms — What usage rights apply to output? [unknown]: usage_terms: What usage rights apply to output? Generated-output rights and complete per-image cost visibility were not established as a LibreChat software entitlement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:images, librechat:librechat:access #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-05: Voice and meetings Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial LibreChat documents STT, TTS and a hands-free conversation mode that chains them. Real-time speech-to-speech behavior, meeting outcomes and Swiss German recognition remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Current self-hosted LibreChat Speech Settings documentation retrieved 2026-10-21; no voice-latency or dialect fixture performed; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Optional configured STT/TTS engines and provider credentials; self-hosted speech services need allowedAddresses; deployment_mode=on-premise; region=Customer-selected app infrastructure; audio processing depends on browser or configured external/self-hosted speech engines, with no universal region verified; os=not specified. Limitations: - Conversation mode is a chain of transcription, text generation and playback; real-time audio-to-audio behavior, interruption and latency were not verified. - Audio location depends on the chosen engine. No meeting or Swiss German fixture was run. - dictation — Can users dictate prompts? [supported]: Speech configuration provides STT for audio input. Sources: librechat:librechat:speech. - read_aloud — Can answers be read aloud? [supported]: Speech configuration provides TTS for model responses. Sources: librechat:librechat:speech. - voice_conversation — Is a live voice mode available? [partial]: speechTab.conversationMode chains STT and TTS for hands-free turns: autoSendText sends the transcript after a configured delay, and automaticPlayback reads a completed response. Microphone recording is initially started by the user. Real-time speech-to-speech, interruption behavior and end-to-end latency were not tested. Sources: librechat:librechat:speech-conversation-r2. - meeting_summaries — Are meetings transcribed and summarised? [unknown]: No meeting capture/integration, speaker diarization or meeting-summary fixture was verified in the reviewed speech documentation. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Swiss German recognition and transcript quality were not tested; a language setting does not establish dialect accuracy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:speech, librechat:librechat:speech-conversation-r2 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-06: Data analysis and document output Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The separate Code Interpreter runs analysis and produces downloadable files; artifacts provide code/HTML/diagram previews. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Separately operated compatible Code Interpreter service, Experimental stateful workspaces only if explicitly configured; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - charts: Code execution and generated-file downloads support chart artifacts, but the shared spreadsheet/chart fixture was not run. - office_file_output: Generated files are downloadable; editable Word/Excel/PowerPoint fidelity was not established with a fixture. - canvas_editing: Artifacts render React/HTML/Mermaid content and source; a rich Office document editor was not established. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Configured Code Interpreter executes programs against uploaded files in its separate sandbox. Sources: librechat:librechat:code. - charts — Can it produce charts? [partial]: Code execution and generated-file downloads support chart artifacts, but the shared spreadsheet/chart fixture was not run. Sources: librechat:librechat:code. - office_file_output — Can it create Word, Excel or PowerPoint files? [partial]: Generated files are downloadable; editable Word/Excel/PowerPoint fidelity was not established with a fixture. Sources: librechat:librechat:code. - canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Artifacts render React/HTML/Mermaid content and source; a rich Office document editor was not established. Sources: librechat:librechat:artifacts. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:code, librechat:librechat:artifacts #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-07: Sharing and team spaces Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared chat links publish transcript snapshots and optional files. Projects are personal, and shared source permission boundaries need care. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - group_chat: Can several people chat together with the AI? Simultaneous multi-person AI group chat was not established from Projects and shareable-link documentation; link continuation creates a separate personal copy. - share_permission_boundary: Published file snapshots are served independently of the owner’s live file ACL. Sharing grants access to the published copy, not continuing source-system authorization; no restricted-source fixture was run. - share_chats — Can chats be shared inside the organisation? [supported]: Authenticated shared links are supported, with optional public viewing; public unauthenticated access is off by default. Sources: librechat:librechat:share. - team_spaces — Are shared projects or workspaces available? [unsupported]: Projects specifically cannot be shared or transferred and are personal to the creator. Shared Agents/resources are a separate capability. Sources: librechat:librechat:projects. - group_chat — Can several people chat together with the AI? [unknown]: group_chat: Can several people chat together with the AI? Simultaneous multi-person AI group chat was not established from Projects and shareable-link documentation; link continuation creates a separate personal copy. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Published file snapshots are served independently of the owner’s live file ACL. Sharing grants access to the published copy, not continuing source-system authorization; no restricted-source fixture was run. Sources: librechat:librechat:share. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:share, librechat:librechat:projects #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-08: Interface languages and accessibility Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial English, German, French and Italian UI resources are registered in the pinned client; quality and accessibility conformance were not evaluated. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - dach_language_quality: Are German, French and Italian UIs complete and natural? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. - accessibility_statement: Is there a WCAG conformance statement? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. - admin_ui_languages: Is the admin interface available in German? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. - ui_languages — Which UI languages are offered? [supported]: The client i18n implementation registers en, de, fr and it among community-maintained translations. Sources: librechat:librechat:i18n-pin. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: dach_language_quality: Are German, French and Italian UIs complete and natural? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: accessibility_statement: Is there a WCAG conformance statement? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. - admin_ui_languages — Is the admin interface available in German? [unknown]: admin_ui_languages: Is the admin interface available in German? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:i18n-pin #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Administration and governance ### ADM-01: Single sign-on and authentication Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted authentication supports OAuth/OIDC, SAML and LDAP; local/LDAP TOTP can be enforced. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - conditional_access: Entra authentication and token reuse are documented, but an actual conditional-access/device-policy login was not tested. - domain_capture: Can the company claim its email domain? Registration/domain filters were not established as a tenant-wide company-domain ownership claim. - sso_protocols — Which SSO protocols and identity providers work? [supported]: OIDC/OAuth providers include Entra, Google, Keycloak and Auth0; SAML and LDAP are documented separately. Sources: librechat:librechat:openid, librechat:librechat:saml, librechat:librechat:auth. - sso_plan — Which plan includes SSO? [supported]: The authentication configuration belongs to the MIT self-hosted project, with no separate SSO licence tariff. Sources: librechat:librechat:license, librechat:librechat:auth. - mfa — Can MFA be enforced? [supported]: ENFORCE_TWO_FACTOR_AUTHENTICATION requires local/LDAP enrollment and prevents disabling it; federated accounts depend on IdP MFA. Sources: librechat:librechat:auth. - conditional_access — Do Entra conditional-access policies apply? [partial]: Entra authentication and token reuse are documented, but an actual conditional-access/device-policy login was not tested. Sources: librechat:librechat:entra. - domain_capture — Can the company claim its email domain? [unknown]: domain_capture: Can the company claim its email domain? Registration/domain filters were not established as a tenant-wide company-domain ownership claim. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:openid, librechat:librechat:saml, librechat:librechat:auth, librechat:librechat:license, librechat:librechat:entra #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The security policy asserts MFA support without documenting enterprise SAML/OIDC administration. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Security policy refers to OAuth provider accounts and standard authentication without naming enterprise SAML/OIDC protocols or supported corporate IdPs. Sources: t3-chat:t3-chat:security. - sso_plan — Which plan includes SSO? [unknown]: Which plan includes SSO? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. - mfa — Can MFA be enforced? [partial]: The vendor asserts MFA support and recommends two-factor protection at the OAuth provider. Enforceable organization-wide MFA settings were not established. Sources: t3-chat:t3-chat:security. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:security ### ADM-02: User provisioning and lifecycle Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Entra group synchronization and federated account creation are documented; SCIM and leaver content transfer remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - scim: Is SCIM provisioning supported? SCIM was not established in the authentication/access docs or pinned repository path review. No two-user deprovisioning fixture was run. - deprovisioning: The docs provide user deletion scripts, but content ownership transfer and revocation behavior were not fixture-tested. - seat_assignment: Operators manage accounts/roles under an MIT licence; there is no per-seat licence entitlement in the scoped source. - scim — Is SCIM provisioning supported? [unknown]: scim: Is SCIM provisioning supported? SCIM was not established in the authentication/access docs or pinned repository path review. No two-user deprovisioning fixture was run. - group_sync — Are identity-provider groups synced? [supported]: With Entra OIDC token reuse, Graph groups sync at login; resource ACL principal membership has a documented cache. Sources: librechat:librechat:access, librechat:librechat:entra. - jit_provisioning — Are users created at first login? [supported]: Federated login creates accounts according to the authentication configuration; OpenID/SAML registration cannot be independently disabled. Sources: librechat:librechat:auth. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: The docs provide user deletion scripts, but content ownership transfer and revocation behavior were not fixture-tested. Sources: librechat:librechat:auth. - seat_assignment — Can admins assign and reclaim seats? [partial]: Operators manage accounts/roles under an MIT licence; there is no per-seat licence entitlement in the scoped source. Sources: librechat:librechat:auth, librechat:librechat:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:entra, librechat:librechat:auth, librechat:librechat:license #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Role permissions, resource ACLs and system grants support granular governance; the separate management UI remains preview. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, Separately deployed LibreChat Admin Panel preview; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Separate Admin Panel preview for GUI management; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - Separate admin management UI is preview; the core authorization model is documented as available. - No two-group disabled-feature fixture was run. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: ADMIN/USER and custom roles exist; capability grants can delegate selected administrative functions without full admin. Sources: librechat:librechat:access. - groups — Can permissions be set per group? [supported]: Local and Entra groups can receive ACLs, system grants and configuration overrides. Sources: librechat:librechat:access, librechat:librechat:admin. - feature_toggles — Which features can be switched on or off per group? [supported]: Permissions include Agents, MCP, prompts, memory, search, file search/citations and code execution. Sources: librechat:librechat:access. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Tenant-scoped API queries and group/configuration boundaries are documented. A commercial multi-entity contract and tested tenant isolation were not established. Sources: librechat:librechat:insights, librechat:librechat:access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:admin, librechat:librechat:insights #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional Insights reports identifiable activity; token transactions and optional tracing are separate sources of usage detail. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - breakdowns: Insights supports Agent filtering and user activity; recorded token/context cost details are per model/endpoint. Complete group/feature/assistant exports were not established. - export: Can usage data be exported? A documented complete admin analytics export and group/cost-centre dataset were not verified. - privacy_modes: Insights is off unless enabled and is capability-gated; it can display names, emails and first-message content. Pseudonymized reporting was not established. - adoption_dashboard — Is there an adoption dashboard? [supported]: Opt-in Insights reports conversations, unique users, messages, tokens, top users and recent conversations. Sources: librechat:librechat:insights. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Insights supports Agent filtering and user activity; recorded token/context cost details are per model/endpoint. Complete group/feature/assistant exports were not established. Sources: librechat:librechat:insights, librechat:librechat:tokens. - export — Can usage data be exported? [unknown]: export: Can usage data be exported? A documented complete admin analytics export and group/cost-centre dataset were not verified. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Insights is off unless enabled and is capability-gated; it can display names, emails and first-message content. Pseudonymized reporting was not established. Sources: librechat:librechat:insights. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:insights, librechat:librechat:tokens #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional token-credit balances block admission when insufficient; credit estimates differ from actual cloud invoices. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - cost_visibility: Token transactions and configured token prices support per-user/model estimates. Insights explicitly reports activity rather than monetary billing. - budgets: Optional per-user start balances and automatic refills are documented. Group/cost-centre pooled budgets were not established. - chargeback: Can costs be exported per cost centre? Cost-centre chargeback exports and reconciliation to actual vendor invoices were not established. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Token transactions and configured token prices support per-user/model estimates. Insights explicitly reports activity rather than monetary billing. Sources: librechat:librechat:tokens, librechat:librechat:insights. - budgets — Can budgets be set per user or group? [partial]: Optional per-user start balances and automatic refills are documented. Group/cost-centre pooled budgets were not established. Sources: librechat:librechat:balance. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Pinned balance middleware reserves estimated token cost and throws an error if credits cannot be reserved; no low-budget trial was run. Sources: librechat:librechat:balance-pin. - chargeback — Can costs be exported per cost centre? [unknown]: chargeback: Can costs be exported per cost centre? Cost-centre chargeback exports and reconciliation to actual vendor invoices were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:tokens, librechat:librechat:insights, librechat:librechat:balance, librechat:librechat:balance-pin #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual consumption indicators exist; organization budgets and chargeback remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 and Premier account consumption mechanics; no organization/admin budget offer asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: The paid Pro discussion and Premier support reply describe per-account cost/bucket consumption. The FAQ describes separate balance displays; exact placement and model-cost indicators are not a customer organization reporting entitlement. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets. - budgets — Can budgets be set per user or group? [unknown]: Can budgets be set per user or group? No customer organization/user-group budget assignment or cost-centre export was retrieved. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: For the documented paid-account bucket routes, exhausting both balances requires waiting for refill. This does not establish configurable user/group currency budgets, alerts or downgrade policies. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No customer organization/user-group budget assignment or cost-centre export was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Operational logs and persisted chats are available; a complete audit retention/integrity or eDiscovery system was not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - admin_events: Backend logs capture errors/debug activity and can include operational/security actions. A complete immutable admin-event schema was not established. - content_logging: Chats are persisted in MongoDB subject to retention settings; external tracing is optional. This is not a verified compliance archive. - siem_export: Operators can feed log files to external systems such as ELK. A native managed SIEM stream and integrity guarantee were not verified. - ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal hold, tamper-evident archive or complete prompt/file/connector event coverage was verified. - log_retention: The logging guide describes 14-day rotation. Rotation is not evidence of an enforced legal retention or deletion guarantee across external sinks. - admin_events — Are admin and security events logged? [partial]: Backend logs capture errors/debug activity and can include operational/security actions. A complete immutable admin-event schema was not established. Sources: librechat:librechat:logging. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: Chats are persisted in MongoDB subject to retention settings; external tracing is optional. This is not a verified compliance archive. Sources: librechat:librechat:retention, librechat:librechat:compose-pin. - siem_export — Can logs stream to a SIEM or be exported? [partial]: Operators can feed log files to external systems such as ELK. A native managed SIEM stream and integrity guarantee were not verified. Sources: librechat:librechat:logging. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal hold, tamper-evident archive or complete prompt/file/connector event coverage was verified. - log_retention — How long are logs kept? [partial]: The logging guide describes 14-day rotation. Rotation is not evidence of an enforced legal retention or deletion guarantee across external sinks. Sources: librechat:librechat:logging. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:retention, librechat:librechat:compose-pin #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The privacy policy describes vendor telemetry, not a customer compliance logging service. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [unknown]: Are admin and security events logged? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: The privacy policy collects prompts/uploads and Terms reserve review/removal for violations. A configurable customer prompt/answer compliance archive was not established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - log_retention — How long are logs kept? [unknown]: How long are logs kept? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ### ADM-07: Data loss prevention and personal data Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional server-side content filters support configured pattern detection, blocking and auditing, plus narrowly scoped Agent text redaction. External DLP integration and fixture accuracy remain unknown. Availability: source-only Delivery: native Scope: surfaces=Customer-operated web application and server; version=Development source a378657583567310c841d652b0f6b00c83e2bd6b; current Latest (dev) documentation; limited redaction announced in config v1.3.18 on 2026-10-22; plan=Customer-operated LibreChat; optional base-YAML content policies, disabled unless configured; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - Development-source finding; no running instance or AHV/IBAN fixture. - Filtering is opt-in and limited to configured sources/fields. Default patterns cover credential shapes, not every PII class. - Redaction applies only to eligible fresh Agent text; encrypted originals remain stored. - A dedicated external DLP integration remains unverified. - pii_detection — Is personal data detected in prompts and files? [partial]: Configured source-aware policies can inspect selected prompt fields and file names/extracted text/transcripts. Built-in starter rules match credentials; admins must supply additional personal-data patterns. Opaque files may be allowed by default or explicitly blocked. AHV/IBAN and confidential-file detection accuracy were not tested. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-pii-runtime, librechat:librechat:r4-patterns, librechat:librechat:r4-private-submission, librechat:librechat:r4-filter-middleware. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Configured matches can block or audit. Redaction transforms only fresh, text-only interactive Agent submissions carrying clientRequestId and a valid CREDS_KEY; edits, resumes, files, quotes and other endpoints retain blocking checks. Original text is encrypted and unindexed, rather than discarded. No running deployment was tested. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-pii-runtime, librechat:librechat:r4-patterns, librechat:librechat:r4-private-submission, librechat:librechat:r4-filter-middleware. - custom_patterns — Can admins add custom patterns or terms? [supported]: Operators can add labelled custom RE2JS regular expressions in base librechat.yaml, with optional categories. Database/role/group/user overrides cannot modify the policy; all replicas must load matching configuration. Invalid rules are rejected on configuration load. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-patterns, librechat:librechat:r4-filter-middleware. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: No first-party Purview/Netskope or other external DLP connector was established from the content-filter guide, current public repository tree and targeted official-site search. Configurable local patterns are not evidence of an external enterprise DLP integration. - filter_location — Where does filtering run? [supported]: Inspected content-filter middleware and rule evaluation run in the customer-operated LibreChat API backend. Optional extraction/OCR and inference providers remain separate data flows; no named deployment region or traffic path was tested. Sources: librechat:librechat:r4-pii-runtime, librechat:librechat:r4-filter-middleware. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-pii-runtime, librechat:librechat:r4-patterns, librechat:librechat:r4-private-submission, librechat:librechat:r4-filter-middleware, librechat:librechat:r4-config-1318 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Operators can configure prompts and usage terms; abuse moderation is distinct from semantic content-policy enforcement. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - org_instructions: Enforced model-spec presets and Agent instructions can guide behavior; model-followed instructions are not guaranteed policy enforcement. - content_filters: Automated moderation scores rate/authentication/message abuse and can ban users. Semantic topic or PII policy coverage was not established. - violation_reporting: Abuse scoring is documented, but a complete organization content-policy violation dashboard and reporting fixture were not established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Enforced model-spec presets and Agent instructions can guide behavior; model-followed instructions are not guaranteed policy enforcement. Sources: librechat:librechat:modelspec, librechat:librechat:agents. - usage_notice — Can users be required to accept a usage policy? [supported]: Interface configuration includes custom terms of service and acceptance settings. Sources: librechat:librechat:interface. - content_filters — Are content filters configurable? [partial]: Automated moderation scores rate/authentication/message abuse and can ban users. Semantic topic or PII policy coverage was not established. Sources: librechat:librechat:mod. - violation_reporting — Are policy hits visible to admins? [partial]: Abuse scoring is documented, but a complete organization content-policy violation dashboard and reporting fixture were not established. Sources: librechat:librechat:mod. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:modelspec, librechat:librechat:agents, librechat:librechat:interface, librechat:librechat:mod #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Acceptable-use terms apply, while organization policy controls remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. - content_filters — Are content filters configurable? [partial]: Terms prohibit categories of unlawful/harmful content and permit vendor review/removal or suspension. Customer configurable content filters are not established. Sources: t3-chat:t3-chat:terms. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ## Data protection and sovereignty ### DATA-01: Hosting location and data residency Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer operators choose storage and service locations; external model, OCR, search and code services need separate residency decisions. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - backups_logs_region: Logs and mounted data reside in the configured deployment; backup, telemetry and optional tracing geographies depend on operator choices and were not audited. - support_access_region: From where can vendor staff access data? No vendor or integrator support-access country restriction was reviewed for this customer-operated deployment. - swiss_hosting: A customer may run the software on Swiss infrastructure; no bundled Swiss managed inference/support commitment was established. - storage_region — Where are chats, files and indexes stored? [supported]: The reference self-hosted stack keeps application data in configured MongoDB/files and retrieval data in PGVector. Its country is chosen by the deployer. Sources: librechat:librechat:compose-pin, librechat:librechat:remote. - inference_region — Where do model calls run, per provider? [supported]: Customer-selected cloud endpoints/regions or local endpoints determine inference; hosting LibreChat in Switzerland does not place every external model there. Sources: librechat:librechat:custom, librechat:librechat:bedrock, librechat:librechat:vertex. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Logs and mounted data reside in the configured deployment; backup, telemetry and optional tracing geographies depend on operator choices and were not audited. Sources: librechat:librechat:logging, librechat:librechat:compose-pin. - support_access_region — From where can vendor staff access data? [unknown]: support_access_region: From where can vendor staff access data? No vendor or integrator support-access country restriction was reviewed for this customer-operated deployment. - swiss_hosting — Is Swiss hosting available? [partial]: A customer may run the software on Swiss infrastructure; no bundled Swiss managed inference/support commitment was established. Sources: librechat:librechat:remote, librechat:librechat:license. - residency_plan — Which plan or option provides residency? [supported]: Customer-controlled placement is a self-hosted deployment property, not a separately priced residency licence. Sources: librechat:librechat:remote, librechat:librechat:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:compose-pin, librechat:librechat:remote, librechat:librechat:custom, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:logging, librechat:librechat:license #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The privacy policy places the service under US/international processing; no EU/Swiss end-to-end option was established. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: The policy says services are provided in the United States and information is processed there or in other countries; Azure, AWS and Vercel are named. Component-specific chat/file/index storage regions are not enumerated. Sources: t3-chat:t3-chat:privacy. - inference_region — Where do model calls run, per provider? [partial]: The policy names OpenAI, Google, Anthropic and OpenRouter processing, but no provider-by-provider region, EU-only switch or customer region guarantee is supplied. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - support_access_region — From where can vendor staff access data? [unknown]: From where can vendor staff access data? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - residency_plan — Which plan or option provides residency? [unknown]: Which plan or option provides residency? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training ### DATA-02: Deployment options Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The project documents local and customer-cloud installs. A free public demo is separate from a production managed service. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, LibreChat public evaluation demo; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - multi_tenant_saas: The project operates a free public evaluation Demo, not a reviewed production business SaaS offer. Its terms permit data cleanups and disclaim persistence. - dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated dedicated production service and its contractual size floor were not established. - air_gapped: Local chat/embedding routes exist, but a complete disconnected installation and its full dependency behavior were not verified. - mode_feature_gaps: External APIs, OCR/search services and separate code runtimes need their own availability/networking; there is no verified SaaS/on-prem feature-parity matrix. - multi_tenant_saas — Is a shared SaaS offered? [partial]: The project operates a free public evaluation Demo, not a reviewed production business SaaS offer. Its terms permit data cleanups and disclaim persistence. Sources: librechat:librechat:demo, librechat:librechat:firstchat. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated dedicated production service and its contractual size floor were not established. - customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: Remote hosting documentation describes customer-selected servers/cloud hosting without a software seat minimum. Sources: librechat:librechat:remote, librechat:librechat:license. - on_premise — Can the whole platform run on customer infrastructure, from what size? [supported]: Docker/npm installation can run the application and dependencies on customer infrastructure. Sources: librechat:librechat:local, librechat:librechat:compose-pin. - air_gapped — Can it run without internet access? [partial]: Local chat/embedding routes exist, but a complete disconnected installation and its full dependency behavior were not verified. Sources: librechat:librechat:custom, librechat:librechat:ragcfg. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: External APIs, OCR/search services and separate code runtimes need their own availability/networking; there is no verified SaaS/on-prem feature-parity matrix. Sources: librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:demo, librechat:librechat:firstchat, librechat:librechat:remote, librechat:librechat:license, librechat:librechat:local, librechat:librechat:compose-pin, librechat:librechat:custom, librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:code #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial A hosted web service is offered; tenant architecture and alternative deployment contracts remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [partial]: The public web service accepts individual accounts and processes content with hosting/model providers. Its exact multitenant architecture and boundaries are not documented in the retrieved public material. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - on_premise — Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy ### DATA-03: Training use and provider retention Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The customer configures model contracts and data paths; a universal no-training or provider-retention promise was not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - vendor_training: The self-hosted application stores data in the customer’s configured stack; this architecture is not a contractual promise covering every optional external service. - provider_training: Do model providers train on it under this product's contracts? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - provider_retention: How long do model providers keep prompts, including for abuse monitoring? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - zero_retention: Is zero data retention available, and on which plan? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - human_review: Can provider staff review content? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - vendor_training — Does the vendor train on customer content? [partial]: The self-hosted application stores data in the customer’s configured stack; this architecture is not a contractual promise covering every optional external service. Sources: librechat:librechat:compose-pin, librechat:librechat:firstchat. - provider_training — Do model providers train on it under this product's contracts? [unknown]: provider_training: Do model providers train on it under this product's contracts? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: provider_retention: How long do model providers keep prompts, including for abuse monitoring? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - zero_retention — Is zero data retention available, and on which plan? [unknown]: zero_retention: Is zero data retention available, and on which plan? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. - human_review — Can provider staff review content? [unknown]: human_review: Can provider staff review content? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:compose-pin, librechat:librechat:firstchat #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial No vendor training is asserted, with provider exceptions and customer-key responsibility explicitly retained. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - vendor_training — Does the vendor train on customer content? [supported]: FAQ says T3 does not train its own models and the privacy policy says personal information is not used to train AI models. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy. - provider_training — Do model providers train on it under this product's contracts? [supported]: The FAQ says OpenAI/Anthropic defaults are not opted into training, Google paid models disable training and OpenRouter training routes are disabled. Some new models may require training and are labeled; BYOK customers manage their own provider settings. Sources: t3-chat:t3-chat:faq-training. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Normal chats have no default expiry; temporary chats default to 30 days and admins can configure broader expiry modes. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - user_deletion: Users can delete conversations/data and retention sweeps remove files. Copies, backups and external provider deletion were not end-to-end verified. - contract_end_deletion: What is deleted at contract end, and when? No commercial contract-end purge/confirmation deadline was reviewed; the Demo’s retention terms are a separate offer. - default_retention — What is retained and for how long by default? [supported]: The default temporary retention is 720 hours; normal chats persist unless configured under all/ephemeral modes. Memories do not expire with chats. Sources: librechat:librechat:retention. - admin_retention — Can admins set retention periods? [supported]: Admins set all or ephemeral retention, regular/temporary deadlines and Agent file retention. New settings apply on later saves rather than rewriting every existing record immediately. Sources: librechat:librechat:retention. - user_deletion — Can users delete their chats and files permanently? [partial]: Users can delete conversations/data and retention sweeps remove files. Copies, backups and external provider deletion were not end-to-end verified. Sources: librechat:librechat:retention, librechat:librechat:settings. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: contract_end_deletion: What is deleted at contract end, and when? No commercial contract-end purge/confirmation deadline was reviewed; the Demo’s retention terms are a separate offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:retention, librechat:librechat:settings #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Termination export responsibilities are contractual; plan-specific temporary-chat behaviour and retention remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual T3 Chat service Terms; temporary-chat Free/Pro/Premier entitlement not established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - default_retention — What is retained and for how long by default? [unknown]: The generic URL FAQ distinguishes temporary and persisted threads but does not map that feature to a named individual tier or specify server/provider/file/backup retention. No plan-specific temporary-chat retention claim is made. - admin_retention — Can admins set retention periods? [unknown]: Can admins set retention periods? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved. - user_deletion — Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved. - contract_end_deletion — What is deleted at contract end, and when? [partial]: Terms put responsibility on users to export before termination and endeavor to provide a reasonable retrieval opportunity only for vendor-convenience termination; deletion timing and certificate are unspecified. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial ClickHouse’s acquisition is sourced; the self-hosted deployment still selects its own external processors and contracts. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - subprocessor_list: Is a dated sub-processor list published? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - subprocessor_countries: Which countries do sub-processors operate in? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - change_notification: Are customers notified of sub-processor changes? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - parent_jurisdiction: ClickHouse, Inc. announced the LibreChat acquisition on 2025-11-04 from San Francisco and brought founder/team into ClickHouse. A self-hosted customer contracting entity/governing jurisdiction was not established from that announcement. - transfer_mechanism: Which transfer mechanism applies to non-EU/CH processing? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - government_access_policy: Is there a published government-access or transparency policy? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - subprocessor_list — Is a dated sub-processor list published? [unknown]: subprocessor_list: Is a dated sub-processor list published? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: subprocessor_countries: Which countries do sub-processors operate in? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - change_notification — Are customers notified of sub-processor changes? [unknown]: change_notification: Are customers notified of sub-processor changes? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: ClickHouse, Inc. announced the LibreChat acquisition on 2025-11-04 from San Francisco and brought founder/team into ClickHouse. A self-hosted customer contracting entity/governing jurisdiction was not established from that announcement. Sources: librechat:librechat:owner. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: transfer_mechanism: Which transfer mechanism applies to non-EU/CH processing? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: government_access_policy: Is there a published government-access or transparency policy? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:owner #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Named providers and a US vendor address are public, without a complete processor-country or transfer contract matrix. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [partial]: The May31,2025 privacy policy names Azure, AWS, Vercel, OpenAI, Google, Anthropic and OpenRouter, explicitly non-exhaustively. This is not established as a complete Article28 subprocessor schedule. Sources: t3-chat:t3-chat:privacy. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved. - change_notification — Are customers notified of sub-processor changes? [partial]: Privacy policy says material changes are posted with an updated effective date. A processor-addition notice period and objection right are not specified. Sources: t3-chat:t3-chat:privacy. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The policy and Terms identify T3 Tools Inc with a San Francisco address and US/California legal context. A separate parent entity, incorporation jurisdiction and ownership were not independently established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The policy allows disclosures for subpoenas, warrants and legal investigations. No separate transparency report or detailed challenge/notification policy was retrieved. Sources: t3-chat:t3-chat:privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ### DATA-06: Contracts and regulatory coverage Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict. #### LibreChat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public consumer/service terms use California law; an enterprise GDPR/Swiss DPA remains unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [unknown]: Is a DPA available, and is it negotiable? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [unknown]: Does the DPA cover revDSG and GDPR? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - governing_law — Which law and court govern the contract? [supported]: Terms section19 uses California law and individual JAMS arbitration in Santa Clara County, with small-claims/injunction exceptions and state/federal Santa Clara courts where arbitration does not apply. Sources: t3-chat:t3-chat:terms. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - sector_materials — Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### DATA-07: Certifications and attestations Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product. #### LibreChat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### DATA-08: Encryption and key control Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN). #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Network and storage security depend on the customer’s deployment; application authentication does not certify encryption of all stored content. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - encryption_at_rest: Is data encrypted at rest? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides. - customer_managed_keys: Operators own infrastructure and application secrets; a documented product HYOK/customer-managed content-encryption service was not verified. - tenant_isolation: How are customers separated in shared SaaS? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides. - encryption_at_rest — Is data encrypted at rest? [unknown]: encryption_at_rest: Is data encrypted at rest? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: Operators own infrastructure and application secrets; a documented product HYOK/customer-managed content-encryption service was not verified. Sources: librechat:librechat:auth, librechat:librechat:compose-pin. - private_networking — Is private connectivity or IP restriction available? [supported]: Operators deploy the stack on their own network and configure reverse proxies/HTTPS for remote access. Sources: librechat:librechat:remote, librechat:librechat:local. - tenant_isolation — How are customers separated in shared SaaS? [unknown]: tenant_isolation: How are customers separated in shared SaaS? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:auth, librechat:librechat:compose-pin, librechat:librechat:remote, librechat:librechat:local #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer-operated message storage and configurable local/external inference establish part of the content-access boundary. A LibreChat-scoped staff/sub-processor secrecy undertaking or professional-secrecy offering remains unverified. Availability: unknown Delivery: unknown Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; message schema and reference Compose pinned to v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional commercial secrecy terms unverified. Public Demo and website policies checked only to distinguish their scope; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected application, storage and model-service locations; no DE/CH professional-secrecy contract variant verified; os=not specified. Limitations: - The secrecy undertaking, sub-processor coverage, offering and professional-secrecy-specific documentation remain unknown. - content_access: Operator permissions, vendor/support grants, optional service access and provider staff access were not tested or contractually verified. - Technical data controls, a DPA, privacy wording and no-training statements do not establish the requested contractual undertaking. No legal compliance assessment is made. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No LibreChat-scoped § 203 StGB / Art. 321 StGB undertaking binding vendor staff was obtained from the reviewed project documentation and public legal pages. The website privacy policy expressly excludes the self-hosted application; ClickHouse ownership does not establish a product-specific agreement. Sources: librechat:librechat:siteprivacy, librechat:librechat:owner. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: No self-hosted LibreChat professional-secrecy annex or documented extension to sub-processors was obtained. The separate Demo policy describes processor instruction/security obligations, which do not establish the undertaking requested here or coverage of a customer deployment. Sources: librechat:librechat:secrecy-demo-policy. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No dedicated professional-secrecy edition, paid add-on, eligible plan or price was established in the public project/legal materials and targeted searches. The public Demo is evaluation-only and excludes confidential or regulated data; it is a separate surface. Sources: librechat:librechat:demo. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The pinned reference deployment mounts customer-controlled MongoDB, uploads and logs; the message schema declares ordinary text/content fields. This places host/database operators inside the application trust boundary (an architectural inference, not a permissions audit). The first-chat and endpoint guides route prompts to a selected local or external model with customer credentials. Vendor/support access, optional service operators and provider human access remain deployment- and contract-specific and unverified. Sources: librechat:librechat:compose-pin, librechat:librechat:secrecy-message-pin, librechat:librechat:firstchat, librechat:librechat:custom. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public installation, endpoint and privacy documents describe technical data paths and distinguish website, Demo and self-hosted software. No LibreChat-specific DE/CH secrecy contract template, covered-party annex or professional-body guidance was located in the reviewed sources. Sources: librechat:librechat:firstchat, librechat:librechat:siteprivacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:siteprivacy, librechat:librechat:owner, librechat:librechat:secrecy-demo-policy, librechat:librechat:demo, librechat:librechat:compose-pin, librechat:librechat:secrecy-message-pin, librechat:librechat:firstchat, librechat:librechat:custom #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public policies describe vendor/provider content processing, but professional-secrecy contracts and a business plan remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual account service; no business/professional-secrecy offer verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US/international policy; no DE/CH-specific arrangement verified; os=not specified. Limitations: - No-training statements and personal account terms are not a professional-secrecy undertaking. - No legal suitability or compliance conclusion. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public DPA or signed/signon §203 StGB/Art321 StGB professional-secrecy undertaking covering T3 staff was retrieved from the Terms, privacy/security policies or targeted first-party searches. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy names hosting/model services but does not establish a dedicated professional-secrecy undertaking binding them. Its existence and flow-down are unknown. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: A team/business offer itself remains unverified; no professional-secrecy-specific tier, dedicated package or paid add-on was established. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Privacy policy sends input to selected OpenAI/Google/Anthropic/OpenRouter services; Terms reserve vendor review/removal of content upon apparent violations. This establishes processing/review possibilities, not an exhaustive plaintext staff/provider access matrix or protected-profession arrangement. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public consumer/service Terms and privacy/security pages were reviewed, with targeted §203/Art321/professional-secrecy searches. No specific template, protected-profession data-flow statement or professional-body guidance was retrieved; no private agreement was requested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ## Commercials and vendor ### VEN-01: Pricing model and list prices Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial MIT software has no licence subscription; hosting, inference and optional runtime services are separately procured. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - add_ons: Optional external code/OCR/search/image services need separately configured endpoints and credentials. Their rates depend on the operator’s contracts. - overage: Provider APIs charge their account holder; internal credit balances are governance configuration rather than a single LibreChat usage tariff. - pricing_unit — What is the pricing unit? [supported]: The pinned MIT permission grant has no per-user fee; self-hosting and model accounts are customer responsibilities. Sources: librechat:librechat:license, librechat:librechat:firstchat. - list_prices — What are list prices per plan, with date and currency? [supported]: The repository’s MIT licence permits use without a software fee as retrieved 2026-10-21; there is no bundled inference subscription in this scope. Sources: librechat:librechat:license, librechat:librechat:firstchat. - included_usage — What usage is included? [supported]: LibreChat ships with no model API key and no included provider token balance. Sources: librechat:librechat:firstchat. - add_ons — Which features cost extra? [partial]: Optional external code/OCR/search/image services need separately configured endpoints and credentials. Their rates depend on the operator’s contracts. Sources: librechat:librechat:code, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:images. - overage — What do usage beyond limits and premium models cost? [partial]: Provider APIs charge their account holder; internal credit balances are governance configuration rather than a single LibreChat usage tariff. Sources: librechat:librechat:balance, librechat:librechat:tokens, librechat:librechat:firstchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:firstchat, librechat:librechat:code, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:images, librechat:librechat:balance, librechat:librechat:tokens #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual subscription prices are supported by vendor replies; quotas are cost-based and checkout/organization details are incomplete. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Staff pricing replies are first-party but undated; current checkout amounts and tax/plan availability were not observed. - pricing_unit — What is the pricing unit? [supported]: Evidence describes monthly individual Pro/Premier subscriptions, optional customer provider keys and cost-based included use. No organizational seat/pool contract is established. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage. - list_prices — What are list prices per plan, with date and currency? [partial]: Vendor replies confirm USD8/month paid-tier context and Premier USD50/month plus applicable tax. No checkout was completed and no business price was retrieved; dates of the undated replies are unknown. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility. - included_usage — What usage is included? [supported]: Included usage is represented by Base and Overage balances, refilling four-hourly/monthly. The FAQ’s20/200 example is not the actual plan quota and the former1500+100 message claim is not used. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:billing-change. - add_ons — Which features cost extra? [partial]: Customer OpenRouter/OpenAI API keys incur direct provider charges. Staff says a top-up product has not been offered since the new billing model and options are only being considered. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai. - overage — What do usage beyond limits and premium models cost? [partial]: The Overage bucket is a monthly included-usage bucket, not an established published dollar-per-token overage tariff. Extra usage via own keys is billed by the customer provider; current model/route tariffs are not fully mapped. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:premier. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai ### VEN-02: Scenario cost Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21: zero standard licence plus a disclosed Swiss infrastructure/operations and direct-BYO-model budget. Annual CHF/EUR figures are floors plus named unknown costs. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Analyst-selected direct OpenAI API proxy, not a bundled model, Assumed operations staffing; optional commercial services excluded; deployment_mode=customer-cloud; region=Azure Switzerland North for the reference application infrastructure; standard OpenAI API inference has no Swiss/EU residency assumption; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21 are analyst inputs, not vendor sizing or an uptime promise. - The budget is a floor because named infrastructure and service costs are unpriced. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 200 users, 12 months excluding VAT: from CHF 34778.28 / EUR 37651.06 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 4749.26, operations CHF 30000.00, and BYO model usage USD 475.20. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 1,000 users, 12 months excluding VAT: from CHF 88600.40 / EUR 95919.02 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 12605.23, operations CHF 75000.00, and BYO model usage USD 2376.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 5,000 users, 12 months excluding VAT: from CHF 189541.24 / EUR 205197.83 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 32214.49, operations CHF 150000.00, and BYO model usage USD 11880.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - variable_share — Which part depends on usage? [partial]: Shared mix is 60% light at 100, 30% regular at 400 and 10% power at 1,500 messages/user/month, or 330 weighted messages. Each message is 3,000 input and 600 output tokens. Direct BYO proxy is gpt-6-luna, reasoning effort none, Standard short-context uncached rates USD 0.10/0.50 per million input/output tokens. It costs USD 2.376/user/year before optional tools, embedding, caching or regional processing. This proxy is an analyst assumption, not the product default. Sources: librechat:librechat:cost-model, librechat:librechat:cost-effort. - unknown_parts — Which costs could not be priced? [partial]: Unpriced additions are file/object storage beyond the assumed 500 GB PostgreSQL storage, VM OS/data disks, backup excess, egress/load balancers, Redis or additional database services, high availability, embeddings, OCR, search, audio/images, integration work and optional commercial services. MongoDB remains the primary store, so its infrastructure, file storage and other required dependencies are additional unpriced items; PostgreSQL is only the shared RAG/reference compute assumption. The shared VM/PG sizes have not been load-tested and do not replace each product’s documented runtime dependencies. Sources: librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multiplying individual list prices yields conditional licence floors, not a verified organization quote or usage-complete TCO. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Conditional independent Pro/Premier account multiplication; no organization plan verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Known price floor + unknown components; no complete year-one TCO, seat commitment or sufficient-usage guarantee. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months,list prices,exVAT,no negotiated discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330,each3000 input+600 output tokens incl retrieval. Vendor subscription usage remains subject to cost/refill limits; no fixed default/recommended model or complete tariff is published, so coverage and variable extra cost stay unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; divideUSD by1.1215 then multiplyEUR by0.9237. For200 separate accounts: Pro from USD19,200/EUR17,119.93/CHF15,813.68 + unknown; Premier reference USD120,000/EUR106,999.55/CHF98,835.49 + unknown. Bulk purchase and business-governance fit unverified. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - cost_1000 — Year-one cost at 1,000 users? [partial]: Same assumptions,1000 separate accounts: Pro from USD96,000/EUR85,599.64/CHF79,068.39 + unknown; Premier reference USD600,000/EUR534,997.77/CHF494,177.44 + unknown. Not a1000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - cost_5000 — Year-one cost at 5,000 users? [partial]: Same assumptions,5000 separate accounts: Pro from USD480,000/EUR427,998.22/CHF395,341.95 + unknown; Premier reference USD3,000,000/EUR2,674,988.85/CHF2,470,887.20 + unknown. Not a5000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - variable_share — Which part depends on usage? [partial]: Included usage consumes a cost meter with no complete published tariff/default model. For an optional direct-provider BYOK comparison only, the shared gpt-6-luna effort-none Standard proxy is USD0.10 input/USD0.50 output per1M and USD2.376/user/year at the shared mix, excluding cache/tools/embeddings/regional uplift. This exact model/route is not verified selectable in T3 and is not added to the subscription floor as though it were a vendor tariff. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model. - unknown_parts — Which costs could not be priced? [supported]: Unpriced: enterprise/bulk entitlement, organization features, exact current checkout prices, model availability and complete token/search/file tariff, whether the shared workload fits refill quotas, direct-provider/OpenRouter route charges, regional processing and support/implementation. No assumed wholesale discount or model-cost subsidy. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:byok-router. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:byok-router ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: supported Customers can self-install without licence payment; the public demo is an evaluation-only alternative. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server, LibreChat public evaluation demo; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. - free_tier — Is there a free tier for business use? [supported]: MIT self-installation permits organizational use without a software licence fee. Sources: librechat:librechat:license. - self_serve_trial — Is a self-serve business trial available? [supported]: Self-installation has no trial clock or software card requirement; the free hosted Demo can be tried separately under its terms. Sources: librechat:librechat:local, librechat:librechat:demo. - trial_scope — Do trials include SSO, connectors and admin features? [supported]: Self-installed instances can configure SSO, Agents, file retrieval and administration with their own service accounts. It is not evidence that every experimental add-on is enabled by default. Sources: librechat:librechat:auth, librechat:librechat:agents, librechat:librechat:rag. - sales_gate — Does meaningful evaluation require sales contact? [supported]: The documented Docker install does not require sales approval; optional third-party services have separate account requirements. Sources: librechat:librechat:local, librechat:librechat:firstchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:local, librechat:librechat:demo, librechat:librechat:auth, librechat:librechat:agents, librechat:librechat:rag, librechat:librechat:firstchat #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Free usage is in the Terms; a business-specific trial and enterprise evaluation path remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [partial]: Terms say services are free up to unspecified usage limits and paid resources may be required. Organizational acceptance is allowed, but no free business admin entitlement is established. Sources: t3-chat:t3-chat:terms. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created. - sales_gate — Does meaningful evaluation require sales contact? [partial]: A public browser service and free-limited offer are documented; business-specific meaningful evaluation and any sales gate cannot be determined without an established business offer. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The MIT licence has no seat or contract-term subscription; optional service contracts are outside that licence. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - cancellation: An operator can stop running the application; this does not cancel its separately purchased cloud/model services or establish deletion of all copies. - local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR commercial invoicing from a European entity was not established for optional project services. - transparency_class: Source licensing is transparent; a complete all-in hosted/support/inference tariff is not included in this self-hosted offer. - minimum_commitment — What seat or spend minimum applies? [supported]: The MIT permission grant has no user-count or spending minimum for software use. Sources: librechat:librechat:license. - contract_length — What contract lengths are offered? [supported]: There is no monthly/annual licence subscription in the MIT permission grant. External hosting/API contracts are separate. Sources: librechat:librechat:license. - cancellation — How can the contract be cancelled or reduced? [partial]: An operator can stop running the application; this does not cancel its separately purchased cloud/model services or establish deletion of all copies. Sources: librechat:librechat:license, librechat:librechat:local. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR commercial invoicing from a European entity was not established for optional project services. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Source licensing is transparent; a complete all-in hosted/support/inference tariff is not included in this self-hosted offer. Sources: librechat:librechat:license, librechat:librechat:firstchat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:local, librechat:librechat:firstchat #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual monthly upgrades/downgrades are documented; business minimums and European invoicing remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [partial]: The public evidence concerns individual accounts and monthly prices, not a minimum team-seat/spend commitment. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier. - contract_length — What contract lengths are offered? [supported]: Vendor replies confirm monthly Premier pricing and billing periods; no signed annual or business-term offer was retrieved. Sources: t3-chat:t3-chat:premier. - cancellation — How can the contract be cancelled or reduced? [supported]: Terms permit account cancellation at any time without refunds. Staff says upgrades take effect immediately and downgrades at the billing-period end. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? No team minimum, European contracting entity or CHF/EUR invoice entitlement was retrieved. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: some individual prices are confirmed in undated staff replies, complete final checkout requires billing information, quotas are not a public token tariff, and a business offer remains unverified. Sources: t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage ### VEN-05: Source licence Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned main repository is MIT licensed; no user-count or product-branding clause appears in that licence. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - enterprise_features_closed: The project documents a separate preview admin panel and optional code services. A closed enterprise-edition boundary for the main repository was not established. - licence_type — Which licence applies to each component? [supported]: The main client/server repository at v0.8.8 is MIT. Separate Code Interpreter, admin-panel, connector or hosted-service components need their own licence review. Sources: librechat:librechat:license. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: The MIT grant permits use/modification/distribution subject to retaining its copyright and permission notice; it includes no 50-user cap or mandatory UI branding clause. Sources: librechat:librechat:license. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: The project documents a separate preview admin panel and optional code services. A closed enterprise-edition boundary for the main repository was not established. Sources: librechat:librechat:admin, librechat:librechat:code, librechat:librechat:license. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:admin, librechat:librechat:code #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The hosted service is proprietary; clone hackathons and T3 Code are separate products. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - licence_type — Which licence applies to each component? [supported]: Terms grant a personal nonassignable service licence and prohibit copying, modification, reverse engineering and source extraction, subject to third-party software rights. Sources: t3-chat:t3-chat:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: Terms reserve vendor trademarks and prohibit sublicensing/renting/providing service access to others; each account is personal and cannot be shared. Sources: t3-chat:t3-chat:terms. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? No supported self-host licence, open-source core/enterprise split or enterprise edition licence was retrieved. Public third-party clones are not licensed distributions of the hosted product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Users can export conversations in machine-readable formats; organization-wide Agent/knowledge exit completeness remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - chat_export: Pinned client code exports a user-selected conversation, including optional branches/options. A documented admin bulk export of every user’s chats was not established. - assistant_export: Beta management APIs expose Agent/Skill objects, but a reusable complete assistant/prompt export fixture was not verified. - knowledge_export: Can knowledge bases and their sources be exported? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned. - post_termination_window: How long can data be retrieved after termination? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned. - chat_export — Can admins export all chats? [partial]: Pinned client code exports a user-selected conversation, including optional branches/options. A documented admin bulk export of every user’s chats was not established. Sources: librechat:librechat:export-pin. - assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: Beta management APIs expose Agent/Skill objects, but a reusable complete assistant/prompt export fixture was not verified. Sources: librechat:librechat:api. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: knowledge_export: Can knowledge bases and their sources be exported? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned. - export_format — Are formats documented and machine-readable? [supported]: Conversation export code supports JSON, CSV, Markdown and text. This establishes format availability, not complete organization-data portability. Sources: librechat:librechat:export-pin. - post_termination_window — How long can data be retrieved after termination? [unknown]: post_termination_window: How long can data be retrieved after termination? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:export-pin, librechat:librechat:api #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms require pre-termination export, but a documented organizational export package was not established. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - export_format — Are formats documented and machine-readable? [unknown]: Are formats documented and machine-readable? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - post_termination_window — How long can data be retrieved after termination? [partial]: Users must export before termination. If the vendor terminates for convenience it will endeavor to allow a reasonable retrieval opportunity; no fixed post-termination window is guaranteed. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-07: Support and service levels Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public project/community channels are available; a binding business support SLA was not established. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - support_channels: Public GitHub issue reporting and community channels are documented; a supported enterprise channel/response-time matrix was not established for MIT self-hosting. - support_languages: Is support available in German, French or Italian? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - regional_presence: Is there a DACH or Swiss entity, team or partner? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - uptime_sla: Is there an uptime SLA with credits? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - status_page: Is there a public status page with history? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - support_channels — Which support channels are available on each plan? [partial]: Public GitHub issue reporting and community channels are documented; a supported enterprise channel/response-time matrix was not established for MIT self-hosting. Sources: librechat:librechat:logging, librechat:librechat:firstchat. - support_languages — Is support available in German, French or Italian? [unknown]: support_languages: Is support available in German, French or Italian? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: regional_presence: Is there a DACH or Swiss entity, team or partner? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - uptime_sla — Is there an uptime SLA with credits? [unknown]: uptime_sla: Is there an uptime SLA with credits? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. - status_page — Is there a public status page with history? [unknown]: status_page: Is there a public status page with history? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:firstchat #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Email support and official feedback are public, without a retrieved SLA or regional-language contract. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: The FAQ lists a support email and official feature/bug board; plan-specific response targets are not published there. Sources: t3-chat:t3-chat:faq-support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: The vendor publishes a San Francisco contact address. A DACH/Swiss entity, partner or support team was not established. Sources: t3-chat:t3-chat:privacy. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-support, t3-chat:t3-chat:privacy ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### LibreChat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosting and Agent use have public setup guides; vendor-led training/adoption packages were not verified. Availability: generally-available Delivery: native Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified. Limitations: - onboarding_service: Is guided onboarding included? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - user_training: Is end-user training offered, in which languages? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - use_case_library: The Agent and setup guides include examples and tutorials; a role-based enterprise training/use-case program was not established. - adoption_programme: Is there a champion or adoption programme? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - service_cost: Which services cost extra? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - onboarding_service — Is guided onboarding included? [unknown]: onboarding_service: Is guided onboarding included? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - user_training — Is end-user training offered, in which languages? [unknown]: user_training: Is end-user training offered, in which languages? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - use_case_library — Are role-based use cases and templates provided? [partial]: The Agent and setup guides include examples and tutorials; a role-based enterprise training/use-case program was not established. Sources: librechat:librechat:agents, librechat:librechat:firstchat. - adoption_programme — Is there a champion or adoption programme? [unknown]: adoption_programme: Is there a champion or adoption programme? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. - service_cost — Which services cost extra? [unknown]: service_cost: Which services cost extra? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:firstchat #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Sources ### librechat:librechat:custom Custom endpoints. Operators configure compatible endpoints and customer-held keys, including local and hosted services. - URL: https://www.librechat.ai/docs/quick_start/custom_endpoints - Locator: Endpoint setup; API key; base URL; model list - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:azure Azure OpenAI configuration. Azure OpenAI uses customer deployment groups, instance names and credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/ai_endpoints/azure - Locator: Deployment groups; API credentials - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:bedrock AWS Bedrock object structure. Bedrock routes use customer AWS configuration and region selection. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/aws_bedrock - Locator: Region; credentials; model selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:vertex Anthropic Vertex AI configuration. Claude can run through customer Google Vertex AI credentials and regions. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/anthropic_vertex - Locator: Project and region configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:modelspec Model specifications. Administrators can enforce configured model presets and defaults; available endpoints still depend on customer credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/model_specs - Locator: enforce; preset; modelSelect; addedEndpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:agents Agents. Agents combine instructions, models, files, tools, skills and sharing permissions, with visible execution and configurable approval. - URL: https://www.librechat.ai/docs/features/agents - Locator: Builder; Capabilities; Version history; Sharing; Activity; tool approval - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:ocr OCR for documents. OCR can augment text extraction, or files can be sent to compatible provider APIs; format and model limitations remain. - URL: https://www.librechat.ai/docs/features/ocr - Locator: File Context; Upload as Text; Optional OCR; Limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:releases LibreChat v0.8.8 release. The stable release documents agent controls, current model updates and explicitly experimental schedules/workspaces and beta Agents API. - URL: https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.8 - Locator: Highlights, 2026-10-01 - Evidence kind: documented - Source date: 2026-10-01 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:faq-training T3 Chat FAQ. The vendor says it does not train models, configures OpenAI/Anthropic/paid Google/OpenRouter no-training where possible, labels exceptions and makes BYOK customers responsible for settings. - URL: https://t3.chat/faq - Locator: Do you use my data for training? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:billing-change Usage model change. Vendor replies confirm current cost-based usage and that an USD8 subscription can still use expensive models within cost limits. - URL: https://feedback.t3.chat/p/t3-feels-nerfed-now - Locator: Mark Florkowski Team replies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-paid-tier-controls Pro/Premier vendor replies. The vendor discusses USD8 Pro usage/search costs, optional OpenRouter keys and Premier USD50/month; this does not establish Free parity or a complete model matrix. - URL: https://feedback.t3.chat/p/new-tier-in-between-pro-and-premier - Locator: Mark Florkowski Team: cost explanation, OpenRouter direct billing, USD50 Premier and plan changes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-pro-context-byok Context and own-key controls. Vendor replies document context restrictions on the USD8 tier and optional own-key fallback without publishing a complete current model/file matrix. - URL: https://feedback.t3.chat/p/premium-requests-for-large-context-windows - Locator: Mark Florkowski Team replies on USD8 limits, higher tier, model switching and OpenRouter fallback - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:changelog Changelog of new features. A vendor reply says major-feature changelog is in Discord and a website version is intended; the website request remains Planned. - URL: https://feedback.t3.chat/p/changelog-of-new-features - Locator: Planned status and Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:firstchat Your first chat. LibreChat ships without a model key; the public demo is for evaluation rather than private or durable data. - URL: https://www.librechat.ai/docs/quick_start/first_chat - Locator: Software you host yourself; endpoint credentials; public demo - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:code Code Interpreter API. A separate code execution service supports multiple languages and downloadable generated files; stateful/attached modes are experimental. - URL: https://www.librechat.ai/docs/features/code_interpreter - Locator: Setup; self-hosted service; workspace permissions; generated files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:license LibreChat v0.8.8 MIT licence. The pinned repository is MIT licensed with copyright/permission notice preservation and an as-is disclaimer. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/LICENSE - Locator: LICENSE, permission grant and notice requirement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:ragcfg RAG API configuration. OpenAI, Hugging Face and Ollama embedding configurations are documented; image choice affects local embedding support. - URL: https://www.librechat.ai/docs/configuration/rag_api - Locator: Embedding providers; lite image; full image - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:access Granular access control. Roles, groups and resource ACLs govern features and sharing, with Entra groups synchronized at sign-in. - URL: https://www.librechat.ai/docs/features/access_control - Locator: Feature permissions; Resource ACLs; System grants; Groups - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:admin LibreChat Admin Panel. A separate browser management panel is available for testing and uses the underlying LibreChat admin APIs. - URL: https://www.librechat.ai/docs/features/admin_panel - Locator: Status Preview; separate service; admin APIs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:balance Balance configuration. Optional token-credit balances initialize and refill user credits; tracking is disabled by default. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/balance - Locator: enabled; startBalance; refill configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mod Automated moderation. Moderation scores abusive login/registration/message activity and may ban users; it is not a documented content DLP classifier. - URL: https://www.librechat.ai/docs/features/mod_system - Locator: Violation scoring and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:balance-pin LibreChat balance admission implementation. The pinned middleware reserves user credits and throws a TOKEN_BALANCE error when the reservation cannot be admitted. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/packages/api/src/middleware/checkBalance.ts - Locator: packages/api/src/middleware/checkBalance.ts, checkBalance - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: packages/api/src/middleware/checkBalance.ts ### t3-chat:t3-chat:faq-usage T3 Chat FAQ. Base refills every four hours and Overage monthly; usage reserves then settles request cost and blocks until refill when both are depleted. Example20/200 points are illustrative, not published quota sizes. - URL: https://t3.chat/faq - Locator: How does the usage meter work? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-premier-buckets Premier usage-limit support. The identifiable vendor reply specifically applies the FAQ bucket mechanics to a Premier account. - URL: https://feedback.t3.chat/p/quickly-reaching-usage-limits-on-premier-plan - Locator: Mark Florkowski Team reply explaining exhausted monthly overage and four-hour bucket - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:rag RAG API. A separate RAG API indexes uploaded content in PostgreSQL/PGVector for retrieval. - URL: https://www.librechat.ai/docs/features/rag_api - Locator: Architecture; document indexing; embeddings; semantic search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:text Upload files as text. Text upload injects extracted file content rather than relying only on vector retrieval. - URL: https://www.librechat.ai/docs/features/upload_as_text - Locator: Full text extraction and context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:filecfg File configuration. File limits and formats are configurable by endpoint and file processing route. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/file_config - Locator: File limits; MIME patterns; provider routes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:r4-spreadsheet-parser LibreChat spreadsheet text parser. The built-in parser accepts XLSX/XLS/ODS and serializes each sheet as its name followed by CSV values. It does not establish preserved workbook layout, recalculated formulas or fixture accuracy. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/files/documents/crud.ts - Locator: getParserForMimeType; excelSheetToText, lines 109-129 - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/files/documents/crud.ts ### librechat:librechat:r4-text-current LibreChat current Upload as Text guide. The development guide lists XLSX/XLS/ODS parsing up to 15 MB and token-bounded text injection, not a formatted spreadsheet editor. - URL: https://www.librechat.ai/docs/features/upload_as_text - Locator: Built-in parser; supported documents; truncation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### librechat:librechat:projects Projects. Projects persist files and instructions across a user’s chats but cannot be shared or transferred. - URL: https://www.librechat.ai/docs/features/projects - Locator: Availability; personal scope; files and instructions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:sharepoint SharePoint and OneDrive integration. The Microsoft file picker uses Entra token reuse and delegated on-behalf-of downloads to attach files. - URL: https://www.librechat.ai/docs/configuration/sharepoint - Locator: Prerequisites; delegated permissions; admin consent - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mcp MCP. MCP servers can be configured through YAML or the permission-gated UI, including per-user OAuth. - URL: https://www.librechat.ai/docs/features/mcp - Locator: YAML/UI setup; authentication; ownership and selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mcpcfg MCP server configuration. Configuration includes stdio, SSE and Streamable HTTP transports and server-specific credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/mcp_servers - Locator: Transport examples; headers; OAuth - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:compose-pin LibreChat Docker service configuration. The pinned example runs a MongoDB primary store and a separate PGVector/RAG service with customer-mounted data. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/docker-compose.yml - Locator: docker-compose.yml, api/mongodb/vectordb/rag_api services - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: docker-compose.yml ### librechat:librechat:memory User memory. Configured user memory stores cross-chat key/value context with user editing controls; it does not index all past chats. - URL: https://www.librechat.ai/docs/features/memory - Locator: Key/value store; controls; disabled by default - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:images Image generation and editing. Agents can use configured image tools for generation/editing; provider credentials and model parameters are separate. - URL: https://www.librechat.ai/docs/features/image_gen - Locator: OpenAI Image Tools; provider setup; admin configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:web Web search. Search can use Serper, SearXNG, Tavily or Keenable, with independently configured scraping and optional reranking. - URL: https://www.librechat.ai/docs/features/web_search - Locator: Provider, scraper and reranker configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:faq-url T3 Chat FAQ. A new-chat URL selects a model, reasoning effort, search on/off, one to five searches, a profile and temporary/persisted storage mode. - URL: https://t3.chat/faq - Locator: Custom search URLs and query parameter table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:schedule Scheduled Chats. Opt-in experimental schedules execute saved Agents with cron/time zones and recheck access and balance before running. - URL: https://www.librechat.ai/docs/features/scheduled_chats - Locator: Experimental and disabled by default; runtime and permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:api Agents API beta. The beta API exposes chat/Responses inference, Agent/Skill management and authenticated event delivery. - URL: https://www.librechat.ai/docs/features/agents_api - Locator: Inference; management; Agent Events; authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:api-request Subscription-backed API request. Staff rejects the economics of applying a T3 Chat subscription to external coding-agent/API usage; an official general chat API is not established. - URL: https://feedback.t3.chat/p/allow-t3-chat-subscription-to-power-external-coding-agents-or - Locator: Closed status and Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:retention Temporary chat and data retention. Operators configure expiry for chats/messages/files/shared links; normal chats do not expire by default and memories are excluded. - URL: https://www.librechat.ai/docs/features/temporary_chat - Locator: Default 30-day temporary retention; all/ephemeral; deadlines; memories - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:insights Admin Insights. Insights reports persisted MongoDB activity and identifiable recent conversations; it is not monetary billing analytics. - URL: https://www.librechat.ai/docs/features/insights - Locator: Opt-in; capabilities; metrics; tenant scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:local Docker installation. Docker self-installation runs LibreChat with its configured service dependencies. - URL: https://www.librechat.ai/docs/local/docker - Locator: Installation; configuration; updating - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:mobile Mobile App. The vendor released an iOS TestFlight beta on September10,2026 and says Android beta is coming soon. - URL: https://feedback.t3.chat/en/p/mobile-app-77 - Locator: Mark Florkowski, Team, pinned September10,2026 announcement - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### librechat:librechat:speech Speech configuration. Administrators configure audio provider engines and models separately from text generation. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/speech - Locator: Speech-to-text and text-to-speech engines - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:speech-conversation-r2 LibreChat conversation-mode speech settings. Conversation mode chains transcription, auto-send and TTS playback for hands-free turns after microphone activation; engines and audio routing are separately configured. - URL: https://www.librechat.ai/docs/configuration/stt_tts - Locator: Speech Tab: conversationMode, autoTranscribeAudio, autoSendText, automaticPlayback; engine and allowedAddresses settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:artifacts Artifacts. Artifacts render generated React, HTML and Mermaid content in the chat interface. - URL: https://www.librechat.ai/docs/features/artifacts - Locator: React, HTML and Mermaid previews - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:share Shareable links. Shared links publish a transcript branch and optional file snapshots independently of the owner’s live file ACL. - URL: https://www.librechat.ai/docs/features/shareable_links - Locator: Authentication defaults; file snapshots; continuation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:i18n-pin LibreChat locale registration. The pinned client registers English, German, French and Italian translations among its supported locales. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/client/src/locales/i18n.ts - Locator: client/src/locales/i18n.ts, language resources - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: client/src/locales/i18n.ts ### librechat:librechat:auth Authentication system. Local/LDAP accounts can be required to use TOTP; federated MFA belongs to the identity provider and account creation/deletion scripts are documented. - URL: https://www.librechat.ai/docs/configuration/authentication - Locator: Required two-factor authentication; Registration; User scripts - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:openid OAuth2 and OIDC. LibreChat documents OAuth2/OIDC providers including Microsoft Entra, Google, Keycloak and Auth0. - URL: https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC - Locator: Supported providers; setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:saml SAML authentication. SAML is a documented authentication option for the self-hosted application. - URL: https://www.librechat.ai/docs/configuration/authentication/SAML - Locator: Overview and requirements - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:entra Azure Entra authentication. Entra OIDC supports group-based admission and Graph integration using configured scopes and token reuse. - URL: https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC/azure - Locator: Group claims; token reuse; Microsoft Graph integration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:security T3 Chat security policy. The vendor asserts TLS, MFA support, secure sessions/access control and regular audits; no independent report or enterprise enforcement configuration is supplied. - URL: https://t3.chat/security-policy - Locator: Data protection, authentication and disclosure program - Evidence kind: vendor-claimed - Source date: 2025-02-14 - Retrieved: 2026-10-21 ### librechat:librechat:tokens Token usage. Usage and estimated costs use recorded tokens and configured provider rates; transactions are distinct from balance enforcement. - URL: https://www.librechat.ai/docs/configuration/token_usage - Locator: Context cost; transactions; per-endpoint token rates - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:logging Logging. Backend operational logs are written to customer files and can feed external tools; the guide describes 14-day rotation rather than a compliance archive. - URL: https://www.librechat.ai/docs/configuration/logging - Locator: Error/debug logs; rotation; external tools - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:privacy T3 Chat privacy policy. The policy covers user uploads, named hosting/model providers, no AI training, US/international processing and general disclosure practices. - URL: https://t3.chat/privacy-policy - Locator: Sections1-7 and11 - Evidence kind: documented - Source date: 2025-05-31 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:terms T3 Chat Terms of Service. T3 Tools Inc permits organizational acceptance but each account is personal; proprietary restrictions, cancellation/export responsibilities and California dispute terms apply. - URL: https://t3.chat/terms-of-service - Locator: Sections1-6,9,19 and21 - Evidence kind: documented - Source date: 2025-11-15 - Retrieved: 2026-10-21 ### librechat:librechat:r4-content-filter LibreChat development content-filter configuration. Opt-in base-YAML policies inspect selected message/file content; block and audit differ from limited Agent text redaction. This is development documentation, not a hosted DLP assurance. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/message_filter - Locator: Source-Aware Filters; Pattern Configuration; Redaction; File Fields - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### librechat:librechat:r4-pii-runtime LibreChat content-inspection runtime. Source-aware configured inspection executes in the LibreChat API. Missing policy disables that scope; configured actions and fields bound inspection. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/runtime.ts - Locator: createConfiguredContentInspector; source rule configuration - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/runtime.ts ### librechat:librechat:r4-patterns LibreChat pattern detector. Default starter patterns detect credential-shaped tokens/headers. Operator custom patterns use bounded regular expressions; a generic comprehensive PII classifier is not established. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/detectors/pattern.ts - Locator: STARTER_PATTERNS; configured RE2JS rules - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/detectors/pattern.ts ### librechat:librechat:r4-private-submission LibreChat private text submission. The private text ingress permits configured redaction only on eligible fresh interactive Agent text. Original content is encrypted; edit/resume/file paths do not gain blanket redaction. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/private/submission.ts - Locator: createPrivateTextIngress; fresh Agent text and clientRequestId checks - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/private/submission.ts ### librechat:librechat:r4-filter-middleware LibreChat API content-filter middleware. The server middleware applies configured inspection and rejects blocked/uninspectable requests with HTTP 400. No deployment or detection fixture was run. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/middleware/messageFilterPii.ts - Locator: createMessageFilterPii; contentFilterBlockResponse; uninspectable response - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/middleware/messageFilterPii.ts ### librechat:librechat:r4-config-1318 LibreChat config v1.3.18 changelog. Dated development config changes add limited Agent text redaction and ephemeral retention mode. These are not a promise of universal redaction or a vendor zero-retention contract. - URL: https://www.librechat.ai/changelog/config_v1.3.18 - Locator: October 22, 2026; opt-in PII redaction; retention mode - Evidence kind: documented - Source date: 2026-10-22 - Retrieved: 2026-10-26 ### librechat:librechat:interface Interface configuration. Administrators configure UI feature permissions and usage terms in the self-hosted deployment. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/interface - Locator: Feature permissions; custom welcome and terms - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:remote Remote hosting. The application can be deployed on customer-selected remote servers with operator-managed security. - URL: https://www.librechat.ai/docs/remote - Locator: Hosting options; security considerations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:demo LibreChat Demo terms. The free hosted Demo is offered as-is with possible data cleanups and no durable business-service guarantee. - URL: https://www.librechat.ai/demo/terms - Locator: Evaluation scope; retention; disclaimer - Evidence kind: documented - Source date: 2026-03-12 - Retrieved: 2026-10-21 ### librechat:librechat:settings Personal settings. Users configure interface language, audio and personal data controls. - URL: https://www.librechat.ai/docs/features/settings - Locator: Language; speech; data controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:owner ClickHouse acquisition of LibreChat. ClickHouse announced the acquisition of LibreChat and that Danny Avila and the team joined ClickHouse. - URL: https://clickhouse.com/blog/clickhouse-acquires-librechat - Locator: Announcement, November 4, 2025 - Evidence kind: documented - Source date: 2025-11-04 - Retrieved: 2026-10-21 ### librechat:librechat:siteprivacy LibreChat website privacy policy. Website, demo and self-hosted software are distinct privacy scopes; website terms do not establish a customer deployment DPA. - URL: https://www.librechat.ai/privacy - Locator: Scope and exclusions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:secrecy-message-pin LibreChat v0.8.8 message storage schema. The pinned Mongoose schema declares message text as a String and content as mixed fields; this source does not establish operator exclusion from live content. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/packages/data-schemas/src/schema/message.ts - Locator: packages/data-schemas/src/schema/message.ts, text at lines 55-58 and content at lines 139-143 - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: packages/data-schemas/src/schema/message.ts ### librechat:librechat:secrecy-demo-policy LibreChat Demo privacy policy. The Demo policy describes model-provider transmission and contractual processor instruction/security duties for the Demo; it does not cover a customer self-hosted deployment. - URL: https://www.librechat.ai/demo/privacy - Locator: Scope; section 4 Third-Party AI Model Providers; section 6 Data Sharing and Sub-Processors - Evidence kind: documented - Source date: 2026-03-12 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:overage Overage bucket refill option. The vendor says top-up refill has not been offered since the new billing model. - URL: https://feedback.t3.chat/p/overage-bucket-refill-option - Locator: Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:premier Pro and Premier pricing discussion. The vendor confirms Premier USD50/month plus tax, immediate upgrades and end-period downgrades, and customer OpenRouter keys for direct usage billing. - URL: https://feedback.t3.chat/p/new-tier-in-between-pro-and-premier - Locator: Mark Florkowski Team replies on price, OpenRouter, upgrades and downgrades - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:price-visibility Paid price visibility. Staff says billing information is needed for final tax-inclusive pricing; no checkout was completed. - URL: https://feedback.t3.chat/p/ability-to-see-paid-plan-price-without-going-into-checkout - Locator: Mark Florkowski Team replies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:byok-openai OpenAI BYOK. Staff confirms GPT5 BYOK and recommends fallback priority plus a verified OpenAI organization or removing the key; this is historical model-specific setup, not a complete current model list. - URL: https://feedback.t3.chat/p/enable-byo-api-key-for-gpt-5-and-gpt-5 - Locator: Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-vm Azure Retail Prices, Switzerland North Linux VMs. EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Virtual+Machines%27+and+%28armSkuName+eq+%27Standard_D4s_v5%27+or+armSkuName+eq+%27Standard_D8s_v5%27+or+armSkuName+eq+%27Standard_D16s_v5%27%29+and+priceType+eq+%27Consumption%27 - Locator: Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-pg Azure Retail Prices, PostgreSQL Flexible Server. EUR hourly PAYG GP compute is 0.2288, 0.4576 and 0.9152 for 2/4/8 vCore; storage is EUR 0.1325 per GB-month. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Azure+Database+for+PostgreSQL%27+and+priceType+eq+%27Consumption%27 - Locator: General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-fx ECB euro reference rate history. The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20; USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### librechat:librechat:cost-model OpenAI API pricing. Standard gpt-6-luna API price is USD 0.10 per million input tokens and USD 0.50 per million output tokens; caching, batch and regional premiums are separate. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard, short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-effort GPT-6 Luna model documentation. The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort and text-token pricing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:byok-router OpenRouter model coverage. The request is marked Completed but the staff reply says those routes do not use OpenRouter and universal rerouting requires future changes. - URL: https://feedback.t3.chat/p/let-openrouter-keys-work-with-more-models - Locator: Completed label versus Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:fx ECB reference exchange rates. EUR1 equals USD1.1215 and CHF0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time2026-10-20 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:openai-price OpenAI API pricing. The shared direct-provider proxy uses USD0.10 input/USD0.50 output per million tokens; T3 availability of this exact route is unverified. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:openai-model GPT-6 Luna documentation. The shared direct-provider proxy uses lowest effort none; this is not a verified T3 default or model-menu entry. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort options - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:export-pin LibreChat conversation export implementation. The pinned user conversation exporter supports JSON, CSV, Markdown and text, plus screenshot export. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/client/src/hooks/Conversations/useExportConversation.ts - Locator: client/src/hooks/Conversations/useExportConversation.ts, export dispatch - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: client/src/hooks/Conversations/useExportConversation.ts ### t3-chat:t3-chat:faq-support T3 Chat FAQ. The FAQ links its official feedback board and lists support email. - URL: https://t3.chat/faq - Locator: Feature requests and support - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21