Quickstart
ACR DashboardGet your ACR key, install the SDK, and read your Creator Plan.
Connect your backend to Kallfi in three steps.
Get your ACR key
Open your ACR account and reveal your key. Basic Account access does not require an Enterprise application.
Save the key in your server environment:
export KALLFI_RED_ACR_KEY="<your ACR key>"Keep your key private
Store keys in your server secret manager. Never include them in browser code, chat messages or a repository. Use the key issued for this surface.
Install the SDK
npm install @kallfi/sdk@latestKeep the resolved version in your application's lockfile.
Read your Creator Plan
Run the example on your server. It reads your existing plan without starting paid work.
import { randomUUID } from "node:crypto";
import { Kallfi } from "@kallfi/sdk";
const apiKey = process.env.KALLFI_RED_ACR_KEY;
if (!apiKey) throw new Error("Set KALLFI_RED_ACR_KEY on your server.");
const client = new Kallfi({
apiKey,
baseUrl: "https://acr.kallfi.red",
});
const result = await client.operation(
"getAccountCreatorPlan",
{ body: { query: {}, body: {} } },
{ idempotencyKey: randomUUID() },
);
console.log(result.data);Account read actions use the same UUID transport key as other Account commands. For mutations, retain one key for each intended action and reuse it when retrying that action.
Explore the ACR reference for Soul creation, content generation and operation status. Each action requires its current permissions, safety checks and available balance. Follow asynchronous work to its completed result.
To connect an AI client instead, follow MCP setup.
Following Account/workspace overhaul — source and proof boundaries
This section describes the reviewed following source candidate. It does not claim that its workspace schema, portal UI or runtime is installed on the currently serving deployment. Published packages and the separately verified hosted MCP Personal reads remain valid; explicit hosted Team requests currently fail closed until the matching workspace implementation is adopted.
Use the same Account surface key when navigating authorized workspaces; do not mint a key per organization. X-Kallfi-Workspace-ID is a strict optional UUID selector, not authority. Omission selects Personal. The shared SDK verifies same-origin capability support before every explicit workspace business request and never silently removes the selector. The 31 Account commands reject a nonpersonal selection; only the 7 organization-runtime operations support the matching adopted protocol. Current hosted MCP Team requests remain unsupported; Personal hosted reads are separately verified.
An authenticated, nonanonymous Account with a live public user may inspect its canonical Personal workspace metadata and its own application while an independent Account restriction remains active. accountAccess.state=restricted and executionAllowed=false describe Account eligibility; eligible does not establish workspace admission, entitlement or funding. Restricted UI presents Personal metadata, own application/status/history, documentation and support; execution pages are not loaded, key reveal/copy/replacement is not mounted, and application Save/Submit/Withdraw/successor controls are read-only. Server execution, key and recent-proof owners retain their strict eligibility checks.
The shared SDK rejects any explicitly configured workspace for Account-scoped methods, including a Personal UUID. The server Account command boundary independently requires the exact Personal mapping; a team selector cannot move an Account wallet action into an organization.