litespeed/purge-url purges specific URLs from the cache and leaves everything else alone.
It is the right call when one page is stale, which is most of the time.
At a glance
| Ability | litespeed/purge-url |
| Toolset | LiteSpeed Cache — toolset/litespeed |
| Group | LiteSpeed Cache › Purging |
| Requires | LiteSpeed Cache, active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
Most staleness is local. A page was edited outside WordPress, a widget on one template renders something dynamic, an external feed changed — and the response is almost always a full purge, which fixes the one page and discards several thousand others for nothing.
Purging by URL costs nothing beyond the pages named. The next visitor to those pages pays a rebuild; nobody else notices.
URLs are matched as LiteSpeed stores them, so the trailing slash and the scheme should match what the site actually serves. A URL that was never cached purges without error and without effect.
For a post, litespeed/purge-post is better than working out its URL — it handles the archive and taxonomy pages the post also appears on.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
urls | array | Yes | The URLs to purge. |
What comes back
| Name | Type | What it is |
|---|---|---|
purged | array | The URLs that were purged. |
count | integer | How many. |
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:
The pricing page is showing old content — clear just that page.
It resolves to one call:
{
"ability": "litespeed/purge-url",
"parameters": {
"urls": ["https://example.com/pricing/"]
}
}Worth knowing
- Match the URL form the site serves, trailing slash included.
- A URL that was not cached purges harmlessly.
- For a post, purge by ID instead — it covers the archives too.
- Idempotent.
Related abilities
- Purge Posts — covers the archives a post appears on
- Purge Cache — the broad version
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category