JenaValve Technology · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the JenaValve Discover AR Site API

6 actions 6 updates update extends openapi/jenavalve-technology-discover-ar-openapi.yml
Derived by API Evangelist Built from the contracts JenaValve Technology publishes. JenaValve Technology did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-notex-apievangelist-profilex-apievangelist-posturex-apievangelist-surfacex-apievangelist-provider-publishedx-apievangelist-probe-datex-conventionsx-authentication

Targets 4

$.info
$.paths['/wp/v2/categories'].get
$.paths['/wp/v2/posts'].get
$.paths['/yoast/v1/get_head'].get

OpenAPI Overlay

jenavalve-technology-discover-ar-overlay.yaml Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the JenaValve Discover AR Site API
  version: 1.0.0
extends: openapi/jenavalve-technology-discover-ar-openapi.yml
x-generated: '2026-08-04'
x-method: generated
x-source: API Evangelist enrichment pipeline.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/provider/jenavalve-technology
    x-apievangelist-posture: no-product-api
    x-apievangelist-surface: incidental-cms
    x-apievangelist-provider-published: false
    x-apievangelist-probe-date: '2026-08-04'
    x-apievangelist-note: >-
      Derived by API Evangelist from anonymous probing. JenaValve Technology does not publish,
      document or support this surface.
- target: $.info
  update:
    x-conventions: conventions/jenavalve-technology-conventions.yml
    x-authentication: authentication/jenavalve-technology-authentication.yml
    x-error-catalog: errors/jenavalve-technology-problem-types.yml
    x-data-model: data-model/jenavalve-technology-data-model.yml
    x-conformance: conformance/jenavalve-technology-conformance.yml
- target: $.info
  update:
    x-stability: unversioned-uncommitted
    x-related-host: https://jenavalve.com/wp-json
    x-related-note: >-
      A separate WordPress installation from jenavalve.com. The two share no identifier space —
      the same integer id means different things on each host.
- target: $.paths['/wp/v2/categories'].get
  update:
    x-apievangelist-recommended: true
    x-apievangelist-note: >-
      The most editorially meaningful endpoint across either JenaValve host. This taxonomy is
      purpose-built to segment the aortic-regurgitation education library by media format —
      articles (id 12), videos (id 13), presentations (id 14), audio (id 15) — so a consumer can
      retrieve, say, every AR audio item without scraping the resources page.
- target: $.paths['/wp/v2/posts'].get
  update:
    x-apievangelist-note: >-
      Pass ?categories=13 for videos, 12 for articles, 15 for audio. Counts as of 2026-08-04:
      videos 6, articles 4, audio 3, presentations 0.
- target: $.paths['/yoast/v1/get_head'].get
  update:
    x-apievangelist-note: >-
      Returns rendered head metadata including schema.org JSON-LD for any discover-ar.com URL —
      structured metadata for a library item without parsing the page HTML. Present on this host
      only; jenavalve.com does not run Yoast.

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/jenavalve-technology-discover-ar-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.