Vendor Terms

Effective Date— The day selling opens

Vendor terms, version 1 · Published 14 November 2026 · Effective: the day selling opens

1. Who a vendor is

1.1 A vendor is a person or a company that publishes skills on the OPVS store.
1.2 To become a vendor you need a free OPVS account. Selling does not need a paid plan.
1.3 A vendor belongs to one OPVS workspace, and a workspace can be one vendor. You set it up from Skills ▸ Selling in that workspace.
1.4 The people who act for the vendor are the members of that workspace. Workspace admins may change keys, the public profile and store pages. Members may read everything under Selling and edit store pages.
1.5 You are responsible for actions that members you authorise take under Selling.
1.6 A workspace admin accepts these terms for the vendor in setup step ①. By accepting, the workspace admin represents that they have authority to bind the vendor. We record the accepted version, account and time.
1.7 A vendor that starts as a person can later become a company. A company cannot change back to a person.
1.8 What you tell us about yourself, your profile and your skills must be true, and you keep it up to date.

2. Your vendor name, and names nobody can take

2.1 You choose your vendor name (for example @acme) when you set up. Your skills are published under it. It can never be changed afterwards.
2.2 A name must be free when you take it. Some names are reserved and nobody can take them: opvs-ai, opvs, openclaw, anthropic, claude, openai, admin, support, official, and any other name OPVS reasonably reserves to prevent impersonation or confusion, protect rights, or operate the store.
2.3 The name check on opvs.ai/vendors is a hint only. The final check happens when your vendor account is made.
2.4 Your vendor name and your skills' names must not infringe another person's rights, impersonate them, or be confusingly similar to another vendor, skill, company or product. They must not start with someone else's brand unless you own it or have permission.
2.5 Do not say or suggest that OPVS made, reviewed, recommends or partners with your skill, unless OPVS has marked it verified.
2.6 You give OPVS a non-exclusive, worldwide, royalty-free licence to use and display your vendor name, logo and store-page content only to operate and promote the OPVS store while any of your skills is listed, to identify and support a skill already installed in a workspace for as long as it stays installed, and for the 30 days after closing described in 10.3.

3. What OPVS checks, and when

3.1 Every skill you publish, and every new version of it, is checked by an OPVS review agent before it is listed. The agent looks for prompt injection, illegal content, aggressive or misleading marketing, and other harm. If the check fails, the skill or version is not listed and we tell you why. You can fix it and publish again.
3.2 Every time you publish, our servers check, in this order: your vendor account is active; the publish key is yours; the package is signed with your active signing key; the new-vendor limits in section 4; and the blocking security checks. If any check fails, nothing is published and you are told which one.
3.3 A skill that may call a website or service outside OPVS needs that address approved by OPVS first, and you must own or control it.
3.4 Passing the checks means only that a package met the stated automatic rules and the review agent in 3.1 found no issue. It is not a guarantee that the skill is lawful, secure, accurate or fit for a purpose, and it does not mean a person at OPVS reviewed or endorsed it.
3.5 A version that failed a blocking check can never be released.
3.6 OPVS may review or test any of your skills at any time after it is listed, and may ask you to fix something for it to stay listed.
3.7 Your store page must say truthfully what the skill does. No fake ratings or installs, and no reviewing your own skill.
3.8 If your skill sends people's personal data outside OPVS, its store page must link a privacy policy that says what is collected, why, who receives it and how long it is kept.

4. New vendors: the "New vendor" label and the first limits

4.1 Your packages can be public on the store at once. For your first 30 days they carry a New vendor label on the store page and in the install wizard.
4.2 While you have the label you may have up to 5 packages and publish up to 10 times a day. Your packages may be marked internal, beta or community; only OPVS can mark a package verified.
4.3 The label and these limits end after 30 days with no suspension and no package revoked for cause. OPVS staff can also end them sooner.
4.4 A "Verified vendor" badge needs a check that you own your web domain, plus those 30 days. A package is marked verified only after an OPVS review you ask for.
4.5 Where your skills appear on the store, and whether they are featured, is OPVS's choice.
4.6 When you release a new version, workspaces that follow updates get it, usually within 24 hours. A workspace can choose to stay on one version.

5. Your keys, and security problems

5.1 You have two kinds of key: a signing key, which proves a package came from you, and a publish key, which lets you upload.
5.2 OPVS makes your signing key on its server and shows you the private half once. We do not keep the private half after showing it, and we do not write it to any log.
5.3 You must keep both keys secure. Until OPVS receives your compromise report and revokes the key, releases signed with your signing key are treated as published by you.
5.4 Your publish key is also shown once.
5.5 Only workspace admins can make, replace or retire a signing key. Replacing one needs your password again.
5.6 If you lose your signing key, replace it. Versions you already published stay valid.
5.7 If your signing key leaks, or you think it may have, report it without undue delay and in any event within 24 hours after you become aware of the actual or suspected leak, with "My key leaked" in Skills ▸ Selling ▸ Keys.
5.8 When you report a leak we cancel that key, publishing stops until you make a new one, and OPVS staff look at the versions signed after the time you give. OPVS may withdraw any version that it reasonably believes was signed after the actual or suspected compromise.
5.9 If a publish key leaks, cancel it under Keys and make a new one.
5.10 Keep a security contact in your profile that works, and give people a way to report a security problem in your skill. Look into every report you get.
5.11 If you find a security problem in a skill of yours, or buyer details you hold leak (section 7), tell OPVS within 24 hours. Before you say anything in public about it, tell OPVS what you will say.

