CREDS are the user-facing unit for Barvinca write operations. The rule is deliberately simple: one Autodesk write mutation costs 1 CREDS.

The goal is to make quota visible without asking operators to understand every API call behind the workflow.

CREDS usage examples
0 CREDSRead users, projects, roles, and companies
0 CREDSRun dry-runs, setup checks, and previews
1 CREDSExecute one add, remove, or role-update row
12 CREDSAdd one user to twelve projects
25 CREDSUpdate one role across twenty-five projects
3 CREDSRetry three failed write rows

What costs CREDS

CREDS are used only when Barvinca submits write work to Autodesk. In Bulk User Manager, that means executed rows such as add user, remove user, or update role. If an operation contains 40 write rows, it needs 40 CREDS.

What does not cost CREDS

Discovery should be cheap. Listing users, syncing account data, checking setup, reviewing projects, preparing a changeset, and running a dry-run cost 0 CREDS. This keeps the safe behavior cheap: look first, write later.

Why not count operations instead?

One operation can contain one row or one hundred rows. Counting operations would hide the real blast radius. Counting CREDS makes the unit match the risk: each write row has a concrete effect in Autodesk.

Welcome and subscription bundles

New users receive 50 CREDS once, enough to run a small real batch after dry-run review. Paid subscriptions add monthly balances: 500 CREDS for $500/month, 2,500 CREDS for $2,500/month, or 10,000 CREDS for $10,000/month.

Rule: 1 Autodesk write mutation = 1 CREDS. Subscription pricing uses 1 CREDS = $1 USD. Reads, sync, setup checks, discovery, previews, and dry-runs cost 0 CREDS.