Skip to content
Merulan

Ghostbuster setup

What an operator supplies to connect the Ghostbuster Source, and the verification the provider requires.

Connecting Ghostbuster accepts a provider API key the operator pastes once. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Ghostbuster refuses the connection until every item holds.

  • A Ghostbuster account that holds its own API key, because Merulan keeps no platform key and no environment fallback.
  • Ghostbuster credits for the lookups a Product runs, which the Ghostbuster account pays and Merulan does not.

Credentials

Ghostbuster stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • One Ghostbuster API key, pasted once and sealed on save. Ghostbuster documents no credit-free key check, so connect checks the shape of the key and a refused key surfaces on the first lookup.

Scopes

Ghostbuster carries no scope list in Merulan: the Ghostbuster key itself holds the requested scopes for this Source.

A Ghostbuster key carries no scope list that Merulan reads. The adapter exercises the people lookup operation, so narrow the account rather than the key.

Verification

Workspace-issued credential governs the Ghostbuster connection. Ghostbuster issues the key inside the customer account, so no application review stands between the key and production data.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.