How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Local Infusion WordPress Abilities API

WordPress Abilities API — the named-ability registry the MCP adapter projects tools from. Routes are advertised in the public discovery document but read access is capability-gated (/wp-json/wp-abilities/v1/abilities returned HTTP 401 anonymously on 2026-08-25).

Local Infusion WordPress Abilities API is one of 5 APIs that Local Infusion publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include wp-abilities/v1. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://mylocalinfusion.com.

10 operations 6 paths 1 schemas 1 DELETE6 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://mylocalinfusion.com/wp-json/
Authentication
OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 2

Local Infusion WordPress Abilities API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (mcpOAuth2) using the authorizationCode flow, exposing 1 scope. An API key is passed in the header as X-WP-Nonce (wpNonce).

  • mcpOAuth2 — OAuth 2.1 authorization-code + PKCE (S256), as advertised by the provider's RFC 8414 metadata at https://mylocalinfusion.com/.well-known/oauth-authorization-se…
  • wpNonce — WordPress cookie-authentication nonce. Advertised by the live server in its Access-Control-Allow-Headers response header (Authorization, X-WP-Nonce, Content-Di…

Paths & Operations 10

Across 6 paths, the API surfaces 10 operations — 1 DELETE, 6 GET, 1 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

wp-abilities/v1 10

WordPress Abilities API — registry of named abilities an agent may discover and run. Read access is capability-gated (observed HTTP 401 anonymously on 2026-08-25).

GET
/wp-json/wp-abilities/v1
GET /wp-abilities/v1
getWpAbilitiesV1 2 params → 200401404
GET
/wp-json/wp-abilities/v1/abilities
GET /wp-abilities/v1/abilities
getWpAbilitiesV1Abilities 6 params → 200401404
GET
/wp-json/wp-abilities/v1/abilities/{name}
GET /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+)
getWpAbilitiesV1AbilitiesByName 1 param → 200401404
GET
/wp-json/wp-abilities/v1/abilities/{name}/run
GET /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+?)/run
getWpAbilitiesV1AbilitiesByNameRun 2 params → 200401404
POST
/wp-json/wp-abilities/v1/abilities/{name}/run
POST /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+?)/run
postWpAbilitiesV1AbilitiesByNameRun 1 param body → 200401404
PUT
/wp-json/wp-abilities/v1/abilities/{name}/run
PUT /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+?)/run
putWpAbilitiesV1AbilitiesByNameRun 1 param body → 200401404
PATCH
/wp-json/wp-abilities/v1/abilities/{name}/run
PATCH /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+?)/run
patchWpAbilitiesV1AbilitiesByNameRun 1 param body → 200401404
DELETE
/wp-json/wp-abilities/v1/abilities/{name}/run
DELETE /wp-abilities/v1/abilities/(?P [a-zA-Z0-9\-\/]+?)/run
deleteWpAbilitiesV1AbilitiesByNameRun 2 params → 200401404
GET
/wp-json/wp-abilities/v1/categories
GET /wp-abilities/v1/categories
getWpAbilitiesV1Categories 3 params → 200401404
GET
/wp-json/wp-abilities/v1/categories/{slug}
GET /wp-abilities/v1/categories/(?P [a-z0-9]+(?:-[a-z0-9]+))
getWpAbilitiesV1CategoriesBySlug 1 param → 200401404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WPError (3 properties). Each schema is shown below with its type and property counts.

WPError
object
The WordPress REST API error envelope, observed verbatim on live 401 responses from this host. Not RFC 9457 problem+json.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

local-infusion-wp-abilities-v1-api-openapi.yml Raw ↑

Other APIs Local Infusion publishes across the network.

Local Infusion WordPress Content API
Local Infusion MCP API
Local Infusion WordPress Root API
Local Infusion oEmbed API
Where this information came from

This is an independent, third-party profile of Local Infusion WordPress Abilities API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.