Linear through Squiid

What Linear is

Linear is issue tracking built for speed, with a GraphQL API that covers issues, projects, cycles, labels, comments and workflow states. Its API is complete enough that most of what the interface does can be done programmatically, and webhooks report changes so an application can react when an issue moves to done or a new bug is filed. Attachments link external resources such as a pull request or a Sentry issue directly to the ticket they relate to. Sub-issues, estimates and triage queues are part of the model, so a generated issue can carry the structure a human would have given it.

In agentic coding workflows Linear is often the queue. An agent reads the next issue, implements it, opens a pull request, and moves the issue along, or a bug report from a support conversation becomes an issue automatically with the context attached. Because the API is fast and well typed, generated code against it tends to work rather than approximate. Linear's API also enforces a clear permission model per workspace, so a connection cannot reach teams it was not granted.

Why connect it through Squiid

Linear is on the Squiid roadmap as a connect service. When it lands, you will link the workspace you already have through an OAuth-style connection, and Squiid will hold it and issue scoped access through https://api.squiid.io/v1/linear/... with Authorization: Bearer $SQUIID_API_KEY, with the SDK working by base URL swap (gateway convention). Your Linear plan stays billed by Linear directly at the provider's listed price, and the connection is revocable in one click. Status transitions are explicit in the API, which makes an automated workflow easy to audit afterwards.

• One account, one key, one bill, one dashboard. Linear sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Linear credentials. Your code carries SQUIID_API_KEY, so LINEAR_API_KEY, LINEAR_TEAM_ID 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 Linear 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 Linear workspace connected, not replaced
• Issue, project and cycle access over GraphQL
• Webhooks for issue and status changes
• Scoped, revocable access for agents
• Linear seats stay billed by Linear

How to connect Linear

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 LINEAR_API_KEY, LINEAR_TEAM_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Linear bills your workspace plan 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 Linear usage, with no markup and no per-request margin.

Linear 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 Linear 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 Linear 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 Linear'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

Linear 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 Linear 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.