> For the complete documentation index, see [llms.txt](https://k4k3ru.gitbook.io/k4k3ru-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://k4k3ru.gitbook.io/k4k3ru-docs/agent/account.md).

# Account and API Credentials

Use K4K3RU Agent to create or restore local account context and create signing credentials for protected operations.

## Sign Up

Run:

```
/account signup
```

Agent guides you through the email OTP flow, creates the account, and writes the resulting account context to local state.

You must be able to receive the OTP at the email address you provide. Do not share the OTP.

## Sign In

If your K4K3RU account already exists but is not configured locally, run:

```
/account signin
```

Agent verifies an email OTP and restores the local account context. Signing protected requests also requires a locally stored, unexpired API credential.

## Create an API Credential

Run:

```
/account api-key create
```

Agent uses your account state and an email OTP to create an API credential. The default credential settings are:

| Setting             | Default                 |
| ------------------- | ----------------------- |
| API name            | Local `whoami@hostname` |
| Signature algorithm | Ed25519                 |
| Lifetime            | 30 days                 |

The new credential becomes the default for signed Agent commands. Treat its signing material as a secret.

## List Local Credentials

Run:

```
/account api-key list
```

This command lists locally stored, unexpired credentials. It does not display their secrets and does not query the service.

## Missing Account State or Credentials

When a signed command cannot find the required local state, Agent keeps the interactive session open and directs you to the relevant sign-up, sign-in, or API-key command.

## Security Guidance

* Do not share OTP codes or credential signing material.
* Do not commit `~/.k4k3ru/auth.json` or copy it into a project directory.
* Avoid including credential files in screenshots, logs, support requests, or diagnostics.
* Each API credential expires. Create a new credential when the selected credential is no longer valid.

For direct API integrations, see [API Request Authentication](/k4k3ru-docs/api/authentication.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://k4k3ru.gitbook.io/k4k3ru-docs/agent/account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.