/data-sources (admin-only) is the operational surface for every external provider.
Metric cards
The four cards across the top are clickable filters into the table:| Card | Action |
|---|---|
| Total Sources | Filters to All. |
| Connected | Filters to providers with status: connected. |
| Issues | Filters to degraded + disconnected. |
| Cost Today | Read-only — sum of requestsToday * costPerRequest across enabled providers. Also surfaces avg latency. |
The integration table
Columns:- Priority — drag-handle + up/down buttons. Lower number is queried first when multiple providers cover the same signal.
- Provider — name + category.
- Status —
connected/degraded/disconnected(driven by the last health probe). - Response Time — last health probe.
- Requests today — counter from the audit log.
- Cost / req — set at provider creation, used by the cost-today card.
- Success Rate — last 24h, colour-banded.
- Enabled — switch. Disabled providers are skipped by workflows.
- Actions —
Test connectionandSettings.
Adding a provider
Pick from catalogue or go custom
The dropdown groups providers by category. Select + Custom Provider if your vendor isn’t listed.
Inspect the preview card
Shows region tags, features, website and average cost from the catalogue entry.
Resold? Skip credentials.
If
resold: true, the dialog shows the reselling notice and no API key field. Frayme manages the credential.Otherwise, fill API key + endpoint + cost
Standard form. The endpoint placeholder pre-fills from the catalogue website.
Provider settings
Open the gear icon in the Actions column. Resold and BYO providers show different fields:- Resold (Sumsub, LSEG, BigDataCorp, Crystal)
- BYO (ThreatMetrix, Plaid, Jumio, …)
- Status row (latency, uptime, last sync).
- Reselling notice explaining that credentials and billing are Frayme-managed.
- Enable / disable toggle.
- Read-only metrics.
- No endpoint, no API key, no cost fields.
Test connection
TheTest connection button (lightning icon in the Actions column or inside the Settings dialog) performs a synthetic round-trip against the configured endpoint. Used after rotating credentials or after the provider reports a health change.