LIVEKINDLY · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the LIVEKINDLY Content API

10 actions 10 updates documentation extends openapi/livekindly-content-openapi.yml
Derived by API Evangelist Built from the contracts LIVEKINDLY publishes. LIVEKINDLY did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

summaryx-item-count-observeddescriptionx-thin-registrationx-apievangelist-profilex-provider-published-specx-derivation-basisx-agent-readiness-notes

Targets 9

$.info
$.paths['/wp/v2/brand'].get
$.paths['/wp/v2/partner'].get
$.paths['/wp/v2/job'].get
$.paths['/wp/v2/posts'].get
$.paths['/wp/v2/media'].get
$.paths['/wp/v2/pages'].get
$.paths['/wp/v2/users'].get
$.components.securitySchemes

OpenAPI Overlay

livekindly-content-overlay.yaml Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the LIVEKINDLY Content API
  version: 1.0.0
extends: openapi/livekindly-content-openapi.yml
x-generated: '2026-08-04'
x-method: generated
x-source: >-
  API Evangelist enrichment pipeline. Captures the annotations API Evangelist adds on top of the
  definition derived from https://thelivekindlyco.com/wp-json/ — the original derived document is
  never mutated.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/provider/livekindly/
    x-provider-published-spec: false
    x-derivation-basis: WordPress REST route-discovery document
    x-agent-readiness-notes: >-
      Anonymous read on every content collection, page/per_page pagination with X-WP-Total
      headers, and a well-formed RFC 9728 bearer challenge on the MCP endpoint. Against that:
      no idempotency contract, no rate-limit signalling, no request id, no conditional requests,
      no RFC 9457 errors, and a WAF that can replace the JSON envelope with an HTML block page.
- target: $.info
  update:
    x-artifacts:
      conventions: conventions/livekindly-conventions.yml
      errors: errors/livekindly-problem-types.yml
      data_model: data-model/livekindly-data-model.yml
      examples: examples/livekindly-examples.yml
      authentication: authentication/livekindly-authentication.yml
      lifecycle: lifecycle/livekindly-lifecycle.yml
      agentic_access: agentic-access/livekindly-agentic-access.yml
      skills: skills/_index.yml
- target: $.paths['/wp/v2/brand'].get
  update:
    summary: List LIVEKINDLY Collective brands
    description: >-
      Returns the Collective's operating brands. Four are published: Fry's Family Food Co., Like
      Meat, Oumph! and The No Meat Company. The custom post type is registered without content,
      excerpt or featured media, so each item carries only title, slug, link and SEO metadata.
    x-item-count-observed: 4
    x-thin-registration: true
- target: $.paths['/wp/v2/partner'].get
  update:
    summary: List LIVEKINDLY Collective partners
    description: >-
      Returns the Collective's manufacturing and distribution partners. Four are published: PHW
      Group, RCL Foods, Ospelt and Coest. Same thin registration as brand.
    x-item-count-observed: 4
    x-thin-registration: true
- target: $.paths['/wp/v2/job'].get
  update:
    summary: List open roles at LIVEKINDLY Collective
    description: >-
      Returns published job listings — six at time of profiling. No location, department,
      employment type or salary field is exposed; the role body lives only on the HTML page at
      `link`.
    x-item-count-observed: 6
    x-thin-registration: true
- target: $.paths['/wp/v2/posts'].get
  update:
    summary: List newsroom releases and LiveKindly Blog articles
    description: >-
      The richest collection in the API — full rendered content, categories, author and featured
      media. 39 posts published, most recent 2026-06-09.
    x-item-count-observed: 39
- target: $.paths['/wp/v2/media'].get
  update:
    summary: List media library assets
    description: >-
      1,145 attachments — product photography, brand assets and newsroom imagery, with populated
      alt_text, caption and the full generated size set in media_details.
    x-item-count-observed: 1145
- target: $.paths['/wp/v2/pages'].get
  update:
    summary: List corporate pages
    x-item-count-observed: 19
- target: $.paths['/wp/v2/users'].get
  update:
    x-edge-blocked: true
    x-edge-block-note: >-
      Returns HTTP 403 with a Sucuri WAF HTML interstitial (Block ID UAT007) rather than the
      WordPress JSON error envelope. Author enumeration is not available anonymously.
- target: $.components.securitySchemes
  update:
    mcpOAuth:
      type: oauth2
      description: >-
        Not used by wp/v2. Documented here because the same host runs an OAuth-protected MCP
        server discovered at /.well-known/oauth-authorization-server. See
        scopes/livekindly-scopes.yml.
      flows:
        authorizationCode:
          authorizationUrl: https://thelivekindlyco.com/oauth/authorize
          tokenUrl: https://thelivekindlyco.com/oauth/token
          refreshUrl: https://thelivekindlyco.com/oauth/token
          scopes:
            mcp: The single scope the LIVEKINDLY authorization server advertises.

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/livekindly-content-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.