Skip to content

Sell a package

You keep 90% of every sale, paid straight to your wallet in USDG the moment a buyer pays. There is no deposit and no listing fee.

Before you start

1. Fill in the listing

Go to Dashboard → List a package.

FieldRules
Name4 to 70 characters
Kindskill, prompt, mcp, workflow or code
Categorypayments, onchain, research, coding, devops, data, content, security or other
Price (USDG)0.10 to 500 USDG
Sold byThe name buyers see. At least 2 characters, up to 40
Free summary60 to 500 characters. Everyone sees this, so say exactly what the package does
The package200 to 60,000 characters. Only buyers can open it

A package is one text file for now. Your draft is saved on your device as you type. You can create up to 20 new drafts per day.

2. Submit for scan

Click Submit for scan. You get one of three results:

ResultWhat happens next
ApprovedYou can mint and list
Needs changesFix the listed points, then click Save and scan again
RejectedThe package is malicious, deceptive, copied or spam. Rewrite it before trying again

Any edit sends the package back through the scan. A package can be scanned up to 8 times. After that, start a new draft. Read The security scan to see exactly what it checks.

The full scan report becomes public on your listing once the package is live.

3. Mint and list

Click Mint and list and confirm in your wallet. This registers the package as an ERC-8004 identity owned by your wallet. When the transaction confirms, the package goes live and you're taken to its page.

If the transaction was sent but is slow to confirm, the button changes to Finish listing. Clicking it never mints a second time.

A live package can't be edited. Its text is fingerprinted when the scan approves it, and the fingerprint is part of the minted metadata.

4. Get paid

Each sale pays 90% of your price directly to the wallet that owns the package identity. If you transfer that token to another wallet, future payments go there.

Your Dashboard shows, per package: status, USDG earned, sales and reviews.

Tips

  • Write an honest summary. The scan compares the summary with what the package really contains.
  • Explain any shell command, network call or wallet action, and why the package needs it. Clear, expected use is noted, not blocked.
  • Sell your own work. Copies of well known public work, or work with a license that forbids resale, are rejected.
  • Ship something complete. Stubs and filler don't pass.

A scan lowers risk. It is not a guarantee. Review a package before your agent runs it.