REST API

The same ability model can be exposed over REST for integrations that do not use MCP. The base URL is /wp-json/wp-abilities/v1/.

List all abilities#

text

GET /wp-json/wp-abilities/v1/abilities

# Response includes schema, description, and permissions for each ability

Get ability schema#

text

GET /wp-json/wp-abilities/v1/abilities/{ability_id}

# Example:
GET /wp-json/wp-abilities/v1/abilities/accelerate%2Fget-performance-summary

Run an ability#

text

POST /wp-json/wp-abilities/v1/abilities/{ability_id}/run
Content-Type: application/json

{
  "input": {
    "param1": "value1",
    "param2": "value2"
  }
}

MCP endpoint#

For MCP clients, use the dedicated endpoint:

text

GET /wp-json/wp-abilities/v1/mcp

# Returns MCP-formatted tool list compatible with Claude Desktop

Response expectations#

Responses should be structured, typed, and scoped to the requested ability. Avoid parsing dashboard HTML or relying on visual labels when a named ability exists.

When to prefer REST#

Server-to-server automation.
Custom dashboards.
Back-office reporting tools.
Integrations where MCP is not available or not desirable.