# Promote your package

Source: https://opvs.ai/docs/guides/vendors/promote

> Make your package easy to find and choose: the detail page, ratings and reviews, discovery, the numbers you can read, and where payouts stand.

Once a package is live, these are the levers that help workspaces find it, trust it and install it.

## 1. The detail page

Two layers make up what a workspace sees:

Signed in `package.yaml` (needs a new version)

Marketing overlay (changes any time)

the one-line `description`

the long description

skills, entitlements, credentials, tier

hero image, screenshots, demo video

peers, signing block

feature list, author card

Ship a good baseline in the manifest's `media` and `marketing` blocks so the page looks complete the moment you publish. The **overlay** sits on top: six fields (`hero_image`, `screenshots`, `demo_video`, `long_description`, `features`, `author`). Where both are set, the overlay wins; clearing an overlay field falls back to the manifest. Overlay edits never touch the signed package, and every edit is recorded.

Today OPVS applies overlay edits for you: send the copy and images to vendors@opvs.ai with the package name.

## 2. Ratings and reviews

Workspace users rate and review packages from the OPVS dashboard.

Rating

Review

What

1–5 stars

a title and a text

Needs an install?

no

yes: the workspace must have installed the package (at any time)

How many

one per user, per workspace, per package (re-rating replaces it)

one per user, editable

Reviews are public:

```bash
curl -s "https://market.opvs.ai/api/v1/registry/packages/@acme/leads/reviews"
```

Moderation is after the fact: OPVS can hide a review, with a recorded reason (the review is kept, not deleted). To reply to a review, or to report abuse such as review-bombing, write to vendors@opvs.ai; vendor replies are attached by OPVS today.

## 3. Discovery

Workspaces and agents find packages in three ways:

```bash
# browse, filtered by vendor, category or tier
curl -s "https://market.opvs.ai/api/v1/registry/packages?category=data-collection"

# search by what the agent wants to do (this is what agents use)
curl -s "https://market.opvs.ai/api/v1/registry/search?intent=find%20restaurant%20leads"
```

Agents search by **intent**, ranked by meaning plus recent usage. To be found:

1. Publish at `beta`, so you are listed at all.
2. Write a `description` that names the job in the words a user would use.
3. Fill `aliases` with the phrases agents search for; without them you get a review warning and rank lower.
4. Pick an accurate `category`.
5. Keep the security score high.

**Featured slots** on the marketplace are an editorial choice by OPVS; there is no paid placement. A complete detail page, a clean review score, real adoption, good ratings and something the catalogue did not have are what make a package worth featuring.

## 4. The numbers you can read

```bash
curl -s "https://market.opvs.ai/api/v1/registry/packages/@acme/leads" \
  | python3 -c "import sys,json; d=json.load(sys.stdin); print({k: d[k] for k in ('version','security_score','avg_rating','rating_count','rating_distribution')})"
```

Field

Meaning

`security_score`

0–100 from the [security review](https://opvs.ai/docs/guides/vendors/security-review.md), for that version

`avg_rating`, `rating_count`, `rating_distribution`

the star ratings. `avg_rating` is `null`, not 0, before the first rating.

search results: `cohort_call_count`, `success_rate`

30-day agent call volume and success rate

A low `success_rate` can mean agents call your tool wrongly rather than that your API is down: improve the guidance before you look at your servers. For how your skill is actually used inside workspaces, use [harvest](https://opvs.ai/docs/guides/vendors/harvest.md). A vendor dashboard with install counts and per-tool numbers is planned.

## 5. Payouts

Skills are **free today**, and OPVS is working on paid skills. There are no payouts yet: installs are free and unmetered. The manifest's `pricing` block accepts `model: none | per_call | subscription`, but nothing bills or pays out from it yet. Set `pricing: { model: none }` or leave it out. Publish for reach and adoption; this page will describe the real model when one exists.

## Next

[Harvest](https://opvs.ai/docs/guides/vendors/harvest.md).