The credential host pointers correspond to configured AI provider routes, not automatic forwarding to unrelated collectors. The mirror has a default vendor gateway, but syncing requires deployment-provided wiring including a per-account key and console token.
Static reason
No blocking static signals were detected.
Trigger
The mirror service is considered at harness startup; it remains inactive until its required deployment wiring is present. Provider keys are used for provider routes.
Impact
No evidence shows credentials being sent to unrelated hosts or collected for unrelated use.
Mechanism
Provider credentials are referenced by their provider-specific environment variable. The mirror requires a URL, owner, console token and per-account mirror key to sync.
Network endpoints7
api.openai.comapi.anthropic.comapi.deepseek.comapi.kimi.comapi.moonshot.aigenerativelanguage.googleapis.comharness.mwt.one