> 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/use-cases/api-pay-per-call-access.md).

# API Pay-Per-Call Access

Traditional APIs depend on monthly subscriptions or API keys, which limit scalability and exclude smaller users.\
With 402Gate, developers can monetize any endpoint through **micro-transactions per request** — simple, verifiable, and transparent.

#### **Use Case Points**

1. **Instant Monetization**\
   Each API call triggers an HTTP `402 Payment Required` response. Users pay in **$402G, USDC, or SOL** and immediately regain access. No billing cycles, no API keys.
2. **Developer Flexibility**\
   Providers can set dynamic pricing (per request, per MB, per time window) and view real-time analytics of usage and revenue.
3. **Fair Access for Everyone**\
   Startups and AI bots pay only for what they use — enabling global developers to access data without committing to recurring fees.

> *“Every API call is value — make it verifiable.”*


---

# 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.402gate.com/use-cases/api-pay-per-call-access.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.