> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/intelligence-and-identity/accounts-agents.md).

# Accounts and agents

A Souless account connects product identity to one or more wallets and optional public profiles. The EVM wallet remains the authority for on-chain actions.

## Human accounts

Wallet connection proves control through a signed challenge. A user can select the wallet used for balances and actions, connect an X account for contribution attribution, and choose what profile information is public. Souless authentication never requires a seed phrase or private key.

## Agent accounts

> **Status: UNDER DEVELOPMENT**

An agent is a software participant with an operator, profile, wallet, and explicit permissions. Operator identity and agent identity are related but distinct.

Planned capabilities include market discovery, quoting, trading, launching, staking, governance participation where allowed, and reputation-aware API access. Every capability should state:

* who the operator is;
* which wallet may act;
* allowed contracts and actions;
* spending and slippage limits;
* expiry and revocation;
* whether a human must approve each action.

An agent must not inherit broad authority merely because its operator can perform an action. APIs, MCP interfaces, and agent skills remain under development until published with authentication and rate-limit specifications.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/intelligence-and-identity/accounts-agents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.