| Jenkins | calls the classic remote API directly (buildWithParameters + polling queue / build + consoleText), Basic Auth (credentials matched by the job URL's host) | "which jobs belong to which system" still comes from momo-ticket-system; the run itself bypasses it entirely |
| RCM Config Server | calls the KrakenD gateway directly with X-Api-Key; in production TP / GCP share one gateway and TC has its own; the production TC path prefix contains /tc/, unlike the test machine | see README_APIKEY_PROD.md; the Deploy toggle (enable) cannot be controlled through the API (known limitation in §2.4) |
| GitLab | REST API v4, PRIVATE-TOKEN; several instances can be configured | also the data source of cogwork's update notice |
| Jira / Atlassian | Atlassian Cloud OAuth | read-only queries; the write action actually creates GitLab issues and never writes back to Jira |
| Outlook / local files | Windows local COM / MAPI, file-system API | entirely on the user's own computer, no server involved |