Claid

DESTRUCTIVE. Remove a storage connection from this Claid account. Claid stops being able to read from or write to that bucket, so every workflow whose `output` pointed at it starts failing, and the connection's stored cloud credentials are gone -- reconnecting means pasting them again. WHETHER ANYTHING IN THE BUCKET ITSELF IS TOUCHED IS UNMEASURED: no Claid credential existed when this integration shipped, and the vendor's own sources do not say. Treat it as removing the connection, and confirm with List connected storages rather than trusting the reply. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Read the state of a job started by Start an AI edit of an image, and its generated images once it has finished. A POLL, not a new job: it costs no credits and returns whatever state the task is in. The ledger's response component is a `$ref` into a schema section the sealed sources did not carry, so the exact status vocabulary and the polling interval are UNMEASURED -- read the reply's own status field rather than assuming one this build could not observe. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Read the state of a shoot started by Start an AI fashion-model shoot, and its generated images once it has finished. A POLL, not a new job: it costs no credits and returns whatever state the task is in. The ledger's response component is a `$ref` into a schema section the sealed sources did not carry, so the exact status vocabulary and the polling interval are UNMEASURED -- read the reply's own status field rather than assuming one this build could not observe. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Read the state of a job started by Edit an image asynchronously, and its output once the job has finished. A POLL, not a new job: it costs no credits and returns whatever state the task is in. The ledger's response component is a `$ref` into a schema section the sealed sources did not carry, so the exact status vocabulary and the polling interval are UNMEASURED -- read the reply's own status field rather than assuming one this build could not observe. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Read the state of a job started by Edit a batch of images, and its outputs once the batch has finished. A POLL, not a new job: it costs no credits and returns whatever state the task is in. The ledger's response component is a `$ref` into a schema section the sealed sources did not carry, so the exact status vocabulary and the polling interval are UNMEASURED -- read the reply's own status field rather than assuming one this build could not observe. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

The storage back ends Claid can connect to, which is also the vocabulary for the `type` member of Connect a storage -- read it before writing that call rather than guessing a name. IT IS ALSO THIS INTEGRATION'S CREDENTIAL CHECK: it is the only parameter-free, side-effect-free, credit-free read on the whole surface, so the connect form and the hosted paste page probe it. IF A KEY YOU BELIEVE IS GOOD IS REFUSED AT THE PASTE BOX, suspect the permission split before the key: this is a /v1/storage/* route, and whether an Image-editing-only key reaches it is UNMEASURED -- no Claid credential existed when this integration shipped. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Every storage this Claid account has connected, with the id the other storage tools take. This is where a `storage_id` comes from. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

One connected storage in full, by the id List connected storages returns. Read it before Update a connected storage, which sends only the members named. The reply is scrubbed the same way Connect a storage's is: `secret_access_key`, `secret_key`, `private_key`, `service_account_key` and `credentials` are replaced at every depth. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Read the state of a job started by Start a video generation, and the video once it has finished. A POLL, not a new job: it costs no credits and returns whatever state the task is in. The ledger's response component is a `$ref` into a schema section the sealed sources did not carry, so the exact status vocabulary and the polling interval are UNMEASURED -- read the reply's own status field rather than assuming one this build could not observe. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Change a connected storage's name, type or parameters. NO MEMBER IS REQUIRED -- send only what is changing, and read the record first with Get a connected storage, because this replaces the members it names rather than merging into them. Rotating a bucket credential is this call with a fresh `parameters`. The reply is scrubbed the same way Connect a storage's is. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Hand an image to Claid's generative editing model with `options` describing what to change. Accepted as a background job: the reply carries the AI EDIT ID, read back with Read an AI edit's result. Generative, so the same request twice does not give the same picture twice. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Generate on-model photography for a garment: `input` names the model and clothing images, `options` customises the shoot. Accepted as a background job -- the reply carries the PROCESSING REQUEST ID, read back with Read an AI fashion-model result. THE OUTPUT IS A SYNTHETIC HUMAN LIKENESS: it is generated, not photographed, and publishing it as a real person's image is the caller's decision rather than this integration's. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Run Claid's editing pipeline over one image and WAIT for the finished result: restoration and upscaling, background removal or generation, object alignment and padding, colour and lighting adjustment, resizing and format conversion -- whichever of those the `operations` object asks for. SYNCHRONOUS, so a heavy pipeline holds the request open; use Edit an image asynchronously for a long job and Edit a batch of images for a folder. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

