Connected apps and API keys

Connected apps

Every app you connect through the sign-in page is listed on your dashboard with its name, where it sent you back, when it was last used, and what it may use: your Omni memory (Personal) or not, and all spaces or the ones you chose.

• What a connection can see: the spaces you chose at sign-in, plus the Inbox. Choosing all workspaces includes spaces you make later. A space the app itself creates is added to its list.
• Disconnect: select Revoke next to the app. Its access ends at once, and it has to sign in again to get it back. If you signed the same app in on two computers, each sign-in is listed and revoked separately.
• Change what an app sees: disconnect it, then connect again and choose differently.

An app can only ever reach your own spaces. A space_id that belongs to someone else, or that the connection wasn't given, is answered as space_not_found, exactly as if it didn't exist.

API keys

For scripts, curl, or MCP clients without OAuth sign-in, make an API key on the dashboard under Advanced → API keys → Create key.

• A key looks like omni_dev_…. It's shown once, when you make it, and Omni stores only a hash of it. Copy it straight away.
• A key can use all your spaces, including Personal.
• Send it as a bearer token to the same address:

curl -sS https://agent.omnistatic.com/mcp \
  -H "Authorization: Bearer $OMNI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_spaces","arguments":{}}}'

• Revoke a key on the dashboard when you no longer need it, or if it may have leaked. It stops working at once.

Treat a key like a password: keep it out of source control and chat messages.

Activity

Each space's page on the dashboard shows what your AI apps did there, such as "Claude saved a memory". The activity log records which tool ran and when, never what was in it.