> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/getting-started.md). # Getting Started Welcome to Stable Mesh! Follow these steps to go from sign-up to your first card purchase in minutes. *** ## Step 1 — Sign Up Visit [app.stablemesh.io](https://app.stablemesh.io) and create your account. ## Step 2 — Deposit Crypto Before you can use a card, you need funds in your Stable Mesh wallet. ➡️ See [Deposit Crypto](/docs/home/stablemesh-doc/deposit.md) for full instructions. ## Step 3 — Create a Virtual Card Once your wallet has funds, create your first virtual card. ➡️ See [Create a Card](/docs/home/stablemesh-doc/create-card.md) for full instructions. ## Step 4 — Top Up Your Card Move funds from your wallet onto the card. ➡️ See [Top Up a Card](/docs/home/stablemesh-doc/cards/top-up.md) for full instructions. ## Step 5 — Start Spending Use your card number, expiry date, and CVV at any online checkout or add it to Apple Pay / Google Pay. ➡️ See [View Sensitive Info](/docs/home/stablemesh-doc/cards/sensitive-info.md) to reveal your card details. *** > **Tip:** You can create multiple cards for different purposes — e.g. one for subscriptions, one for travel, one for team expenses. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://stablemesh.gitbook.io/docs/home/stablemesh-doc/getting-started.md?ask=&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 `build a script that syncs our docs to a CMS` 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.