FactorAI

Core concepts

The nouns behind the product and how they relate.

FactorAI runs agents inside projects, and each team's usage is billed through one shared wallet. This page defines the nouns the rest of the docs use, then links to the pages that cover them in detail.

Team and project

A team owns billing, members, and API keys. A project belongs to a team and scopes the agents, chats, and Runs that work inside it, with its own membership list.

API key, capability, and action grant

An API key authenticates a request to the Developer API. Each key carries a capability level per family, with values such as none, read, or manage, that sets the broad access boundary. A mutation can also require an action grant, an exact action id that narrows what the key may attempt. Neither replaces the team or project permission policy, which is evaluated last and may deny the request or require approval.

See API keys to create one, and API overview for the capability levels and action grants.

Workflow, Run, and Attempt

A workflow is a persistent orchestrator that coordinates Runs toward an objective, including scheduled follow-up work. A Run is one independently dispatched unit of work with its own policy, budget, and history; standalone Runs do not require a workflow.

Every Run starts from an immutable Revision - its prompt, input, model, tools, and context - and executes as one or more Attempts. Each Attempt is one execution of that Revision and is resumable after an interruption; a retry creates a replacement Attempt on the same Revision, while a rerun dispatches a fresh Run.

See API overview for the workflow and Run endpoint families.

Chat

A chat is a long-lived interactive thread that a person starts. A chat turn can dispatch a Run when it needs structured work, and the conversation continues over the Run's result. Chats optimize for conversational continuity; Runs are dispatched by the system, including an approved chat tool call, a schedule, or an API request.

Wallet, grant, and entitlement

Billing uses one shared USD wallet. Grants - plan allowances, eligible daily FTAI, purchases, rewards, and adjustments - fund the wallet, and usage is debited from it. A plan's limits, such as allowed models, projects, seats, request rate, and sessions per day, are entitlements: they cap how you use the product and are not separate wallet lines.

See Billing wallet for balances, grant order, and consumption types.

Next steps

  • API overview - authentication, capabilities, action grants, and endpoint families
  • Command-line interface - install, authenticate, and automate the CLI
  • Billing - wallet, plans, usage, and consumption types