The console is where you see and manage everything without writing code: your spaces, new scans, the assistants you connected, API keys, billing, webhooks and the audit log.
Sign in
Choose Continue with Apple, Continue with Google, Continue with GitHub, or enter your email and the one-time code we send you (valid for 10 minutes).
It is the same account as the Space Context iPhone app, whichever way you signed up there: the console finds it by the email of your Apple, Google or GitHub account (for GitHub, its primary verified email). If you used Apple’s Hide My Email in the app, sign in here with Apple too: you reach the same account.
Approve a sign-in from the terminal
spacecontext login shows a code and sends you to Approve a sign-in in the console. Type the code, read what is asking (the name a terminal gives is what it said about itself), choose what the key may do and its mode, and approve: the terminal receives a key of its own, listed under API keys as CLI · …, revocable at any time. A live key that can scan (scans:write) needs a card on file: without one the console tells you so instead of approving. Add one under Billing → Add a card (nothing is charged) and approve again, or approve the key without scans:write. Approve only a code you are looking at in your own terminal; a code never travels in a link.
What the console shows
| Section | What you can do |
|---|---|
| Overview | Spaces, documented items, scans and questions this month, balance; 30-day charts of scans, API requests, questions and spend; usage per key; the latest scans, updated live. A short Get started checklist takes a new account from the demo (free) to a card on file (nothing charged) to its first live scan (free, one free scan per card). |
| Spaces | Every space you can read, and a search across all of them. Open one for its summary, issues, key locations, how-tos and facts, the inventory by area with the original photos, questions answered with sources, the scan history with before/after comparisons, and exports (Agent Skill, JSON). |
| New scan | Drop a walkthrough video or photos, see the price (the account’s free scan, if it has one, or $1.00), follow the analysis step by step, and land on the result. |
| Connect AI | The MCP server URL and the steps for Claude, Claude Code, ChatGPT and Cursor, with the assistants already connected. |
| API keys | Create test and live keys with scopes and a monthly spending cap (a live key that can scan needs a card on file); revoke them. Keys created by the MCP connector carry an MCP badge; keys approved for a terminal are named CLI · …. |
| Billing | Balance, the card on file (added without a charge), top-ups by card through Stripe, invoice details (individual or company, VAT number), automatic top-up, spend chart, every movement, and invoices. |
| Webhooks | HTTPS endpoints, events, test deliveries, delivery history. |
| Security | The audit log: sign-ins, keys, webhooks, payments and deletions, with who did them, kept 400 days. |
The Live / Test switch at the top changes what the spaces, scans and overview show: Test is the demo space and free, instant scans that return demo content; Live is your real spaces. Nothing in Test mode is ever charged.
Sessions
- A console session lasts up to 30 days and lives only in the browser tab (not in cookies, not on disk). Closing the tab ends it.
- Sign out revokes the session on the server, and is recorded in the audit log.
- In the console you act as the owner of the account, with every permission. A console session cannot be used on the app’s API, and an API key cannot open the console: keys cannot create keys, see billing or change webhooks.
Limits on codes
To protect your account, emailed codes are rate-limited per address and per network. If you request many codes in a short time you are asked to wait a few minutes. A wrong code can be retried a few times before a new one is needed.