> 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-buyers-and-agents/find-apis.md). # Find APIs Call search finds APIs by capability and shows listing details, verification, and live x402 payment facts before you pay. {% hint style="info" %} Call is launching. The console does not serve Call yet; this page describes the launch flow. {% endhint %} Search Call in the console or with `vapi` to find APIs by capability. Use the listing details and live check facts before you pay. ## Search in the console Open [Call](https://api.vapinetwork.ai/call), enter what the API should do, and open a listing. The Call directory at `/call` is one ranked catalogue with a card view and a table view. Use sorting and the **Source** filter for **vAPI endpoints**, **Added APIs**, **Partners**, and **External**. A preview sheet opens from a listing before you visit its page. Each listing page is a product-style page with a description, endpoints, live quote, verification, fee, liveness, and identity. Your own listings live at **My APIs** at `/call/my-apis`; add one at **Add API** at `/call/my-apis/new`. The directory groups results in this order: 1. **vAPI endpoints** 2. **Added APIs** 3. **Partners** 4. **External** Results are ordered by group first. Within a group, Call uses relevance, trust, and freshness. ## Search with `vapi` ```bash vapi search "" ``` Use `--include-unverified` to include unverified self-listed APIs: ```bash vapi search "" --include-unverified ``` Use `--network ` to filter by network: ```bash vapi search "" --network ``` The discovery request uses the `network` query parameter: ``` https://api.vapinetwork.ai/api/call/discovery?q=&network= ``` ## What the groups mean * **vAPI endpoints** are first-party self-listed APIs. * **Added APIs** are self-listed APIs published through the provider flow. * **Partners** are listings with partner provenance. * **External** listings are mirrored from the Coinbase x402 Bazaar. See [Groups and fees](/call/reference/groups-and-fees.md) for the provenance, payout path, and default visibility of each group. The group is separate from the verification tier. Trust labels can also appear together: **Live x402**, **Payout wallet confirmed**, **Partner**, **vAPI**, and **External catalog**. ## Machine Payments Protocol An API that answers `402` with a `WWW-Authenticate: Payment` challenge from Stripe/Tempo Machine Payments Protocol can be listed and is shown with the label **MPP (Stripe/Tempo), not payable here**. vAPI does not pay MPP, neither the console nor `vapi pay`. `vapi check` recognises it: the `transport` rule passes with the `mpp` tag, and the JSON report's `transport` field is `x402` or `mpp`. ## Verification and visibility The verification tier is one of `none`, `requested`, `verified`, or `rejected`. The public wire does not say `rejected`. By default, search shows verified listings and external catalog listings whose catalog-reported live x402 check succeeded within the last 24 hours. In the console, turn on **Include unverified APIs** to add unverified self-listed APIs. The same switch is `--include-unverified` in `vapi` and `includeUnverified=true` in discovery requests. With the switch on, external listings are shown regardless of freshness. ## Freshness and liveness Self-listed and partner listings are rechecked every hour. Mirrored external listings are checked at most once a day. Anyone can trigger a recheck for a listing. Listings show when Call last checked them. Once a listing has three checks in the last seven days, its checked facts can also show uptime for that period and p50 and p95 latency. 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-buyers-and-agents/find-apis.md?ask=&goal= ``` `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.