Astell Actions FAQs
Plans, billing, and costs for Astell Actions, and how actions work from Claude or ChatGPT.
Which plans include Astell Actions?
Astell Actions are available to paid users only: Tree, Grove, and Forest. Not available on Sapling. Usage is subject to the token limit of your plan.
How are Astell Actions billed?
Per action, in tokens. Each action consumes tokens from your organization's monthly pool, the same pool that covers chat and Processed Data ingestion. Pricing is identical no matter where you trigger the action: from chat or from the Loops dashboard.
Do actions on Exacto cost more?
Yes. Actions can run on either model (Fast or Exacto), and an action on Exacto consumes more tokens than the same action on Fast. Higher-volume needs are best served by Grove or Forest, where the token pool is larger.
Why isn't there a per-action price chart?
The cost of an action depends on the underlying LLM call: context size, response length, and complexity all factor in, and model responses are inherently variable. A fixed chart would go stale immediately, so actions are metered in tokens instead.
Can I trigger an Astell Action from Claude or ChatGPT?
Not directly. Inside Claude or ChatGPT, Astell supplies context via MCP; any action you ask for runs through that assistant's own connectors for those tools. The benefit Astell brings is grounding: the assistant acts on pre-ingested company data instead of whatever its connectors can fetch live, which means better drafts and fewer wrong guesses.
Can Astell call my tools' own MCP servers?
Yes. Once an integration with an MCP server is linked to the workspace, Astell chat can call it, with a confirmation card before every call and the same role rules as Astell Actions for writes. Pause or resume a server's tools from its integration card under Workspace settings → Integrations. See MCP servers in Astell chat.