Skip to main content
The Reporting API gives Edge Providers server-to-server access to the same numbers the Edge Operator Portal shows: requests and tokens served, devices registered, and estimated earnings for each app, overall, per device, or per end user.
Every endpoint is a GET scoped to one of your apps. The endpoints come in two groups, the same as the Try it panel on the portal’s Reporting page:

Create a reporting API key

1

Open the Reporting page

Sign in to the Edge Operator Portal and select Reporting in the sidebar. Only account owners and admins see this page.
2

Create a key

Select Create key and give it a name, for example Nightly earnings export. A key gives access to usage and earnings for every app on the account. An account can hold up to 10 keys, so each server or integration can have its own.
3

Copy it straight away

The full key (zgsk_…) is shown once. Copy it, or confirm you’ve stored it somewhere safe, before you can close the dialog. After that the portal shows only its last four characters. If you lose a key, revoke it and create a new one.
A reporting key reads your earnings. Keep it on your server, in an environment variable or secret manager, and never ship it in an app, extension, or web page. Revoking a key on the Reporting page makes requests with it fail with 401 immediately.
The reporting key (zgsk_…) is for this API only. It is different from your app’s SDK key (zgpu-sdk-…), which lets devices join the network, and from the API key (zgpu-api-…) used to call the ZeroGPU inference API.

Authentication

Send the key as a bearer token:

Common parameters

With no window, totals cover all retained history (about 3 months).

Edge operator

Totals for an app, and the same usage broken down by device.

App totals

GET /app/edge-operator returns an app’s requests, input and output tokens, registered devices, and estimated earnings for the window.
Response

Usage per device

GET /app/devices returns requests and input and output tokens for each device, highest usage first.
Response
Usage that carried no device ID is reported as a single row with deviceId: null, so with no cust_param the rows always add up to the app totals. With a cust_param, only devices that served matching usage are listed.
New traffic reorders devices between requests. To walk every device exactly once, pass a from/to window that has already ended.

By custom param

Your app can tag the work its devices serve with up to three custom params (cust_param1–cust_param3) through the SDK, for example your own user ID or a campaign tag. Use them to split requests and earnings by those values.

Earnings per custom param

GET /app/earnings returns requests, tokens, and earnings for usage that carried the custom param values you pass.
Response
  • Each cust_param is an exact match on the value recorded when the request ran. Pass several to narrow further: usage must match all of them.
  • A filter value must be 1–128 characters of A-Z a-z 0-9 . _ -. Anything else answers 400.
  • The Web and Android SDKs strip control characters and surrounding whitespace from a value before recording it, and truncate a value longer than 128 characters to its first 128. If your app sets longer values, filter with the truncated value.
  • With no cust_param, the totals equal /app/edge-operator for the same window.
  • Changing a device’s macros later never moves earnings already recorded under the old value.

Errors

All figures are estimates, matching what the portal shows. Narrow filters, such as a single end user, cover fewer events and are less precise than app totals.