Authenticate the Creator API

Creator API manages models controlled by the authenticated Creator. It uses a separate credential namespace from Providers and inference. Start from the Creator workspace that owns the collection.

Create credentials#

1. Open Creator in Console and select the correct workspace.
2. Enable Creator Remote Access and create a named access token.
3. Save the creator UUID and token securely.
4. Send HTTP Basic with the creator UUID as username and the creator access token as password.

curl --fail-with-body --request GET \
  "https://api.shareai.now/api/v1/console/creator" \
  -u "$CREATOR_UUID:$CREATOR_ACCESS_TOKEN"

import json
import os
import urllib.request
import base64

credentials = os.environ["CREATOR_UUID"] + ":" + os.environ["CREATOR_ACCESS_TOKEN"]
headers = {"Authorization": "Basic " + base64.b64encode(credentials.encode()).decode()}
request = urllib.request.Request('https://api.shareai.now/api/v1/console/creator', headers=headers, method='GET')
with urllib.request.urlopen(request, timeout=60) as response:
    print(json.load(response))

const url = "https://api.shareai.now/api/v1/console/creator";
const credentials = `${process.env.CREATOR_UUID}:${process.env.CREATOR_ACCESS_TOKEN}`;
const headers: Record = {
  Authorization: `Basic ${Buffer.from(credentials).toString("base64")}`,
};
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
console.log(await response.json());

Scopes#

Creating a complete model package requires both collection-write and model-write scopes. Required scopes are checked in addition to Creator ownership and program permissions.

Access is not publication approval#

A valid write token does not approve a collection or unlock an unsupported commercial method. Keep draft, pending review and accepted states separate. The current remote-token route map does not establish a supported token-based submit-review flow; submit review through Console.

Rotate or revoke#

Use distinct named credentials for separate integrations. Revoke credentials that are no longer needed and update your secret store when issuing a replacement. Never distribute a Creator token with a downloadable model package.