Skip to content

Managing access & security

This page covers how to see what’s connected, how to cut access off, and the security guarantees behind AI / Agent access.

The API & agent access page (under Settings) has two lists:

  • Active keys — every API key (asmk_…) used by desktop and CLI clients and your own scripts, with its label, scope, who created it, and when.
  • Connected apps — every web-chat connection (claude.ai / ChatGPT), with the app name, who granted it, when, and the scope.

Both lists have a trash icon on each row.

  • Revoke a key — the key stops working on its next request. The row is shown struck through and marked revoked.
  • Revoke a connected app — the connection is torn down immediately; the app can no longer read or change your data and cannot silently reconnect.

Revoke access whenever a device is lost, a teammate leaves, or you simply no longer use a connection.

Check the response before replacing a key or reconnecting a chat app:

  • Assemblified returns 401 with a JSON unauthorized message: check the server URL, bearer-token configuration and whether the key was revoked. Create a replacement only if the key is unusable or lost.
  • A web-chat client first receives 401 asking it to discover sign-in information: this can be a normal connection step. It does not by itself mean an existing connection expired. Follow the client’s sign-in recovery only when it identifies an actual authorization problem.
  • The response explicitly says the connection was blocked before sign-in: contact support with the short error and support reference. Replacing credentials does not address that refusal.
  • You see 403, an HTML error page, or an unclear refusal: the cause is still unknown. These alone do not prove the key is wrong or the chat connection needs renewing.
  • An MCP tool returns a permission, subscription or retry error: follow that error’s instructions. A connection failure never grants extra access or makes it safe to repeat an uncertain change.
  • The client reports a timeout, DNS or TLS error without an HTTP response: check connectivity and the configured URL; this does not establish a credential problem.

For a custom client that supports a user-agent setting, you may compare an honest application-name/version value under the same access rules. Do not impersonate a browser or assume this will resolve a refusal.

For support, collect the time and timezone, client and version, server path without query parameters, HTTP status, response type, a short sanitized error and any support reference. Include the actual user-agent if available; otherwise say it is unknown. Never share keys, tokens, connection codes, cookies, authorization headers or full request/response dumps.

AI / Agent access is built to be safe to hand to an outside assistant:

  • Read-only by default. A connection can only change data if you explicitly granted it read & write scope — chosen when you create an API key or generate a web-chat connection code. Write access covers exactly the surfaces described in Operating BOMs & subassemblies and Operating materials & stock; read-only connections can’t see or use any of it.
  • Scoped to one store. Every key and connection is pinned to your single store. An assistant can never reach another merchant’s data.
  • Keys shown once. The plaintext key is displayed only at creation and never stored, so it can’t leak from Assemblified later.
  • Sandboxed execution. When your assistant runs a program (run), it executes in an isolated sandbox with no access to anything beyond the data described in What the assistant can read. It can’t reach the internet, your secrets, or the wider system.
  • Revocable. Any key or connection can be cut off at any time, and revocation takes effect on the next request.
  • Removed on uninstall. If you uninstall Assemblified, every key and connection is invalidated along with it.

AI / Agent access requires an active Assemblified subscription. It’s currently in open beta, and access may move to the Enhanced plan in the future. Open Settings → API & agent access to create API keys, generate web-chat connection codes, and revoke them at any time.