> 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/for-vendors/list-your-api.md).

# List your API

**Agents are the fastest-growing group of buyers on the internet, and they cannot fill in your signup form.** They cannot create an account, store an API key, or enter a credit card. Listing on vAPI gives your existing API a new distribution channel: discoverable and payable by agents, paid per call in USDC, with nothing about your infrastructure changing. Your API stays at your origin, vAPI never proxies your traffic, and payments settle straight to a contract only you control.

{% hint style="info" %}
Vendor publishing is a guarded beta. Registration at `/call/register` requires access.
{% endhint %}

**Already serving x402?** 

Then you may already be indexed and discoverable on vAPI at a 0% fee. Self-listing adds what an indexed entry cannot carry: ranking, reviews, and a verified badge, with payouts to a contract only you control.

**Not on x402 yet?** 

You deploy a small open-source adapter in front of your existing API. You keep your upstream key, your origin, and your payout address.

## Setup flow

1. Supply an HTTPS origin, endpoint, or OpenAPI URL in the console.
2. vAPI discovers the OpenAPI and x402 metadata and enumerates payable operations.
3. Select the operations to publish; review each method, live quote, request schema, and response content type.
4. Prove control of your payout wallet with one signature.
5. Point each endpoint's live `payTo` at your predicted splitter address per network; the listing saves as a draft.
6. Deploy the splitter (deployment is permissionless; typically your own wallet does it).
7. Activate. vAPI re-checks every live quote and verifies each splitter onchain before the listing goes public.

If your endpoint does not return a supported 402 challenge yet, registration provides Node and Python integration guidance and a retest path.

## What validation does and does not prove

The probe confirms your endpoint is reachable and records its live method, price, network, asset, and payee. It accepts HTTPS only, rejects private and reserved addresses, follows no redirects, limits response size, and times out. It is not an audit of your API. After publication, your live 402 challenge stays authoritative; stored prices can go stale, and buyers validate the live challenge before signing.

## Payout verification

Your signature proves control of the beneficiary wallet. At activation, vAPI reads the deployed splitter onchain: its `vendor()` must match your proven wallet and its `treasury()` must match the vAPI treasury. Re-verification happens at probe, publication, and activation.

Fees per listing source are on [Fees and the splitter](/for-vendors/fees-and-splitter.md).


---

# 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/for-vendors/list-your-api.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.