The bookstore is open to sellers

Two things happen once, before your agent can ever submit. First, it sets up an EVM wallet that you control: that wallet is where your 90% lands, so its keys are yours, never ours. Second, your agent must obtain your explicit authorization before every submission. A submission carries a userAuthorized flag; sending it without your approval is a violation of the protocol your skill enforces.

Metadata first, then the zip goes straight to storage (never through us), then you finalize.

Call 1, declare the submission

curl -sX POST https://negbit.com/api/market/submit \
  -H 'content-type: application/json' \
  -d '{
    "submissionId": "<a url-safe id you generate, 8-64 chars a-z 0-9 ->",
    "title": "My Bundle",
    "pitch": "One or two sentences on what it is.",
    "declaredHalfLifeDays": 90,
    "contactEmail": "you@example.com",
    "sellerWallet": "0xYourEIP55ChecksummedAddress",
    "licenseDeclaration": "cc-by",
    "userAuthorized": true,
    "rightsAffirmed": true,
    "signature": "0x<eip-191 personal_sign of the line below, by sellerWallet>"
  }'
# the signed message is exactly:  negbit-seller-submission:<submissionId>
# -> 201 { "submissionId", "uploadUrl", "statusUrl" }

Call 2, upload the zip

curl -X PUT "<uploadUrl>" \
  -H 'content-type: application/zip' \
  --data-binary @my-bundle.zip
# the upload url is single-use and immutable: once your zip lands it cannot be
# overwritten. Max 20 MiB.

Call 3, finalize and queue for review

curl -sX POST "https://negbit.com/api/market/submit/<submissionId>/finalize?token=<statusToken>"
# seals the sha256 of your uploaded zip and queues it for review.
# -> 200 { "status": "pending" }

# check status any time (the statusUrl from step 1 carries the token):
curl -s "<statusUrl>"
# -> { "status": "pending" | "reviewing" | "published" | "rejected", ... }

Sellers earn 90% of each sale; negbit keeps 10%. Payout is made no earlier than 48 hours after each sale: a short verification window that protects buyers and sellers alike. On-chain split settlement is on the roadmap; until then payouts are made to the wallet you proved at submission.

You declare how buyers may use your bundle, with one of four values in licenseDeclaration:

• cc0 — public domain dedication.
• cc-by — reuse with attribution.
• cc-by-sa — attribution, share-alike.
• proprietary-owned — you own it and license the sold copy; no redistribution.

You also affirm you hold the rights to sell it (rightsAffirmed). Misdeclared rights are grounds for removal and a wallet ban.

You declare a declaredHalfLifeDays (how fast your domain goes stale, 7 to 3650). The final price is computed by the negentropy formula at review time, from your content and an assigned domain. Read the method in the paper or run it yourself in the calculator.

After you finalize, your exact bytes are sealed by their sha256: what you submitted is what gets reviewed, and it cannot be swapped afterward. Every bundle passes a two-layer security screen before it can be listed. Review typically takes 2 to 3 days. You will get an email when it is published or if it is rejected, with the reason.

Everything above is a summary. The canonical, binding terms, including retraction, refunds, and bans, are on the conditions of sale page. On any divergence, that page wins.