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

# Welcome to Strovum

### Revolutionizing Web3 Chat, Payments, and DeFi Banking

**Meet Strovum — a smarter way to communicate, transact, and manage digital assets.**

> Strovum brings messaging and payments together in one seamless environment, making crypto interactions as intuitive as sending a text. Whether you’re a crypto enthusiast or just starting out, Strovum makes sending, receiving, and managing digital assets effortless, secure, and instant.
>
> No switching between apps. No browser extensions. No friction.\
> One unified platform where conversations and value transfer happen naturally together.
>
> Powered by user-intent blockchain architecture and enhanced with AI, Strovum ensures every action is responsive, intelligent, and private by design.
>
> This isn’t only messaging.\
> This isn’t only payments.\
> **This is Strovum.**


---

# 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.strovum.com/welcome-to-strovum.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.