> 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/get-verified.md).

# Get verified

Call verification is a review tier that adds eligible listings to default search and raises their trust score.

Verification is a review tier for a live listing. It adds the listing to default search and raises its trust score.

## Understand the states

The tier has four states: `none`, `requested`, `verified`, and `rejected`. The public wire never shows `rejected`.

`none` means the listing passed the automated x402 probe but has not been reviewed. `requested` means review is requested and the listing stays live. `verified` means vAPI reviewed the listing against the published rubric. A rejection also leaves the listing live, and you can request verification again.

Default search shows verified self-listed listings and the external catalog. Include unverified APIs to show listings in `none` or `requested`. Within a group, relevance ranks first. A more relevant unverified listing can appear above a verified listing when unverified APIs are included.

## What the review checks

The published rubric checks these points:

1. Every endpoint answers a live 402 quote and a paid call.
2. The quote pays the listing's own payout address.
3. The published request schema matches what the endpoint accepts.
4. The paid amount, asset, and network match the quote.
5. Three separate paid calls per endpoint stay inside the stated latency budget.
6. Your identity and the endpoint host resolve to the same party, without impersonation.
7. The listing and a sample response contain no content prohibited by the console terms.
8. Non-idempotent methods declare retry safety, and one retry is checked.
9. Every 402 matches its declared x402 version and has no conformance issue.

Verification is not a guarantee of quality or uptime. The live endpoint remains the source of truth for every quote, and a verified listing can still be suspended when it stops answering.

## Request verification

In the console, open **My APIs** at `/call/my-apis` and choose **Request verification** on the listing. After a rejection the same place offers **Request verification again**, with the stored reason.

With `vapi`, request review by slug:

```bash
vapi publish verify-request <slug>
```

The machine API uses the same status action:

```http
POST /api/call/listings/<slug>/status
Authorization: Bearer <api-key>
Content-Type: application/json

{"action":"request_verification"}
```

The request re-probes the endpoints. The listing stays live while the review is pending.

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/get-verified.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.