openapi: 3.2.0
info:
title: BioAegis Therapeutics Content Oembed API
version: wp/v2
summary: Anonymously readable WordPress REST content API behind www.bioaegistherapeutics.com.
description: The read-only content surface BioAegis Therapeutics exposes at https://www.bioaegistherapeutics.com/wp-json. BioAegis Therapeutics is a privately held, clinical-stage biopharmaceutical company developing recombinant human plasma gelsolin (rhu-pGSN) for acute respiratory distress syndrome (BTI-203, Phase 2) and inflammasome-driven decompression sickness; it runs no developer program and markets no product API. This document is an API Evangelist derivation of the WordPress `wp/v2`, `oembed/1.0` and `yoast/v1` route index the site publishes at /wp-json/, restricted to the operations that were verified to return data anonymously on 2026-08-07. Write operations, `/wp/v2/users`, `/wp/v2/settings`, `/wp/v2/menus`, `/wp/v2/menu-locations`, `/wp/v2/sidebars`, `/wp/v2/widget-types`, `/wp/v2/themes`, `/wp/v2/plugins`, `/wp/v2/templates`, `/wp/v2/template-parts`, `/wp/v2/global-styles`, `/wp/v2/block-types`, `/wp/v2/block-patterns`, `/wp/v2/pattern-directory`, `/wp/v2/font-collections`, every `revisions` and `autosaves` sub-resource, the `oembed/1.0/proxy` endpoint, the `wp-abilities/v1` namespace, the `wp-site-health/v1` namespace, the `wp-block-editor/v1` namespace, the `redirection/v1` namespace, the `elementor*` namespaces, the `astra/v1` namespace, the `monsterinsights/v1` namespace, the `nps-survey/v1` namespace, the `duplicate-post/v1` namespace and the authenticated half of `yoast/v1` all require authentication (or return 404/500/502 anonymously) and are deliberately excluded — see x-api-evangelist-provenance.
contact:
name: BioAegis Therapeutics
url: https://www.bioaegistherapeutics.com/contact-us/
x-api-evangelist-provenance: Derived by the API Evangelist enrichment pipeline from the live WordPress REST route index at https://www.bioaegistherapeutics.com/wp-json/ (308 routes across the namespaces oembed/1.0, redirection/v1, yoast/v1, elementor-one/v1, duplicate-post/v1, elementor/v1, elementor-pro/v1, monsterinsights/v1, astra/v1, elementor/v1/documents, elementor-ai/v1, elementor/v1/feedback, nps-survey/v1, wp/v2, wp-site-health/v1, wp-block-editor/v1 and wp-abilities/v1) and verified against live anonymous responses on 2026-08-07. Every parameter below appears verbatim in the route index `args` for that endpoint, and every operation modelled here returned 200 without credentials. The site is fronted by a Sucuri CloudProxy WAF, which answers /wp/v2/users and /wp/v2/users/me with a 403 HTML interstitial instead of a JSON error — the only place on this surface where the error envelope is not JSON. BioAegis Therapeutics publishes no OpenAPI, no developer documentation and no API reference for this surface; the humanURL in apis.yml points at the upstream WordPress REST handbook that defines the wp/v2 contract. Nothing here was obtained with credentials.
license:
name: Site content is © BioAegis Therapeutics, Inc. — see Terms of Use
url: https://www.bioaegistherapeutics.com/terms-of-use/
servers:
- url: https://www.bioaegistherapeutics.com/wp-json
description: Production content API
tags:
- name: oembed
description: oEmbed 1.0 provider endpoint for bioaegistherapeutics.com URLs.
paths:
/oembed/1.0/embed:
get:
tags:
- oembed
operationId: getOembed
summary: Get an oEmbed response for a URL
description: The oEmbed 1.0 provider endpoint. Returns the oEmbed rich/link response for a bioaegistherapeutics.com URL. The sibling `/oembed/1.0/proxy` endpoint, which would fetch third-party URLs, returns 401 `rest_forbidden` anonymously.
parameters:
- name: url
in: query
required: true
description: The URL of the resource for which to fetch oEmbed data.
schema:
type: string
format: uri
examples:
- https://www.bioaegistherapeutics.com/
- name: format
in: query
description: The oEmbed format to use.
schema:
type: string
enum:
- json
- xml
default: json
- name: maxwidth
in: query
description: The maximum width of the embed frame in pixels.
schema:
type: integer
default: 600
responses:
'200':
description: oEmbed response
content:
application/json:
schema:
$ref: '#/components/schemas/OembedResponse'
'404':
$ref: '#/components/responses/NoRoute'
components:
schemas:
RestError:
type: object
description: The WordPress REST error envelope. This is NOT RFC 9457 problem+json — it is served as `application/json` with a `code`/`message`/`data.status` shape, and the HTTP status is duplicated inside `data.status`.
required:
- code
- message
- data
properties:
code:
type: string
description: Machine-readable error code.
examples:
- rest_post_invalid_id
message:
type: string
description: Human-readable message.
data:
type: object
properties:
status:
type: integer
description: HTTP status code, repeated in the body.
params:
type: object
description: Per-parameter validation messages, present on rest_invalid_param.
additionalProperties:
type: string
details:
type: object
description: Per-parameter structured validation detail, present on rest_invalid_param.
OembedResponse:
type: object
description: An oEmbed 1.0 response document.
properties:
version:
type: string
examples:
- '1.0'
provider_name:
type: string
examples:
- BioAegis Therapeutics
provider_url:
type: string
format: uri
author_name:
type: string
author_url:
type: string
format: uri
title:
type: string
type:
type: string
examples:
- rich
width:
type: integer
height:
type:
- integer
- 'null'
html:
type: string
responses:
NoRoute:
description: No route matched the requested path and method.
content:
application/json:
schema:
$ref: '#/components/schemas/RestError'
examples:
noRoute:
value:
code: rest_no_route
message: No route was found matching the URL and request method.
data:
status: 404