hosting
GET /v1/sites/{siteId}/wordpress/abilities
Our plugins' AI agent abilities on the site.
Authentication
Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/abilities \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The WordPress abilities Page Builder Sandwich, Tranzly, Zinn® Chat, Zinn® Cache and the Zinn® Reseller Toolkit register on this site (pages, sections, blocks, kits, design, translation, jobs, SEO, support tickets, caching, reseller clients and more; docs/901), read from the site itself through each plugin's own MCP server, run on the worker as the site's administrator. servers says which plugin answered: false when it is not installed, is older than the version with AI agents, or its "AI agents (MCP)" switch is off. ⛔ Fleet only (wp_cli). Requires sites.view and sites.panel_access.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
abilities | object[] | Yes | — |
servers | object | Yes | Plugin server id -> whether it answered. |
Errors this endpoint can return
401 · 403 · 404 · 422 · 429 · 503