Skip to content
Merulan

Fiber setup

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

Connecting Fiber opens a Nango Connect session in the operator browser. Nango holds the credential, and Merulan holds a handle to it. An operator who holds the material below connects in one pass.

Prerequisites

Fiber refuses the connection until every item holds.

  • A Fiber account with search and enrichment entitlements.
  • A Fiber key issued for the Fiber account rather than for one person.

Credentials

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

  • One Fiber API key, held per workspace and sealed on save.

Scopes

Fiber requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • search
  • enrich

Fiber grants reach through the key entitlement. The names above are the operations the adapter exercises.

Verification

Workspace-issued credential governs the Fiber connection. Fiber issues the key to 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.