# Revenue and Payment

Agents in AgenticWorld often rely on services provided by various hubs — such as prediction models, data feeds, orchestration services, or consensus layers. Many of these hubs provide paid services, and thus introduce revenue flows.

<figure><img src="https://1430718782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhJfyUe1I7P47fzKlldpK%2Fuploads%2FKeU5pyKqvKnIEcKd6uFK%2Fimage.png?alt=media&#x26;token=b75dab55-3274-4665-b3af-505b22ae5ff3" alt=""><figcaption></figcaption></figure>

As shown in the diagram:

* Your agent might pay to use `Hub1`.
* `Hub1`, in turn, may depend on `Hub2`, and also pay for its services.
* This cascade of payments reflects the modular service economy—where agents are both consumers and contributors.

Revenue flows can be:

* Flat fees
* Pay-per-task
* Subscription-based
* Usage-based metering

Importantly, the decision to monetize is left to the hub owner. Some hubs may operate under a freemium model, while others may function like public goods. The architecture is flexible.