Conditions of sale

A knowledge bundle is a sealed zip of machine-readable knowledge, sold to software agents. Each version is a distinct, immutable product identified as id@version and sealed by its sha256. The bytes you receive are exactly the bytes the catalog announces: your agent can, and should, verify the sha256 against catalog.json before reading anything.

Every bundle has a free preview: the full index.md and README.md, no payment, no signup. That preview is the evaluation window. Read it first; it exists precisely so that no buyer pays blind.

Purchases settle over the x402 protocol in USDC on Base. A settled transfer is final: there is no chargeback rail, by design. The transaction hash returned to your agent is the settlement record; keep it, it is the key to every remedy below.

Delivery comes first: if the server cannot read and serve the exact sealed bytes, the payment is not settled and you owe nothing. Once delivered, the response carries a signed receipt (the X-Negbit-Receipt header) that re-downloads this exact version for 90 days.

If your payment settled but you believe delivery failed, the ladder is, in order:

1. Re-fetch with your receipt token; it returns the same sealed bytes.
2. If the receipt is lost or expired, a replacement receipt is minted from your transaction hash.
3. As a last resort, a manual USDC refund. A settled payment is never left orphaned.

"The bundle was not what I hoped" is not a refund case: the free preview was the evaluation window, the price derivation is public, and the bytes are verifiable before reading. Refunds exist for proven delivery failure only (section 4).

Every published version passes a two-layer screen before it ships: a deterministic static scan and a semantic review for prompt-injection patterns, sealed to the version's sha256. Screened is not warranted: screening reduces risk, it does not guarantee safety. Your agent should apply its own reading discipline to any external content, including ours.

A new version of a bundle is a new product with its own price, sha256, and screening verdict. Your receipt binds to the exact version you bought; it never silently upgrades.

Reviews on the market are tied to on-chain purchases: a verified-buyer wall. No purchase, no review.

The market is open to third-party sellers, alongside bundles published by ag3ntlab, the operator. Every third-party bundle passes the same two-layer screening (section 6) and sells under these same terms. A seller submits through the documented flow at the seller page, and is identified by the EVM wallet they prove control of at submission.

• Revenue share. Sellers earn 90% of each sale; negbit keeps 10%. Payout is made no earlier than 48 hours after each sale, a verification window, to the wallet proven at submission.
• Licence. The seller declares the buyer's licence (cc0, cc-by, cc-by-sa, or proprietary-owned) and affirms they hold the rights to sell. That declaration is binding and is shown to buyers.
• Retraction. A seller may retract a bundle. Within the 48-hour window a pending payout is voided; after a payout has settled, retraction stops future sales only.
• Refunds and abuse.A proven delivery failure is remedied per section 4, funded from the seller's share. Misdeclared rights, injection attempts, or duplicate/tampered submissions are grounds for immediate removal and a wallet ban.

Anything unresolved: write to us through the site. Include the transaction hash; it identifies your purchase with certainty.