The same editing pipeline as Edit an image, accepted as a background job: the reply carries the TASK ID to poll, not an image. Read it back with Read an asynchronous edit's result. Use this when the pipeline is heavy enough that a synchronous call would time out. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Run one editing pipeline over MANY images: `input` is a folder URL, a single image URL, an array of image URLs, or the vendor's batch-input object. Accepted as a background job -- the reply carries the batch task id, read back with Read a batch edit's result. A batch spends credits PER IMAGE, so a folder is the fastest way to spend an account's balance. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Generate images from a text prompt (3 to 1024 characters). `options` carries the generation knobs -- the vendor's own defaults are four images at guidance scale 5, so an unspecified call bills for FOUR pictures rather than one. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Place a product into a generated scene: `object` says how the product sits in the frame (absolute placement, original, or padded) and `scene` says what it sits in (a background effect, a text prompt, or a template). The vendor's default output is FOUR images at 1MP, so an unspecified call bills for four. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. Note for whoever reads the research: the endpoint ledger files this one under an `image_generation` scope, which is not a permission Claid's dashboard can mint -- the key permissions are Storage, Image editing and Admin -- so it is granted here under Image editing, the permission the vendor's own authentication page puts the /v1/scene/* routes behind. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Wire one of the customer's own buckets into Claid so edited images can be written straight to it: `name` is the label inside Claid (it need not match the bucket's global name), `type` is one of the values List the storage connector types returns, and `parameters` carries that back end's own settings. THE BODY CARRIES THE CUSTOMER'S OWN CLOUD CREDENTIALS -- an S3 access key pair or a Google service account -- which is what this operation is for; they go to Claid and to nowhere else, and Agentic Fabriq never logs a request body. The REPLY is scrubbed before it reaches the caller: `secret_access_key`, `secret_key`, `private_key`, `service_account_key` and `credentials` are replaced at every depth, because a tool result is copied into the model's context and into the audit trail. Whether Claid echoes any of them is unmeasured -- the response component is a `$ref` the sealed sources did not carry -- so the scrub is a precaution keyed on AWS's and Google's own field names, and it is inert if Claid returns none of them. NEEDS THE STORAGE KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so an Image-editing-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Storage instead. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.

Animate a still image into a video, with `options` describing the motion. Accepted as a background job -- the reply carries the ANIMATION ID, read back with Read a generated video's result. Video is the most expensive thing on this API. With `output` omitted Claid keeps the result on its own bucket and returns a TEMPORARY URL that stops working after one day; pass an output URL (or a connected storage) to keep it. THIS SPENDS CLAID CREDITS: credits, not the request rate, are the real budget on this provider, a new account is given 50, and every image, scene and video operation draws on them. Reading a result back does not. The published costs are PER OPERATION and are not uniform -- 1 credit for text-to-image, 2 for an AI edit, 35 for five seconds of AI video -- so one video call spends most of a new account's balance and a batch spends per image. API credits are also a separate pool from web-plan credits and the two are not interchangeable. NEEDS THE IMAGE EDITING KEY PERMISSION (Admin grants both). A Claid API key carries Storage, Image editing or both, chosen when the key is minted in the Claid dashboard and changeable afterwards at API keys -> Edit key -- so a Storage-only key is refused here while remaining a perfectly valid key, and re-pasting it will not help. Mint or edit the key with Image editing instead. The endpoint ledger files this one under a `video_generation` scope, which is not a permission Claid's dashboard can mint; it is granted here under Image editing for the same reason the scene tool is. Claid reports a failure as `{"error_code", "error_type", "error_message", "error_details"}`. Measured credential-free 2026-09-26 and re-measured 2026-09-27: `Authorization: Bearer <bogus>` answers 401 error_code 108 "Could not validate credentials." while NO Authorization header answers 401 error_code 111 "Authorization is required." -- two different bodies, so a key Claid read and refused is distinguishable from one that never arrived. An unknown path answers 404 error_code 2005 and a wrong verb answers 405 {"detail":"Method Not Allowed"} BEFORE authentication, so a 401 here is a verdict on the credential rather than an unmounted route. Claid allows 120 requests a minute and 4 a second by default; image processing replies carry `RateLimit-Limit`, `RateLimit-Remaining` and `RateLimit-Reset`, and a 429 means the limit rather than the key.