nodeslate

Getting started

API keys

Every request to the API and the MCP server carries an API key. Each key works in one place and says who did what.

Make a key

  1. Open Account settings → API keys.
  2. Name it after where it's used, such as “Claude Code (checkout repo)” or “CI”.
  3. Pick where it works: Personal, or one of your workspaces. Optionally pick the folder new diagrams go to.
  4. Choose Create key and copy it. It starts with ns_ and is shown once.

Send it

Put the key in the Authorization header of every request:

Authorization: Bearer ns_YOUR_KEY

Where a key works

  • A key reaches only the place it was made for: Personal, or one workspace. Make one key per workspace.
  • It can read diagrams its person can open there, including ones shared with them.
  • New diagrams go to the folder the request names, otherwise the key's folder, otherwise the top of the place.
  • Everything a key does shows its person's name with “via” and the key's name, for example “Dev via Claude Code”, in history, change requests and comments.
  • On a workspace that protects main, AI tools can't edit main directly: they propose changes, and people approve and merge them.

Saving links in a codebase

Each key has a setting for what create_diagram does about .nodeslate/config.json, the file that links a codebase to its diagrams: ask the person first (the default), always save the new diagram's link, or never mention it. Change it in Account settings, beside the key.

Stuck, or missing something? Contact us.