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

# Get discovered

x402 Bazaar metadata helps buyers find APIs; Call also exposes discovery, an Atom feed, and a machine-readable API catalog.

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

Add x402 discovery metadata so buyers and agents can find your API. Call also publishes its own discovery surfaces for listings that pass its rules.

## Add Bazaar metadata

Add the x402 Bazaar extension to your 402 response. This makes the API discoverable in Coinbase's x402 Bazaar and by Coinbase for Agents. `vapi check` reports `bazaar_metadata_missing` when the extension is absent. The warning does not block a listing.

See [x402 extensions](/call/reference/x402-extensions.md) for the metadata Call reads from your 402 response and from the Coinbase x402 Bazaar.

## Use vAPI discovery

Call exposes these surfaces:

* Search in the Call directory and through the public discovery API.
* The hosted MCP server for search and inspection.
* The RFC 9727 API catalog at `/.well-known/api-catalog`.
* The Atom feed at `/call/feed.xml`, which lists new verified self-listed, Partner, and claimed listings.

Default search includes verified listings and the External catalog. Include unverified APIs to add self-listed listings that passed the automated probe but have not received verification.

## Identify payments

The console and `vapi` client attach the x402 `builder-code` extension with `vapi` for on-chain attribution on every payment they make.

## On-chain identity

Listings whose provider payout wallet is registered in the ERC-8004 Identity Registry on Base show **On-chain identity** and reputation on the listing page. `vapi inspect` prints `On-chain identity:` and `Reputation:` lines. `vapi whoami` prints the wallet's own identity or `not registered`, and `/api/call/services` carries `identity`.

This is read-only. vAPI reads the registries and never writes to them. On-chain identity is separate from vAPI verification.

The Base mainnet registry addresses are:

| Registry   | Address                                      |
| ---------- | -------------------------------------------- |
| Identity   | `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432` |
| Reputation | `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63` |

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