generated: '2026-08-07'
method: generated
source: openapi/bluejay-therapeutics-content-openapi.yml
note: >-
  Packaged Agent Skills for the Bluejay Therapeutics Content API, generated by the API Evangelist
  enrichment pipeline. Bluejay Therapeutics publishes no skills, no AGENTS.md and no agent guidance
  of its own — a search of the site and of the /wp-json/ route index found none. Every operationId
  referenced below exists verbatim in the OpenAPI and was individually verified against a live
  anonymous call on 2026-08-07 before being used in a step.
skills:
- file: bluejay-therapeutics-read-press-archive.md
  name: Read the Bluejay Therapeutics press and publication archive
  description: >-
    Retrieve, filter and read the 35 press releases and publication notices published between 2021
    and 2025, over the anonymous WordPress REST API that outlived the company's web site.
  api: openapi/bluejay-therapeutics-content-openapi.yml
  operations: [listPosts, getPost, listCategories, getCategory, listTags, search]
- file: bluejay-therapeutics-harvest-media-library.md
  name: Harvest the Bluejay Therapeutics media library
  description: >-
    Enumerate and fetch the 99 files in the media library — press-release PDFs, conference poster
    and presentation decks, and site imagery — and tie each file back to the post it belongs to.
  api: openapi/bluejay-therapeutics-content-openapi.yml
  operations: [listMedia, getMediaItem, listPosts, getPost, getOEmbed]

exclusions:
- surface: /wp/v2/users
  status: 200
  anonymous: true
  reason: personal-data
  detail: >-
    The users collection returns 200 anonymously and discloses five author records — display name,
    slug, author-archive URL, description and gravatar URLs — corresponding to the site
    administrator account and to outside investor-relations and communications agency staff. Under
    the API Evangelist enrichment PII guardrail no skill, tool or OpenAPI operation is emitted for
    it, and both skills above carry an explicit "do not call this" instruction, including a warning
    against `?_embed` because that parameter inlines author records into any response. The
    exposure itself is documented in conventions/bluejay-therapeutics-conventions.yml. This
    omission is DELIBERATE, not an oversight.
- surface: wp-abilities/v1
  status: 401
  reason: auth-gated
  detail: >-
    The site registers the WordPress Abilities API — the agent-facing capability registry, with
    /abilities, /abilities/{name}, /abilities/{name}/run and /categories routes. Every route
    returns 401 rest_forbidden anonymously, so there is no capability to package and none is
    claimed. Worth re-probing if the site's plugin configuration changes.
- surface: write operations
  reason: capability-gated
  detail: >-
    Every POST/PUT/PATCH/DELETE endpoint in the route index is gated by WordPress capability
    checks and reachable only with an Application Password issued from wp-admin, which no third
    party can obtain. This is a read-only surface and the skills reflect that.
- surface: /oembed/1.0/proxy
  status: 401
  reason: auth-gated

no_mcp_server:
  detail: >-
    No MCP server is emitted for this provider, and no candidate tool list is derived. The company
    was fully absorbed by Mirum Pharmaceuticals in January 2026, the content is frozen, and the
    surface has no deprecation policy or announced end of life. Publishing a candidate agent
    endpoint for a wound-down company's CMS would assert an agent posture that does not exist. The
    two skills above are grounded in verified operationIds and are sufficient.