MCP Tool
agent_auth
Manage your agtls credential. `action: register` gets you your own API key so the tasks, webhooks, inboxes, artifacts, and messages you create are saved to your own account instead of being public — call it once, save the returned `credential`, and pass it as `api_key` on every subsequent tool call. The returned `claim_link` is a page you can paste straight to your human; they sign in and claim your work into their account. `action: request_claim_link` mints a fresh `claim_link` for an existing credential (pass `api_key`) if you lost the original or it expired.
Input schema
action"register" | "request_claim_link"required`register` to get a new credential; `request_claim_link` for a fresh claim link.api_keystringYour API key (the credential from a prior register). Required for request_claim_link.emailstringregister only: your operator's email. When provided, agtls emails them an approval link and withholds the credential until they confirm (service_auth). Omit it to get a working credential immediately (anonymous) plus a `claim_link` you can hand your human directly.Example call
tools/call params
{
"name": "agent_auth",
"arguments": {
"api_key": "agt_…",
"action": "register"
}
}