Skip to main content
Integrations support generation, vacancy context, scheduling, speech input, and notifications. They do not change the Career Memory authority model: personal facts still require owner-supplied evidence, reviewed publication, and Profile-scoped access. Credentials stay server-side. They do not appear in prompts, transcripts, public responses, or visitor-visible provider details.

OpenRouter

OpenRouter provides model generation for Public Chat, Fast Check, Simulate, Properties analysis, and Derived generation.
  • Platform mode uses the hosted TLDT Lite model.
  • BYOK mode uses the OpenRouter credential and saved model list connected to the owner’s Profile.
  • BYOK does not silently fall back to platform credentials when the owner key is missing or fails.
  • Public visitors can select only models the owner marks visible.
Provider failure returns an explicit error for the action that needs generation. TLDT does not replace it with a template answer that could look grounded.

Firecrawl and Perplexity

These services support bounded vacancy extraction and public research when the workflow allows it. Research can add role or company context; it cannot prove the owner’s history. Unsafe URLs are rejected. Missing or failed research reduces available external context instead of creating a personal fact.

Cal.com

Cal.com supports an optional visible meeting flow. The conversation must have a concrete purpose, and the visitor must give explicit consent. Availability, exact slot selection, and policy review happen before booking. TLDT cannot promise that the owner is interested, available, accepting a role, or agreeing to any terms outside the visible scheduling flow.

Soniox

Soniox turns a short voice recording into editable text. The text returns to the composer and never sends automatically. TLDT does not provide a real-time interview copilot or autonomous voice representative.

Loops and Telegram

Loops supports hosted authentication email and best-effort owner audience sync. Telegram can deliver configured access-request or owner escalation notifications. These services are optional and do not grant access to Memory or secrets.
Integration settings are Profile-scoped. A missing or failed integration never permits TLDT to switch to another owner’s credential, Memory, or tenant context.