AgentsReady
Verified deep dive · SaaS

Linear

Run the agent liveReport a change
4 minTime to key
NoNo-human path
1Human gates
9/10Onboarding score
Email verification

Fastest path to a key

  1. Email verification
    Sign up at linear.app with Google OAuth (or email magic link/code)
  2. Create workspace (name + URL slug) during onboarding
  3. Settings > Account > Security & access > Personal API keys > New key (optionally read-only / team-scoped)
  4. Call https://api.linear.app/graphql with header 'Authorization: <API_KEY>'
  5. Working API key

Biggest gap

No official CLI with device login and no llms-full.txt; API key creation still requires clicking through the web settings UI.

Worth copying

MCP accepts the same personal API key as a bearer header (plus a dedicated /mcp/readonly endpoint), so headless agents never need a browser OAuth dance.

Sources (6) · checked 2026-10-11
77Readiness score / 100
L3 Agent-operableBeats 93% of 1,846 companies
Access20/20
Context17/20
Interfaces24/32
Onboarding14/19
Trust2/9
llms.txt · root
MCP · https://mcp.linear.app/mcp

Biggest gains

  1. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
  2. +5 Self-serve API keys. Show how to create a key on the first docs page. No sales call.
  3. +4 Agent manifests. Publish an MCP server card (/.well-known/mcp.json) or A2A agent card.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 6 changes, up to +23 points

Each change is ready to paste, filled in for linear.app, with a command to check it worked. Or hand the whole list to your coding agent.

An OpenAPI spec is the contract agents and SDK generators build against. Without it they guess from prose.

Where: https://linear.app/openapi.json, linked from llms.txt and the API reference
// Serve the spec your API framework already generates (FastAPI: /openapi.json is built in).
// Next.js: app/openapi.json/route.ts
import spec from "@/openapi/openapi.json";
export const GET = () => Response.json(spec, { headers: { "Access-Control-Allow-Origin": "*" } });

// Every operation needs: operationId, summary, description, request/response examples,
// and the auth scheme (components.securitySchemes) so agents know how to send the key.
Check it worked:curl -s https://linear.app/openapi.json | head -c 200

Add the badge to your README

AgentsReady badge for linear.app
[![AgentsReady](https://agentsready.dev/badge/linear.app)](https://agentsready.dev/c/linear.app)