AgentPay Market
Docs

Publish Skills

Publish a Skill

Prepare a ZIP, preview the listing and submit it for review.

Sign in and open Publish Skill. You can publish instructions for your own service or someone else’s; Provider references are optional and do not grant control of a service.

Prepare the package

  1. Choose Download Skill template in the editor. It includes a Runtime call script, service-reference example and README explaining what to change.
  2. Keep exactly one non-empty SKILL.md and an adjacent agentpay.json in the Skill directory. Declare packageName and packageVersion; the template also includes author information. Replace services.main with the Provider’s registered service reference; add another alias for each additional service.
  3. Upload a ZIP up to 2 MiB. Expanded files may total up to 8 MiB, with at most 256 entries and 1 MiB per file.

The initial format check verifies package structure. It is not approval for publication. Market does not choose or increment your package version.

The Runtime template supports qualified services implementing the AgentPay JSON interface. Each call includes its service reference; no global service switch is needed. Complete User/Wallet setup first; a successful format check does not establish Runtime or harness compatibility. Matching calls resume or reuse their verified result without paying again. Use --force only for a deliberate additional purchase.

Describe the Skill

  • Name and Summary: help people identify the Skill in lists and at the top of its page.
  • Introduction: the detailed public description. Explain what it does, how to use it and any paid services it calls.
  • Images: save the draft first, then upload up to 20 images of up to 1 MiB each. Select a cover for lists and the page header; select it again to clear it. Insert in text adds an image to the introduction.

Removing an image from the draft also clears its draft references. Published versions keep their own files.

Save, preview and publish

  1. Save: keep your work private. After the initial draft is established, changed drafts are automatically saved about every 30 seconds when no conflicting operation or review is in progress. Unchanged content does not update the saved time. Check that saving succeeded before leaving.
  2. Preview: open the public-page layout in a separate tab. The Preview only banner identifies it as a draft; it does not publish anything.
  3. Publish: submit for background review and return to Account. The public listing appears only after approval.

Market checks file safety, unsafe instructions, basic content compliance, misleading claims and exposed private information in the package, description and images. You can close the page while review continues.

How submitted content is processed

Files are sent to VirusTotal, whose standard uploads share submitted data with its community. Text and publication images are sent to the configured model service. Do not include secrets or confidential material. Passing review does not guarantee service quality.

Next: open Account → Skills to follow your submission, or read Manage drafts and published Skills.