> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/call/sell-on-call/fees-and-payouts.md).

# Fees and payouts

Self-listed APIs pay a 5% network fee through a Base FeeSplitter; direct-payout Partners have no network fee.

Use this page to see which payout path applies to your listing and where the network fee is enforced. The fee follows the payout path.

See [Groups and fees](/call/reference/groups-and-fees.md) for the discovery group, default visibility, and fee fields.

## Fee by listing type

| Listing type                       | vAPI network fee | Payout path                 |
| ---------------------------------- | ---------------: | --------------------------- |
| Added API, self-listed             |               5% | Your `FeeSplitter` on Base  |
| vAPI endpoint, self-listed         |               5% | The same `FeeSplitter` path |
| Partner, added through the website |               5% | Your `FeeSplitter` on Base  |
| Partner, direct payout             |               0% | Your live `payTo`           |
| External, mirrored                 |               0% | The API's live `payTo`      |

Added APIs pay the 5% network fee through the provider's own `FeeSplitter` on Base. A Partner added through the website uses the same `FeeSplitter` path and pays 5%. A Partner on direct payout and External listings pay no network fee.

## How the splitter pays out

The buyer pays the advertised amount to your `FeeSplitter`. The contract sends 95% of its accumulated USDC balance to your payout wallet and 5% to the immutable vAPI treasury when `distribute()` runs. Anyone can call `distribute()`. The contract has no owner or upgrade path.

The fee is enforced at the payout address, not in the request or quote path. For an Added API, deploy the splitter through the `FeeSplitterFactory`, then set the live x402 `payTo` to the predicted Base address before you activate the listing.

The splitter sends its 5% treasury leg to `FeeRouter`. The current router divides that leg into 33% to the burn sink, 33% to operations, and 34% to the protocol treasury.

FeeRouter sends the rounding remainder to the protocol treasury. If a burn-sink or operations transfer fails, FeeRouter sends that share to the treasury too.

<figure><picture><source srcset="/files/8hi3QV9h26hI4Xvvzo8W" media="(prefers-color-scheme: dark)"><img src="https://565465579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FC8O04QfdFicZZcqBGUz5%2Fuploads%2Fgit-blob-7b871a1a3a696accf5982735133d66954dc658f7%2Fvapi-call-fee-split-light.svg?alt=media" alt="Where the USDC from one paid call goes for a self-listed API. The buyer pays the advertised amount from the live x402 quote, in exact USDC on Base, to your payTo, which is your FeeSplitter; the fee comes out of that amount. The FeeSplitter is your immutable payout address on Base, deployed by the FeeSplitterFactory, with no owner and no upgrade path, and anyone can call distribute(). On distribute(), 95% of its balance goes to your payout wallet, the wallet you proved when you listed the API, and 5% goes to the FeeRouter as the network fee. The FeeRouter splits that 5% leg: 33% to the burn sink, 1.65% of the price; 33% to operations, 1.65% of the price; and 34% to the protocol treasury, 1.70% of the price."></picture><figcaption><p>A self-listed API's payout path. Orange marks where USDC moves.</p></figcaption></figure>

## Base mainnet contracts

| Contract             | Address                                      |
| -------------------- | -------------------------------------------- |
| `FeeSplitterFactory` | `0x8405f917f6EfBd1447aF01Fe879529bcD313279D` |
| `FeeRouter`          | `0xe11aeeC31E54E8E6E66382c8BdBFfd1000E0194B` |

The live x402 challenge remains the source of truth for the current amount and payee.

Checked on 2026-10-15.


---

# 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.vapinetwork.ai/call/sell-on-call/fees-and-payouts.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.