Agent Native CRM

Showing 25 of 109 from the live probe.

• Health

  Liveness probe

• Create Workspace

  Create a workspace and become its owner Two ways in, told apart by the credential you send. With no Authorization header, send `owner` and a new principal is created to own the workspace: the bootstrap, for a caller who has no key yet. With your existing key or session, omit `owner` and you become the owner of another workspace under the identity you already have -- an `owner` block there is refused rather than believed. Either way you get the workspace, your principal, and a new key bound to t

• Get Me

  Who you are and which workspace you are in

• Get Usage

  Record and activity counts against the plan's caps

• Get Workspace

  The current workspace

• Update Workspace

  Rename the workspace or change its slug

• List Principals

  Everyone who can act in this workspace Agents carry their `profile` -- what they are for and the capability keys they declare -- or `null` when nobody has described them yet. Humans have no `profile` field at all.

• Create Principal

  Add a human or an agent Agents authenticate only by API key and cannot have a password. Humans may be given one so they can sign in to the dashboard. Adding somebody sends them nothing; mail an invitation with `POST /principals/{id}/invite`. Email is the natural key, so this upserts -- an account that already exists joins this workspace at the role you asked for and comes back 200 with created: false, needing no claim link. Send `profile` for an agent to describe it in the same call; it needs a

• Get Principal

  Fetch one principal An agent comes back with its `profile`; a human has no such field.

• Get Agent Profile

  What one agent says it is for The structured profile: display name, one-sentence description, declared capability keys, the scope it works to and the limits at which it hands back. `404` when the principal is not in this workspace, `409` when it is a human, and `null` when it is an agent nobody has described yet.

• Set Agent Profile

  Describe an agent, or replace its description Owners and admins may describe any agent; an agent may always describe itself, because the thing that knows what it can now do is the thing whose tools changed. A description and at least one capability are required. Capability keys are normalised to lowercase dotted segments -- `Lead Qualify`, `lead-qualify` and `lead.qualify` are one key, not three -- and any key the workspace has not seen joins its vocabulary with the label you sent. The list you

• Update Agent Profile

  Change part of an agent's profile Leaves out what you do not send. `capabilities` is still replaced wholesale when present, because a partial capability list has no meaning. Refused with `404` for an agent that has no profile yet -- `PUT` one first.

• Update Principal

  Rename, re-role or archive a principal

• List Keys

  A principal's keys, without the secrets

• Issue Key

  Issue an API key The key is shown once, here. Only a salted hash is stored.

• Revoke Key

  Revoke a key

• Remove Principal

  Remove a principal from this workspace Takes them off the roster and deletes the keys this workspace issued them. The person is not deleted and everything they wrote stays attributed to them -- archive instead when the work should stand but the access should not. The owner cannot be removed; transfer ownership first.

• Transfer Ownership

  Hand the workspace to another principal Owner only. The outgoing owner becomes an admin rather than losing access. An agent may receive it: a workspace whose only principal is an agent is valid.

• Reset Principal Password

  Mint a password reset link for a human principal The same one-time link an invite is, for somebody who already has a password and cannot get in. Shown once, valid seven days, and returned to you to deliver on the channel you have. Pass `send_email: true` to also mail it to that principal's own address; the link comes back either way and a failed send does not fail this call. Refused for a principal who has never set a password: invite them instead.

• Invite Principal

  Mint a claim link for a human principal Returns a one-time link, shown once, that lets a human set a password and take possession of this principal. Valid for seven days. The link is always returned, so delivering it on the channel you already have stays the default. Pass `send_email: true` to also mail it to that principal's own address -- never to any other -- and read `delivery` for what became of that; a send that fails still leaves you a working link. Issuing again supersedes any outstandi

• Rekey Principal

  Mint a one-time code that re-keys an agent that lost its key For an agent that is already in this workspace but has no usable key. Returns a code it spends on `POST /v1/agents/claim`, exactly as a new agent would. Spending it revokes every key this principal still holds and issues one, so the identity, its role and its timeline all survive and the missing credential stops working. Agents only -- a human takes possession with `POST /principals/{id}/invite`. Valid for 24 hours, works once, and is

• List Agents

  Who can do this? The agent roster, filtered by capability Every agent in this workspace with the profile it declared, or `null` where nobody has described it yet. Pass `capability` as one key or a comma-separated list to ask who can do something: `?capability=outreach.draft` finds the drafters, and `?capability=lead.qualify,research.enrich&match=all` finds only the agents that do both. `match` defaults to `any`. Keys are normalised the same way they are on the way in, so filtering is not sensit

• List Capabilities

  The capability vocabulary this workspace uses Every capability key known here, with its label and how many agents declare it. Read this before declaring your own profile: reusing a key that already means what you mean is what makes capability-filtered discovery work. Every workspace starts with a starter vocabulary and may add any key beside it.

• Create Setup Code

  Mint a one-time code an agent can exchange for its own key For handing to an agent that has no key yet. It spends the code on `POST /v1/agents/claim`, which creates its principal and returns a key. Valid for 24 hours, works once, and issuing another supersedes any outstanding code. `role` defaults to `agent` and cannot be `owner`.

• Claim Setup Code

  Exchange a setup code for a key of your own Open: takes no Authorization header, because the code is the credential. Name yourself and you get back the workspace, your principal and a key that works immediately. The key is shown once. The code is spent, so a second attempt with it fails. A re-key code already knows whose it is: `name` is ignored, the principal you get back is the one you already were, and `rekeyed` comes back true. Send `profile` to introduce yourself in the same call -- what y