Refresh job
the data behind every page.

01Why it runs on GitHub

• Kalshi refuses browser requests. Any request with an Origin header gets HTTP 403, so the fetch must happen server-side.
• Your network may block a venue. Some internet providers block Polymarket's domains. GitHub's runners are not behind your provider. Do not try to get around a block on your own network.
• Nothing to host. No server, no database, no keys.

02Run it by hand

The workflow ships with the schedule off; only a manual start (workflow_dispatch) runs it. Not tested here

1. Open ActionsOn your repository on GitHub, click Actions. Enable workflows if GitHub asks.
2. Pick "refresh board"In the list on the left.
3. Run workflowKeep the branch main and confirm.
4. Pull the resultWhen the run is green, run git pull. The commit is titled board: refresh YYYY-MM-DDTHH:MMZ and authored by mikodes-bot (the name is set in the workflow; change it if you like). On Vercel's Hobby plan such a commit is not deployed on its own; see Deployment.

The job pushes a commit, so the workflow declares permissions: contents: write. If the last step fails with a 403 on git push, check Settings → Actions → General → Workflow permissions.

03What each step does

04Use your own Polygon RPC

The Terminal tape is read from Polygon. Out of the box the job uses three public, keyless RPCs and falls through them in order. They are enough for a 40-block window; a paid or private endpoint gives you higher rate limits and one provider you chose.

1. Get an endpointAn HTTPS Polygon mainnet (chain 137) URL from any RPC provider. It must allow eth_getLogs over at least 40 blocks.
2. Add the secretIn your GitHub repository open Settings → Secrets and variables → Actions and add a repository secret named POLYGON_RPC_URL with the full URL. Several URLs may be given, separated by commas.
3. Run the workflowThe tape step passes the secret to node src/onchain.js.

• Your endpoint is tried first; the public RPCs stay as the fallback. Set POLYGON_RPC_ONLY=1 as well to use only yours.
• The URL is never written anywhere. Many providers put the key in the URL, so tape.json and the Terminal footer name it only as own RPC (POLYGON_RPC_URL), and error messages carry that label instead of the URL.
• A value that is not an https:// URL stops the job with an error that does not print the value.
• The Polygon RPC URL in the admin's Integrations is separate: it feeds the admin's Status check only. Use the same URL in both places if you like.

Tested offline with node --test test/rpc.test.js in terminal/ (6 cases, a local stand-in RPC). Not tested here A GitHub Actions run with a real secret.

05Turn on the schedule

Edit .github/workflows/refresh.yml and remove the # in front of the two schedule lines, so the on: block reads:

on:
  schedule:
    - cron: '*/15 * * * *'
  workflow_dispatch:

Commit and push. GitHub may delay scheduled runs at busy times and pauses schedules in repositories with no activity for a long time; re-enable them in the Actions tab.

06What it costs in Actions minutes

Recent runs on the project's own repository took 2 min 33 s to 3 min 51 s. GitHub bills each job rounded up to the whole minute. At 3 billed minutes per run:

The comment in the workflow gives the same figure (2,880 runs, about 8,640 billed minutes a month at every 15 minutes). Check the free allowance and overage price for your own GitHub plan on GitHub's billing page before you turn the schedule on.

07Running the jobs locally

cd terminal
node src/onchain.js 40     # Polygon only; argument = blocks to read
POLYGON_RPC_URL=https://your-endpoint node src/onchain.js 40   # with your own RPC

cd scanner
node src/run.js            # options: --contracts 1000 --max-events 1200 --no-depth --out public/board.json
cd ../terminal
node src/titles.js         # needs Polymarket's Gamma API