# Core Revenue Architecture

WGA’s revenue is generated through the following four structured circulation models.

| Category                                                           | Description                                                                                                                                                                                                                                                             | Payment & Settlement Structure                                                                                                                                                                               |
| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **1. Proof-based Campaign Execution Fee**                          | When advertisers or projects deposit campaign budgets, the funds are automatically distributed into: ① campaign operations, ② participant rewards, and ③ AI verification costs. Around 5–10% is allocated as platform operation and data verification maintenance fees. | Campaign budgets are settled in XYZ units and reflected in the **Reward Pool** and operational accounting (recorded both Off-chain and On-chain).                                                            |
| **2. AI Analysis & Verification Reports (B2B SaaS / API Service)** | The **AI Proof Engine** provides companies and institutions with performance reports, ROI analysis, and predictive reports based on verified datasets.                                                                                                                  | Payments are made in **Fiat (credit card, remittance)** or **USDT**. The payment amount is converted internally into XYZ-denominated revenue and reflected in the **Reward Pool** and foundation accounting. |
| **3. Soft DePIN Network Usage Fee (Node Service Fee)**             | Services or websites connected via SDK/API are automatically registered as **Soft Nodes**, supplying data to the Proof Engine. Fees are charged based on data transmission and throughput volume.                                                                       | Companies or partners are billed monthly based on data throughput. Payments in **Fiat/USDT** are converted internally into XYZ and reflected in accounting.                                                  |
| **4. Verification API / SDK Licensing**                            | External institutions, exchanges, or marketing agencies use WGA’s data verification API to implement their own system-level verification features.                                                                                                                      | **B2B contract licensing** (USD/USDT payment) → converted into XYZ-denominated revenue and reflected in accounting.                                                                                          |

**This structure connects AI Proof → verified data generation → service/API consumption → internal token economy,**\
where external fiat revenues are converted into internal token-based circulation and accounting.


---

# 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://web3-growth-agent.gitbook.io/wga-whitepaper-ver-1.5_en/.-business-model-and-market-strategy/core-revenue-architecture.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.