user…

Your dashboard.

Your API key, your GitHub token, custom tracks and real-time usage metrics. Everything you ask the API runs on your own GitHub token with stable rate limits.

API usage

GitHub Rate Limit Quota checking
reset in …
5,000 / 5,000 requests left Resource: core · Resets at …
0Today
0Last 7 days
0Last 30 days
0All time

0%Succeeded
0 msAverage time
0 msMedian
0 ms95% faster than
0 msSlowest

Requests per day requests errors

Today

Where calls come from

    Time of day your local time

    0:0012:0023:00

    Most used endpoints

    EndpointCallsErrorsAvgp95

    Status codes

    Recent requests

    Download .csv
    TimeFromRequestStatusTime taken

    No requests yet. Call the API with your key and they show up here.

    GitHub token checking

    The API reads GitHub with your token, under your own 5,000 requests an hour. Public repositories need no permissions; add Contents: Read-only to see private ones.

    Tracked repositories & Custom tracks

    Track repositories on distinct tracks (prod, staging, tools) to automate releases, filter CI checks, and run multi-environment updates in one click.

    Active Track: All

    Nothing tracked yet.

    Scripts can do the same: PUT /api/v1/watchlist syncs a whole list, GET /api/v1/watchlist/check returns a 0/1 exit code for CI gating. See the automation guide.

    Automation & CI/CD Hub

    Production Ready

    Automate version gating and release detection in your pipelines. Select your language to view ready-to-run integration code:

    curl -H "Authorization: Bearer YOUR_KEY" "http://localhost:8000/api/v1/watchlist/check"

    API key

    ••••••••••••••••••••••••

    curl -H "Authorization: Bearer YOUR_KEY" "http://localhost:8000/api/v1/usage"

    Automation keys

    0

    One key per script, CI job or integration. Each has a name, shows up by name in your usage charts and can be rotated or deleted on its own. Read looks things up (and batch-checks); Craft data may only read /api/v1/craft/; Full also changes your tracked repositories. Give a key an expiry and a daily cap so a leaked or runaway job stays small. All keys share your account limits and your GitHub token.

    No automation keys yet. Your main key above keeps working.

    Change your password, sign out everywhere or delete your account in Settings.

    Loading your dashboard…