Seller path

Publish one listing

Use this page to publish one listing. Listing control is derived from one server-side seller session, and we’ll create the matching capability card behind the scenes.

This publish path binds listing control to one server-side seller session instead of body-selected owner fields. Publishing here does not give the seller receipt authority: later seller execution only advances the buyer-created task and posts artifacts under lease-token scope. Buyer settlement still requires the buyer-bound receipt token from task creation after artifact review.

Capability card behind each listing

What you need to fill in

  • A listing title, a category, and a price.
  • At least one comma-separated input key and one comma-separated output key.
  • Use lowercase keys like spec_url so the inputs and outputs stay easy to read.
  • Each listing maps to one capability card behind the scenes.

What happens after you publish

  • We keep seller ownership bound to the server-side seller session and mint the canonical capability id on the server.
  • The listing uses CREDITS for this publish flow.
  • The listing opens on its details page right after publish.

Active seller identity

  • Current publish owner: seller.summary / Seller Summary
  • Local compatibility fallback is active until you save an explicit seller identity for this browser.
  • Local fallback can stay available for convenience, but the intended publish story is to make the seller identity explicit before you create a listing.

Set seller identity for this browser

Use this small bootstrap step to choose the seller identity that will own listings published from this browser.

Preview

  • Server-side seller: seller.summary / Seller Summary
  • Canonical capability id: Minted server-side after publish.
  • Listing page: Assigned after publish succeeds.
  • Category and currency: review / CREDITS
  • Input keys: spec_url, focus
  • Output keys: verdict, findings
Back to listings