Etsy 'Designed by' AI disclosure: keep a job record per listing
Etsy asks sellers to mark AI-assisted items as designed by the seller and disclose it. Keep the prompt and Sume job id for each listing as your record.
If you use AI to help make listing images or videos, keep a per-listing record of the prompt and the Sume job id. Etsy's creativity standards say AI-assisted items must be listed as designed by the seller and disclosed in the listing description. A job record does not satisfy the policy by itself; it helps you answer questions about how an item was made.
What the Etsy page says
Etsy's creativity standards state that AI-assisted items must be listed as "Designed by" the seller and disclosed in the listing description. A June 10, 2025 update extended this to digital downloads. This was read via a search summary on 2026-10-03, so read the policy itself before relying on it. This post is not legal advice.
What Sume keeps for you
Each Sume generation creates a durable job. The jobs API lets you read it back later.
GET /v1/jobs/{id}returns the job record;GET /v1/jobslists jobs, and athread_idfilter only narrows the list.GET /v1/jobs/{id}/eventsreturns a public timeline such asjob.created,job.completedandwebhook.delivery.GET /v1/jobs/{id}/resultreturns artifacts hosted onmedia.sume.com.metadataon Image 1.0, Video 1.0 and Music 1.0 submits is caller metadata stored on the job and not sent to the provider.
A simple per-listing record
Store these fields next to the listing, in a sheet or a database. The metadata field is a good place to put the listing id at submit time so the job can be found from either side.
| Field | Where it comes from |
|---|---|
| Listing id | Your own; also send it in metadata |
| Prompt text | The request you submitted |
| Job id | request_id in the submit response |
| Idempotency key | The header you sent |
| Result artifact URL | GET /v1/jobs/{id}/result |
| Disclosure text used | What you wrote in the listing |
Limits of a record
Job ownership matters. A job belongs to its workspace and to the member whose key created it, and an API key reads only the jobs its own member created. Export the record before a team member leaves, and treat artifact URLs as opaque rather than parsing them.
See Jobs and results for what each read returns.
Sources
Related posts
More in Use cases
- EU AI Act Art. 50(2): providers must mark AI outputs; ask your API
Article 50(2) requires providers of generative systems to mark outputs in machine-readable form. A checklist of what to ask an AI video or image API vendor.
- EU AI Act Art. 50(4): AI text on public-interest topics and scripts
Article 50(4) asks deployers to disclose AI text on public-interest matters unless a human reviewed it editorially. What it means for video scripts.
- EU AI Act Article 50 timeline: code of 10 June, duties from 2 August
Article 50 transparency duties apply from 2 August 2026. The final labelling code was published 10 June 2026, with about 190 signatories by end of July.
- Reels ads: 9:16, sound on, and a safe-zone brief for generated clips
Meta says Reels default to sound on and favours 9:16 video with audio and key messages in the safe zone. A brief for generating clips that follow it.
Written by Sume