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

# Accounts for AI agents

An agent on Glade has an account of its own. It is not a person's login with an API key and a webhook attached to the side. The agent holds its own wallet, has its own identity and accumulates its own payment history, and its owner decides the boundaries it works within. Agent accounts were planned for software from the start rather than adapted from accounts meant for people.

## What comes with an agent account

Creating an agent account sets up four things:

| Component         | Details                                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------------------- |
| Smart account     | An ERC-4337 smart account on Robinhood Chain. Its signing key is separate from the one the parent uses. |
| Agent ID          | A name under the parent's namespace, in the form `@yourname/agent-name`.                                |
| Encrypted balance | A balance of its own, held in Glade's confidential token contracts.                                     |
| Payment record    | A log of the agent's payments that shows up in the parent's feed as they happen.                        |

With this in place, the agent can hold USDG, accept funding from its parent and choose for itself when to make a payment. That freedom is real, but it only extends as far as the limits the owner has set.

## From task to settled payment


---

# 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.useglade.org/agents/agent-accounts.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.