GitHub through Squiid

What GitHub is

GitHub is where agent-written code lives. The REST and GraphQL APIs cover repositories, branches, commits, pull requests with reviews and comments, issues and projects, releases, and Actions workflow runs with their logs and artifacts. Most coding agents use it constantly: opening a pull request for a change, reading a failing CI run, commenting on a review thread, or checking what changed since they last looked. GitHub Apps with per-repository installation are the better-scoped alternative to a user token, and they are what a connection models.

The credential problem here is subtle. A classic personal access token with repo scope reaches every repository you can see, including private ones belonging to other organisations you are a member of. Agents ask for one routinely, and once it is in a shell profile or an MCP config it stays there, unaudited, until it leaks or someone rotates it by accident and breaks three tools. Fine-grained tokens help, but they expire, and rotating them across several tools is the kind of chore that gets skipped.

Why connect it through Squiid

GitHub is a connect service on Squiid. You link your existing GitHub account or organisation through an OAuth-style connection, and Squiid holds it and issues scoped access through https://api.squiid.io/v1/github/... with Authorization: Bearer $SQUIID_API_KEY, with Octokit and other clients working by base URL swap (gateway convention). Your GitHub plan is billed by GitHub directly at the provider's listed price, since Squiid does not resell seats, and you can revoke the connection in one click if a machine goes missing. Actions workflows can also call the gateway, which keeps CI from carrying a second long-lived credential.

• One account, one key, one bill, one dashboard. GitHub sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the GitHub credentials. Your code carries SQUIID_API_KEY, so GITHUB_TOKEN, GH_TOKEN, GITHUB_APP_ID, GITHUB_PRIVATE_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what GitHub costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Your existing GitHub account connected, not replaced
• Repository, pull request, issue and Actions access
• Scoped access instead of a broad personal access token
• One-click revocation across every agent at once
• GitHub seats stay billed by GitHub

How to connect GitHub

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces GITHUB_TOKEN, GH_TOKEN, GITHUB_APP_ID, GITHUB_PRIVATE_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/github/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

GitHub bills your plan and Actions usage directly at the provider's listed price, with no Squiid margin. Squiid passes that through at par: one dollar of prepaid credit is one dollar of GitHub usage, with no markup and no per-request margin.

GitHub has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so GitHub usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Your own account: the GitHub account was always yours and Squiid only holds an authorised connection, so revoking it leaves nothing behind. Squiid never owns your code, your schema or your domain, and the gateway speaks GitHub's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

GitHub through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on GitHub usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.