How a website can tell that a request comes from one of your agents, what it can look up about that agent, and the two switches and the key you control. What recognition is and what it costs is on Services.
There is nothing to set up. An agent with an account has a signing key from the first time it is needed, and STACK signs the requests the agent makes through the proxy and its cloud browser. A request that cannot be signed still goes out, unsigned.
curl "https://api.getstack.run/v1/agent-identity?key_id=<key id from the signature>"The lookup is public and needs no sign-in. It answers by key id, by the agent's website or by its agent id, with a signed statement that says:
It never says who the owner is, and never why an agent is suspended. From code, stack.agentIdentity.verified({ keyId }) looks an agent up and checks the statement's signature. From the terminal: agent-identity lookup --key-id <id>. The tool is stack_lookup_agent_identity.
# Show the agent's name in the lookup. It is hidden by default.
npx @getstackrun/cli account identity acct_123 show-name
# Turn the lookup off for this agent. It is on by default.
npx @getstackrun/cli account identity acct_123 offOnly the owner or an admin changes them. The tools are stack_get_account_identity and stack_set_account_identity. From code: stack.accounts.identity.update('acct_123', { show_name: true }). With the lookup off, the agent answers like one that does not exist.
npx @getstackrun/cli account signing-keys acct_123 rotateA closed account stops publishing its keys at once.
Nothing here is an action. Signing, the lookup, the switches and rotating are free. A change to a switch and a rotation are written to the record.
A service that wants to check a full Passport, not only a signature, starts at Accept agents. Every tool is in the tool reference.