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

# Onramps

Explore reliable fiat-to-crypto onramps that connect users from traditional payment methods directly to Gravity, enabling smooth and secure blockchain access.

## **Overview**

Fiat onramps are essential gateways that allow users to purchase cryptocurrencies using traditional payment methods like credit cards, bank transfers, and e-wallets. They simplify Web3 access by bridging the gap between fiat currencies and crypto assets.

## **Onramps**

### Onramp.money

Onramp.money is a secure crypto onramp platform that enables users to buy, sell, and swap over 400 tokens across multiple blockchains including Gravity. Users can purchase cryptocurrencies using local payment methods, including bank transfers and mobile wallets, across more than 30 countries.

[Buy G on Onramp.money](https://onramp.money/)

***

### Alchemy Pay

Alchemy Pay is a global payment gateway that bridges fiat and crypto economies, supporting payments in 173 countries. It enables users to purchase cryptocurrencies using Visa, Mastercard, Apple Pay, Google Pay, regional mobile wallets, and domestic bank transfers. Alchemy Pay also offers off-ramping capabilities, allowing users to convert crypto back to fiat currencies.

[Buy G on Alchemy Pay](https://alchemypay.org/)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gravity.xyz/ecosystem-infrastructures/onramps.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
