> 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/for-providers/partner-program.md).

# Partner program

Partner listings require operator approval; direct-payout Partners use their own x402 payout address without a network fee.

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

A Partner listing is an operator-approved listing for a provider-hosted x402 endpoint. Use this path when you want Call to list your origin directly and show Partner provenance.

## What Partner status means

Partner status is an operator action, not an automatic result of publishing. A Partner listing uses its concrete origin x402 endpoint directly. A direct-payout Partner listing does not need a `FeeSplitter` or an owner wallet signature, and it has no network fee.

## Onboarding ladder

Start at the highest rung you can reach:

1. **Native x402:** You already serve x402 at your origin. vAPI probes and lists the endpoint, then stays outside the request path.
2. **Adapter:** You deploy an open-source x402 adapter in front of your existing API. Your upstream key, payout address, and origin remain yours. vAPI stays out of the request and money paths.
3. **Hosted shim:** The decision describes this route, but it is not built. It is not a current onboarding path.
4. **Nothing:** If you do not use one of the available routes, the API is not listed.

The publish flow does not create a vAPI proxy or an operator-funded upstream call. If your endpoint does not return a supported 402 challenge, the flow provides Node and Python integration guidance and a retest path.

Partner status is handled by a vAPI operator. Publishing an API creates an Added API, not a Partner listing.

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/for-providers/partner-program.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.