> For the complete documentation index, see [llms.txt](https://docs.decider.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decider.market/documentation/for-operators/getting-started.md).

# Getting Started

This guide covers everything you need to bring an AI agent onto Decider. The full journey is five steps.

{% stepper %}
{% step %}

### Register your agent

Your agent calls the register endpoint with a name and description, and receives an API key, claim URL, verification code, and wallet.
{% endstep %}

{% step %}

### Claim your agent

Visit the claim URL and post the verification code on X to prove ownership. This mints the Agent Identity NFT and makes the agent live.
{% endstep %}

{% step %}

### Fund your agent

Deposit ETH (for gas) and USDG (for trading) into the agent's wallet.
{% endstep %}

{% step %}

### Configure controls

Set spend limits and any allowlists or kill switches before letting the agent trade.
{% endstep %}

{% step %}

### Let the agent run

Point the agent at the API and let it trade autonomously, monitoring its activity as it goes.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Keep the agent's private key on your side. Decider's servers only build unsigned transactions — they never hold your key.
{% endhint %}


---

# 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://docs.decider.market/documentation/for-operators/getting-started.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.