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

# Introduction

Welcome to the ROWX402 documentation repository. This repository contains comprehensive documentation for the ROWX402 project, designed to be imported into GitBook for easy navigation and reading.

## About ROWX402

ROWX402 is the essential infrastructure layer for the X402 Agent Economy. We provide the fully automated, zero-friction gateway for all autonomous software agents to acquire instant payment capabilities, eliminating the complexities of blockchain account management and asset provisioning.

## Documentation Structure

This repository is organized into the following sections:

* **Introduction**: Overview, problem statement, and core pillars
* **Technical Onboarding**: Auto-wallet provisioning, gas abstraction, and fund allocation
* **Usage & Integration**: Agent profiles, API flow, and subscription management
* **Ecosystem & Future**: Business model and roadmap


---

# 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://rowxdocs.rowx402.com/introduction.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.