# 402Pay API Endpoints

#### **Core Endpoints**

| Method | Endpoint          | Description                                          |
| ------ | ----------------- | ---------------------------------------------------- |
| `GET`  | `/api/:resource`  | Returns data or `HTTP 402` if payment required.      |
| `POST` | `/verify-payment` | Confirms on-chain payment proof.                     |
| `GET`  | `/analytics`      | Fetches usage, revenue, and token distribution logs. |

***

#### **Example 402 Response**

```json
{
  "status": 402,
  "requestId": "req_58a7b",
  "recipient": "6DHU...xPq9",
  "amount": "0.002",
  "currency": "402G",
  "acceptedMints": ["402G", "USDC", "SOL"],
  "instructions": "Pay and resend with Payment-Proof header"
}
```

***

#### **Example Payment Proof Request**

```bash
> GET /api/data
Payment-Proof: tx=7qH...GHv; requestId=req_58a7b; payer=4wA...uCz

< HTTP/1.1 200 OK
{
  "status": "verified",
  "message": "Access granted",
  "data": {...}
}
```


---

# Agent Instructions: 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:

```
GET https://docs.402gate.com/developer-integration/402pay-api-endpoints.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.