Skip to main content
Data Sources at /data-sources needs datasources:read to view and datasources:write to change anything.
Today the provider catalog behind this page is served only to the tenant admin role: a scoped engineer sees an empty table with an error until that is lifted. Ask a manager to connect providers, or use the admin role for this page.

Metric cards and status tabs

Total Sources, the connected count, Issues (degraded plus error) and Cost Today sit on top; the first three filter the table. Tabs: All, Connected, Degraded, Error.

Add a provider

1

Click Add Source

Add Data Provider opens.
2

Select Provider

Providers are grouped by category: identity verification, blockchain analytics, and the built-in Frayme mock used for testing.
3

Choose credentials

Leave Use own credentials off to use the platform’s credentials where Frayme resells the provider. Turn it on to enter your own; the fields are the provider’s, for Sumsub App Token, Secret Key and Webhook Secret.
4

Add Provider

The provider appears in the table and in the Integration node’s provider list.

Provider settings

The gear opens the provider’s settings dialog (titled with the provider name): status, Provider enabled, credential fields (Leave blank to keep existing credentials), read-only metrics and Remove data source.

Disable or remove

The Enabled switch in the table asks Deactivate …? with the provider’s name: flows that use it stop enriching until it is enabled again; existing case results are unaffected. Remove data source deactivates the provider for the tenant permanently.

Available providers

Sumsub (identity verification), Chainalysis (blockchain analytics), BigDataCorp and BigDataCorp Companies (identity and registry data, provisioned automatically), and the Frayme mock provider for testing flows without vendor calls.

Not yet real

Not available today. appears in the interface but does nothing yet. The guides only document controls that work; this note marks the gap so you do not wait on it.
Per-dataset configuration (which product, which inputs) lives on the Integration node, not on this page.