Option 1: write it by hand
Start from this example and replace every number with your own. Illustrative example. The figures are hypothetical, not a recommendation.position_size under a class, and short_position_size for shorts. For example, position_size: { max: 9 } caps one holding at 9% of the portfolio. The format reference explains both keys and what defaults apply.
Option 2: have an AI draft one
Give an AI assistant your own rules in plain language and ask it to produce rules text. The numbers below are a fictional example; use yours. A prompt like this is a starting point. Check what the assistant writes with a preview before you import it:draft_rules prompt. With no notes, its text asks the assistant to ask for your classes and ranges one at a time. Where your MCP client lists prompts depends on the client. See Claude and MCP.
Option 3: convert an existing investment policy statement
Paste your investment policy statement or spreadsheet to an AI assistant and ask it to convert the allocation ranges into rules text format. If a document splits a class (domestic and international equity, for example), choose whether to keep the parts as separate classes named as written, or combine them into one built-in class by adding their targets, minimums and maximums. A name that isn’t an exact match, such as Global Equities, becomes a new custom class. In an MCP client that lists prompts, thedraft_rules prompt takes the statement in its notes argument.
Checking the text
Before importing, callpreview_rules (MCP) or POST /scenarios/{id}/rules with dry_run: true (REST API) to validate the text against the spec and see what it would change, without touching your account.
Importing
1
Open the Edit as text tab
Pick the scenario in the top bar, then go to Allocation and open the Edit as text tab. The tab shows that scenario’s current rules as rules text you can copy or download.
2
Paste or upload your text
Choose Import, then drop a file or paste your rules text. Examples (Browse examples on a scenario with no rules yet) opens starting points with every number left blank, for you to fill in, then review and apply the same way.
3
Review the preview
Allocait shows every class that would change, be added, or be removed, with the old value next to the new one. Nothing is written yet.
4
Apply
Choose Apply changes. Allocait saves a restore point first, then confirms the update with an Undo button that stays for ten seconds. After that, the same point is listed under Restore points on the Edit as text tab. Restore sets the scenario’s rules back to that point and says which classes it could not restore. Allocait keeps the 20 newest restore points per account.
preview_rules returns the changes without writing, and apply_rules writes them and returns a restore point; restore_rules sets the rules back to that point and returns a new restore point. To change one class without a file, save_class_rule, which keeps every other rule and also saves a restore point. Applying needs Read and change access; see what each level of access allows.
Next steps
- Rules text format lists every key and default.
- Rules text explains the format and how an import works.
- Scenarios explains how imported rules text relates to the active scenario.
- Check before you trade tests a change against the rules you just imported.
- Rule tools lists the tools an agent uses.