Suppliers

Open Connections → Suppliers. Every member sees each supplier’s usage; only an organisation owner sees and changes its connections.

Usage

An owner sees every supplier the organisation has a connection for and every supplier named on its edges’ events, so a supplier an edge calls with its own local key appears too. A member sees the suppliers named on events plus the connections authorised to their own edges. Choose a Window and select Show.

The page shows at most 20 suppliers: connected suppliers first, then the most recently seen, and it says when others are left out. A supplier name is 1–64 lower-case letters, digits, dots, underscores or hyphens, starting with a letter or digit; the page counts the names on your events that are not valid and does not list them. If one supplier’s usage cannot be loaded, its entry says so and the rest of the page still loads.

For each supplier the page shows the retrieved and grounded counts, the number of sessions, and per host the counts and the last event. It counts only the events that supplier served: an event carries the supplier’s name in its commonmeasure-supplier field, and a direct fetch of a host the supplier also serves is not counted.

Download JSON saves the API’s answer unchanged. It contains no session identifier and no engagement. It lists the enrolled edge key ids whose sessions the events came from. Give this file to the supplier under your agreement; the hub sends nothing to a supplier.

Older events are kept as daily totals once the retention period passes. Where a window starts or ends inside such a day, the window is widened to whole UTC days and the page says so.

Supplier usage API

GET /api/v1/suppliers lists the suppliers named on your organisation’s events, with each one’s last_event_at: the 100 most recently seen, most recent first. omitted counts the valid names beyond those 100 and invalid the names that are not valid supplier names, which are not listed. The usage route refuses a name that is not valid with 400.

GET /api/v1/suppliers/{supplier}/usage answers with supplier, supplier_field, since, until, window (since, until, snapped), content_retrieved, content_grounded, sessions, agent_ids and hosts, each host with its content_retrieved, content_grounded, first_event_at and last_event_at. since and until are optional RFC 3339 times; until is exclusive. Both routes need a signed-in member or a telemetry:read key.

curl -H "X-API-Key: $KEY" \
  "https://hub.commonmeasure.ai/api/v1/suppliers/ozone/usage?since=2026-09-01T00:00:00Z"

Connections

An organisation owner connects a supplier account under Connections on the same page. The suppliers offered are the ones the edge can call: Dataville, Exa, Firecrawl, Keenable, Linkup, Nimble, Ozone Live, Parallel, People Inc, Redpine, Search1API, SERPdive, Tavily, TinyFish, TollBit, Valyu and You.com. Open Connect supplier, check the organisation name, choose the supplier, give the connection a label, enter its API key and select Save connection. The key is stored encrypted and cannot be revealed on the page. Saving it does not test the supplier account or establish permission to use a source. Supplier charges remain on that account.

Expand a saved connection to manage it. Choose the hosted edge you operate and select Authorise edge. Only a hosted edge with supplier custody turned on fetches Hub-held keys. A local edge uses its own credentials (credentials.env) and does not fetch them. The Hub cannot tell which enrolled edges are hosted, so the list names every enrolled edge. Authorising an edge lets whoever runs it obtain the supplier key; authorise only edges you operate.

Each authorised edge shows one of three states. Never fetched, with No effect on a local edge: the edge has never fetched a release. Not fetched since authorised, also with No effect on a local edge: the edge has fetched before, but not since this authorisation, so this key has not reached it yet. An edge that now runs locally, or has custody off, stays in this state. Last credential check: when the edge last fetched a release, which includes this key. It does not establish that a supplier call succeeded. A hosted edge with custody on normally fetches every five minutes, so a new authorisation normally reaches it within five minutes. The authorisation stays until you remove it. Remove edge access withdraws one edge’s access. Revoking its ingest key alone does not remove supplier access. Revoke connection, followed by confirmation, removes all authorisations and deletes the stored key. Removal takes effect at a reachable edge on refresh; if it cannot reach the Hub, its configured expiry bound applies.

Replace API key stores a new value for the same connection and keeps its authorised edges. Neither replacement nor revocation here invalidates the old key at the supplier. Rotate or revoke it in the supplier account as well. The page permits changes only in your own session; exit impersonation first.

Each connection says how its costs are known. Some suppliers report the charge on each response; for others the cost is quoted from their published price. Keenable, Ozone Live, People Inc and TollBit report no charge and publish no price the edge can quote, so their cost remains unknown, which is not the same as free. Connecting an account does not establish a source licence or relax the Edge source policy. Confirm your permitted use with the supplier before admitting licensed content.