> 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/reference/groups-and-fees.md).

# Groups and fees

Call groups listings by source; provenance, verification, payout path, and network fee are separate listing facts.

{% hint style="info" %}
Call is launching. The console does not serve Call yet; this page describes the launch flow.
{% endhint %}

Use this page to understand why a listing appears in a Call group and which payout path applies. The live x402 challenge remains the source of truth for the amount and payee.

## The four groups

Call derives the group from provenance and ownership. The group is separate from the verification tier.

| Group              | What it is                                                                         |                                                                                                  Network fee | Payout path                                                 | Default visibility                                                             |
| ------------------ | ---------------------------------------------------------------------------------- | -----------------------------------------------------------------------------------------------------------: | ----------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **vAPI endpoints** | A `self_listed` listing owned by a wallet in the first-party provider wallet set.  |                                                    5% through the FeeSplitter path for vAPI's own paid APIs. | The listing's `FeeSplitter` payee.                          | Verified listings are shown by default.                                        |
| **Added APIs**     | A `self_listed` listing whose owner is not in the first-party provider wallet set. |                                                         5% on Base through the provider's own `FeeSplitter`. | The provider's Base `FeeSplitter` is the live `payTo`.      | Verified listings are shown by default.                                        |
| **Partners**       | A listing with `provenance: "partner"`, added through the partner flow.            | 0% when paid directly, or 5% when the partner is added through the website and paid through a `FeeSplitter`. | The provider's live `payTo` directly, or its `FeeSplitter`. | Partner listings are shown by default when eligible.                           |
| **External**       | A listing with `provenance: "indexed"`, mirrored from the Coinbase x402 Bazaar.    |                                                                                                          0%. | The provider's own live `payTo` directly.                   | Shown when the catalog-reported live check succeeded within the last 24 hours. |

The `includeUnverified` switch adds unverified self-listed listings with verification `none` or `requested`. With the switch on, External listings are shown regardless of catalog-check freshness.

## Sort order and discovery fields

Group is the primary sort order: `vapi`, `added`, `partner`, then `external`. Relevance, trust, and freshness are applied within each group.

Discovery responses carry `group`, `fee`, and `verification` on each listing. You can see these fields on [`/api/call/discovery`](https://api.vapinetwork.ai/api/call/discovery) and [`/api/call/services`](https://api.vapinetwork.ai/api/call/services).

## Added API payout

For an Added API on Base, the buyer pays the advertised amount to the provider's `FeeSplitter`. Anyone can call `distribute()`: 95% of the accumulated USDC goes to the provider's payout wallet and 5% goes to the vAPI treasury. The splitter has no owner or upgrade path.

The fee follows the payout path. It is not added as a markup in the request or quote path.

## Routed through vAPI

`/call` and `GET /api/call/stats` show USDC settled through vAPI clients for 24h and 30d, plus the transaction count. The totals are counted from the x402 `builder-code` tag (`vapi`) in settle calldata, and `vapi stats` shows them too. This is network volume attributed to vAPI clients, not vAPI revenue.

See [x402 extensions](/call/reference/x402-extensions.md) for the `builder-code` extension.

Checked on 2026-10-02.


---

# 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.vapinetwork.ai/call/reference/groups-and-fees.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.