API keys & access

Scoped keys for developer tools.

Most supported assistants, including Claude Code, don't need a key at all — the two-minute connection handles browser sign-in. Keys are for headless jobs and clients that do not support OAuth, where you choose exactly what each key is allowed to do.

Create a key #

Sign in and go to Settings → Connections → API keys. Every key starts with smb_live_ and is shown once, at creation — copy it then, because it can't be displayed again. If you lose one, revoke it and create a new one.

Choose what a key can do #

When you create a key you choose what it can do: read-only or read-and-write. Only what you grant is available to that key — a read-only key simply has no way to change anything. Grant the least you need: reading is enough for research and reporting, and you can always create a second, more capable key for a specific job. (The browser connection at claude.ai works the same way: when you connect, you make the same choice.) No key or connection can delete records — removing something stays in the app, where you do it yourself.

Use a key #

Point your tool at the connection address below and send the key as a bearer token (an Authorization: Bearer smb_live_... header). The Connections page in the app has copy-paste setup instructions for common tools.

https://app.solosearcher.com/mcp

Revoke anytime, audited always #

Revoking a key under Active keys ends its access immediately. And every request made with any key or connection is written to your audit trail — which tool ran, when, and whether it succeeded — never the data itself. Anything that changes is traceable back to the request that changed it.