litespeed/list-settings-areas lists every settings area this suite can read or write, with the option keys each area owns and the ability that writes it.
It is the discovery call. Rather than guessing which of a dozen update abilities owns a given option, call this once and read the mapping.
At a glance
| Ability | litespeed/list-settings-areas |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Toolbox |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
LiteSpeed has several hundred options, and this suite divides the writable ones into areas — cache, purge, optimisation, media, crawler, object cache, advanced. Each key belongs to exactly one area, and each area has exactly one ability that writes it.
That structure is clean and completely opaque from outside. Knowing you want to change optm-js_defer does not tell you whether that lives in the JS area, the tuning area or the general optimisation area.
So this returns the map: area, keys, writing ability. One call, and every subsequent write goes to the right place first time.
It also marks the keys this suite will not write. Some LiteSpeed options are deliberately out of scope — anything that spends QUIC.cloud credits, anything whose correct value is a business decision — and seeing that here is better than discovering it in a refusal.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
areas | array | One entry per area: its name, the option keys it owns, and the ability that writes it. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Which ability do I use to change a given LiteSpeed setting?
It resolves to one call:
{
"ability": "litespeed/list-settings-areas",
"parameters": {}
}Worth knowing
- Each key belongs to exactly one area and one writing ability.
- Keys this suite will not write are marked as such.
- The call to make first when working with an unfamiliar setting.
Related abilities
- Get Cache Settings — the largest area
- Export Settings — the whole configuration at once
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category