Skip to content
ACS Infra
Looms

List Looms

GET
/v1/looms

List your Looms as Production does: the pinned ones first, then the others by their last change, newest first, at most 100, each with its name and prompt. Read a Loom for its Nodes.

Authorization

bearer
headerAuthorizationBearer <token>

An API key: Authorization: Bearer sk-acs-..., or a key of the old platform, acs-bm-.... A User makes and revokes keys in the App.

Response Body

LoomList

application/json
  1. response
object*"list"
Value in"list"
data*array<>

At most 100 Looms: the pinned ones first, newest pin first, then the others by their last change, newest first. A rename, a Branch and a deleted Node change a Loom; a pin does not.

Example Request
curl -X GET 'https://api.v2.infra.acsresearch.org/v1/looms' \  -H 'Authorization: Bearer <API_KEY>'
Example Response
{  "object": "list",  "data": [    {      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",      "object": "loom",      "created_at": 0,      "updated_at": 0,      "title": "string",      "pinned": true,      "prompt": "string"    }  ]}

Cancel Harvest DELETE

Cancel a pending or running harvest job, and stop its GPU run, also one that is still starting. A job that is running and whose GPU run started is charged the tokens it holds; any other cancel costs nothing. Answers the cancelled job, also for a second cancel.

Create Loom POST

Make a Loom. Its root Node is the prompt. A retry with the same `Idempotency-Key` answers the Loom as it is now, or 404 if it was deleted since.