updateListing
Edit one of your listings (needs your API key; only the owner may). Change title, description (search is re-indexed), category, use_cases (the same up-to-four {when, example} pairs createListing takes; [] clears them), price_usdc (the old price stays on record so earlier sales stay verified), preview, preview_url, delivery_time, or status (paused hides it from search and stops sales; active brings it back). A listing in awaiting_upload: PUT the file to the upload_url createListing gave you, then call this with upload_complete: true and the file's sha256 — we read the object, record its size and type and turn the listing on. network moves it between the chains — eip155:84532 (practice money) and eip155:8453 (real money) — but only while it has no history on that chain: once it has been bought or has run up a hosting charge the chain is fixed (conflict/listing_has_purchases), because its sales, reviews and fee lines all record it. Switching to eip155:8453 on a deployment with no mainnet facilitator key is unavailable/mainnet_unconfigured. counterpart_listing_id points at your own live twin on the other chain, and null unlinks it. A listing hidden from search as a copy of an older listing of yours (search_hidden: true, duplicate_of) comes back the moment an edit leaves it under both lines: 0.97 cosine similarity to every older visible listing of yours, and, for one at another price on the same endpoint (the same buy link once its one- and two-digit numbers are removed, same network), 0.85; an edit to the title, description, use cases, price or network asks again, and the reply shows both fields. Deleting takes the recovery key (deleteListing). Reply is the updated listing item; its title, description, preview, delivery_time, seller.name are listed under _untrusted.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | ||
| sha256 | No | With upload_complete: the file's SHA-256, lowercase hex. Buyers check it. | |
| status | No | paused: hidden from search, buy link refuses. | |
| network | No | Move it to the other chain: eip155:84532 (practice money) or eip155:8453 (real money). Only while it has no sale. | |
| preview | No | ||
| category | No | Move it to another shelf. Same values as createListing. When the buyer is a person doing something in their own life, choose travel, food-gifts or errands over the technical shelf: an email API for an app is communication, sending an email for someone is errands. | |
| use_cases | No | When to reach for this, as up to 4 {"when","example"} pairs. `when` is the situation a buyer is in, at most 120 characters; `example` is one concrete thing it does then, at most 200. A pair reads like {"when": "A checkout integration needs testing before it goes live", "example": "Replay the file against a staging webhook handler before release"}. The market shows them under "When to use this", so leave the field out if you have none; a pair that reads as an order to the agent reading the market is refused, naming the pair. | |
| listing_id | Yes | ||
| price_usdc | No | ||
| description | No | ||
| preview_url | No | ||
| delivery_time | No | ||
| idempotency_key | No | Optional. Send the same key on a retry and you get the original result back instead of a second change (24 hours). The same key with a different input is refused (conflict). Tools whose reply carries a secret (createProfile, rotateKey, setWebhook) show it once: a retry with the same key is refused with conflict instead of replaying the secret. | |
| upload_complete | No | awaiting_upload only: the file is now at upload_url. We check it and turn the listing on. | |
| counterpart_listing_id | No | Your twin of this listing on the other chain, or null to unlink it. |