Dashboard
The home page adapts to where you are — a sample API and a getting-started checklist when you sign up, an operational view of the changes you depend on once you're connected.
The Spec0 home page at spec0.io isn't a fixed wall of widgets. It detects where your org and you are when it loads and shows one layout for that moment — an activation flow when you're new, an operational view once you're set up. You never see a blank account, and you're never shown every panel at once.
You start with something to explore
Every new organisation is created with a sample Pet Store API already in it, in a system team called Sample APIs. It's a normal API, not a screenshot — it renders in the reference viewer, has a governance result, and is queryable from an MCP-connected agent. Use it to see what the platform does before you commit your own spec.
The sample is just an API — you can delete it like any other, and it doesn't count toward your real APIs. Your own APIs come from a repo via spec0 push; there's no "upload a spec" button that bypasses Git for your own specs (the seeded sample is the one exception).
First: name your organisation
The very first time you sign in, Spec0 asks you to name your organisation before the dashboard opens — so you never land on a placeholder "My Organization". You can invite teammates in the same step (optional), then you're dropped onto the home page. New accounts get a real organisation of their own; if you were invited to an existing org, accepting the invite puts you there instead.
Getting started: the checklist
Before you've connected anything, the home page is an activation checklist. Each item is ticked from a real signal, not a box you check yourself — so it always reflects reality and disappears once you're done:
| Step | Done when |
|---|---|
| Push your first spec | Your org has a real (non-sample) API — see Getting started. |
| Connect your AI provider | You've added an AI provider key (BYOK). |
| Wire up the MCP server | Your agent has made an authenticated call — see Agents. |
| Invite teammates (optional) | Your org has invited at least one member. |
| Set an org ruleset (optional) | Your org has a Spectral ruleset. |
The primary action is Explore with a sample API; the secondary is connecting your own repo.
Connecting
Once your org has real APIs but you personally haven't connected yet, the home page becomes a single connect nudge with the exact commands to run — no JSON editing:
spec0 mcp install # wire the MCP server into your editor/agent
npm install -g @spec0/cli && spec0 auth login # install + authorise the CLIIt also shows your org's MCP server URL and prompts you to connect an AI provider if one isn't set, since AI-powered search needs a provider key. Each row collapses to a quiet ✓ as you satisfy it.
The operational view
When you're connected — MCP and CLI both active — the home page settles into a quiet operational dashboard.
Changes in APIs you depend on
The core of the page: a feed of recent changes across your org's APIs, so you catch a breaking change before it breaks a build. Each entry shows the API, the new version, a change-type badge (breaking, +N endpoints, or non-breaking), a one-line diff summary, and — for APIs your agents actually query — how many times you queried it this month. The feed is ranked by what your team owns and what you query. The same change data drives the inbox and notifications; see Versioning for how the diffs and breaking-change detection work.
Governance score
The share of your org's real APIs whose latest spec passes your org ruleset with zero errors, with a link to the ones that don't. A quality number you can watch move, not buried config.
Saved this month
A small estimate of the tokens (and the rough cost) you avoided by having your agents query specs over MCP instead of pasting full specs into prompts. It's deliberately approximate — reinforcement, not accounting — and stays quiet until there's a real number.
Org mesh
Below the fold: a link into the org mesh — which teams own which APIs, and who subscribes to them. See Teams and Subscriptions.
Where to go next
- Getting started — install the CLI, push your first spec, connect an agent.
- Agents & MCP — wire the MCP server into Cursor, Claude, or VS Code.
- AI providers — bring your own key for AI search, reviews, and changelogs.
- Events — the same change data, delivered to your inbox.