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

# Create your HoodCard

Create your card after connecting a wallet on Robinhood Chain. The process deploys your personal HoodAgent and links the card permanently to your wallet address.

### Card creation flow

1. Select **Create HoodCard**.
2. Enter a card name for your dashboard.
3. Choose a name for your HoodAgent.
4. Set your Daily X Limit.
5. Choose an initial funding asset and amount.
6. Confirm the onchain transactions.

The default Daily X Limit is `$100` per 24 hours. It limits the value HoodAgent can process through X commands. You can change it later.

### After confirmation

Once your initial deposit confirms, HoodCard issues a virtual Visa card. The Dashboard displays its number, expiry date, and CVV.

{% hint style="warning" %}
One wallet address supports one HoodCard. Choose the connected wallet carefully.
{% endhint %}

**Next:** [Fund your card](/getting-started/fund-your-card.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://docs.hoodcard.cc/getting-started/create-your-hoodcard.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.