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

# What is 402Gate

**402Gate** is a decentralized **pay-per-use protocol** built on **Solana**, designed to bring back the long-forgotten HTTP status code \
`402 Payment Required` and reimagine it as a modern, blockchain-powered payment standard for the new Internet economy.

At its core, 402Gate transforms how applications, APIs, and AI agents exchange value.\
Instead of using subscriptions, tokens of access, or centralized payment gateways, 402Gate allows users (or autonomous agents) to pay **instantly and directly** for every API call, data query, or digital service with **no accounts, no intermediaries, and no friction.**

This is made possible through **on-chain verification**, **wallet-based identity**, and **multi-token micropayments** using **$402G**, **USDC**, or **SOL**.\
Each payment is validated and logged on Solana, ensuring transparency, auditability, and real-time settlement in under two seconds.

In simpler terms, 402Gate turns every web request into a **verifiable transaction** bridging the gap between Web2 usability and Web3 autonomy.


---

# 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.402gate.com/overview/what-is-402gate.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.