6. What you see about your skills: numbers only

6.1 For your own packages you see totals and trends: installs, uninstalls, how many run your latest version, uses, success rate, rating, orders, store page views and the top search topics.
6.2 A search topic is shown only when 10 or more workspaces searched for it. You never see the words someone typed or who searched.
6.3 You never see which workspace's agent used your skill, agent names or ids, prompts, inputs, outputs or run logs. No number is split by workspace or by agent.
6.4 The one list of people you see is the orders list in section 7.
6.5 You see your own packages, keys and orders only, never another vendor's.

7. The orders list: who got your skill

What it holds

7.1 When someone gets your skill from its page on opvs.ai (a download or an install into a workspace), the orders list shows: their name, their email, the workspace name, the package, the version they got, how they got it, when, and whether it is still installed.
7.2 Before they get it, the skill page tells them that you will see their name, email, workspace name and version, and that you may contact them about this skill.
7.3 Installs made inside the OPVS dashboard without the skill page, by OPVS staff, or by hiring an agent are not on the list. Nothing from before selling opened is on it.
7.4 A buyer can hide themselves from you later. Their row then shows "Hidden by the buyer", with no name, email or workspace.

What you may do with it

7.5 You may use a buyer's details only to support them with this skill, to answer their questions about it, and to send them its updates and security notices.
7.6 You must not sell, share or rent the list, or any part of it, to anyone.
7.7 You must not use the list for marketing unless each person has given you specific, informed and freely given consent for that marketing, and you let them withdraw it as easily as they gave it.
7.8 There is no export. The page shows one email at a time, with a copy button.
7.9 If you copy a buyer's details elsewhere, keep them safe, keep them only while you need them for 7.5, and delete them when the buyer asks you to.

What you never get

7.10 The orders list never shows the person's agent data, harvest data or usage, the other packages they got, other vendors, their workspace's internal id, or the members of their workspace.

8. Harvest: off for you

8.1 Harvest (reading data from a workspace's agents to improve a skill) is off for vendors who sign up themselves, until a workspace opts in. Selling has no harvest page, link or count.
8.2 How a workspace opts in will be set out separately, before it exists.

9. Suspension, appeal, and getting reinstated

9.1 OPVS staff can suspend a vendor, and always give the reason. Reasons include: a harmful or misleading skill; pretending to be someone else; a leaked key not reported within 24 hours; misuse of the orders list; breaking these terms or the law; and any other serious reason we explain to you.
9.2 While you are suspended: your publish keys and every change under Selling are refused; your packages leave the store listing; nobody can newly download or install them.
9.3 Copies already installed keep running. OPVS can separately withdraw a package, or all your packages, from every workspace; a withdrawal is final.
9.4 While suspended you see a banner with the reason and the security contact, and you can still read everything, orders included, but change nothing.
9.5 If a skill has a security problem, OPVS may hide it from the store until it is fixed and will tell you what needs fixing.
9.6 You may appeal a suspension or a withdrawal once, in writing, within 30 days, from the banner or by email to the security contact. Someone at OPVS who did not make the decision answers within 14 days. A second appeal on the same decision is not taken.
9.7 If OPVS reinstates you, everything comes back except packages that were withdrawn.

10. Closing your vendor account

10.1 A workspace admin can close the vendor account once none of its packages is still on the store; you can hide them at once from each Store page first.
10.2 Workspaces that already installed your skills keep the versions they have. They get no new versions.
10.3 After you close, your orders list stays readable for 30 days so you can answer last support emails, then it is gone.
10.4 OPVS can also close a vendor account. Unless it is for a reason in 9.1, we give you 30 days' notice first.
10.5 Closing ends selling; it does not delete your OPVS account or your workspace.
10.6 Your vendor name never changes, so a closed account keeps the name it had, and nobody else can take it.

11. What is not open yet

11.1 Paid skills are not available yet. These terms cover free skills only. If paid skills open, they will come with their own terms, which you will be asked to accept first. Nothing in these vendor terms limits a buyer's mandatory rights for digital content or services.
11.2 Store pages in more than one language are not available yet.

12. Changes to these terms

12.1 These terms have a version number. At sign-up, a workspace admin accepts the terms for the vendor, and we record which version was accepted, and when.
12.2 At least 30 days before a new version takes effect, we email every workspace admin of your vendor on a durable medium with the new text, effective date and a plain summary of changes.
12.3 A later version takes effect 30 days after we email you about it. There is no new acceptance step: continuing to use Skills ▸ Selling after that date counts as accepting the new version.
12.4 A change the law requires, or one needed to keep buyers safe, can take effect sooner; we tell you why.

13. Responsibility

13.1 The store, the checks and the analytics are provided as they are. OPVS does not promise they are free of errors or always available.
13.2 You are responsible for your skills, including having all rights and licences to publish them, their compliance with law, and their operation in buyers' workspaces to the extent within your control.
13.3 If someone makes a claim against OPVS because of your skill or because you broke these terms, you cover OPVS's costs.
13.4 OPVS is not liable to you for removing, hiding or withdrawing a skill under these terms.
13.5 OPVS's general terms of service cover everything else, including the law that applies and how disputes are handled.