openapi: 3.1.0 info: title: MOMA Therapeutics Search API version: wp/v2 summary: Anonymously readable WordPress REST content API behind momatx.com. description: The site-wide search surface of momatx.com. MOMA Therapeutics is a Cambridge, Massachusetts drug-discovery company building precision medicines against molecular machines — highly dynamic proteins that convert chemical energy into regulatory work such as protein transport and degradation — using its proprietary KNOMATIC platform. It runs no developer program and markets no product API. This document is an API Evangelist derivation of the WordPress REST route index MOMA Therapeutics publishes at https://momatx.com/wp-json/, restricted to the operations verified to return data anonymously on 2026-08-26. contact: name: MOMA Therapeutics url: https://momatx.com/ email: info@momatx.com x-api-evangelist-provenance: Derived by the API Evangelist enrichment pipeline from the live WordPress REST route index published at https://momatx.com/wp-json/ (219 routes across 12 namespaces) and verified against live anonymous responses on 2026-08-26. Every parameter below appears verbatim in that index's `args` for the endpoint, every schema property name was read from a real response body, and every collection count in a description was read from the `X-WP-Total` response header on that date. MOMA Therapeutics publishes no OpenAPI, no developer portal 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. The deployment is WP Engine (nginx), with Wordfence, Yoast SEO and Advanced Custom Fields registering additional namespaces. Routes that returned 401 anonymously (/wp/v2/users, /wp/v2/settings, /wp/v2/menu-items, /wp/v2/plugins, /wp/v2/themes and the entire wp-abilities/v1 namespace) are deliberately excluded, as are all write operations. Nothing here was obtained with credentials. servers: - url: https://momatx.com/wp-json description: Production WordPress REST content API tags: - name: search description: Cross-content search over every published object — posts, pages and team records. paths: /wp/v2/search: get: tags: - search operationId: search summary: Search published content description: Searches across published objects and returns lightweight hits (id, title, url, type, subtype). An unfiltered query returned 42 results on 2026-08-26 — the union of the 32 news posts, 9 pages and the searchable subset of `team`. Use `subtype` to restrict to `post`, `page` or `team`. parameters: - name: context in: query description: Scope under which the request is made; determines fields present in response. schema: type: string enum: - view - embed default: view - name: page in: query description: Current page of the collection. schema: type: integer default: 1 minimum: 1 - name: per_page in: query description: Maximum number of items to be returned in result set. schema: type: integer default: 10 minimum: 1 maximum: 100 - name: search in: query description: Limit results to those matching a string. schema: type: string - name: type in: query description: Limit results to items of an object type. schema: type: string enum: - post - term - post-format default: post - name: subtype in: query description: Limit results to items of one or more object subtypes. schema: type: array items: enum: - post - page - team - category - post_tag - team_types - any type: string default: any - name: exclude in: query description: Ensure result set excludes specific IDs. schema: type: array items: type: integer - name: include in: query description: Limit result set to specific IDs. schema: type: array items: type: integer responses: '200': description: A page of results. headers: X-WP-Total: description: Total number of matching items. schema: type: integer examples: - 42 X-WP-TotalPages: description: Total number of pages available at the current `per_page`. schema: type: integer Link: description: RFC 8288 pagination links (`rel="next"` / `rel="prev"`). schema: type: string content: application/json: schema: type: array items: $ref: '#/components/schemas/SearchResult' '400': $ref: '#/components/responses/BadRequest' components: schemas: Error: type: object description: The WordPress REST error envelope. It is NOT RFC 9457 `application/problem+json`; it is a bespoke JSON object served as `application/json`. required: - code - message - data properties: code: type: string description: Machine-readable error slug, e.g. `rest_post_invalid_id`. examples: - rest_no_route message: type: string description: Human-readable message. data: type: object properties: status: type: integer description: HTTP status code, repeated in the body. params: type: array items: type: string SearchResult: type: object description: A cross-content search hit. properties: id: type: integer title: type: string url: type: string format: uri type: type: string description: Search result object type, e.g. `post`. subtype: type: string description: The underlying post type, e.g. `post`, `page`, `team`. _links: type: object description: HAL-style `_links` relations WordPress emits for the object. additionalProperties: true responses: BadRequest: description: Invalid parameter. WordPress returns `rest_invalid_param` / `rest_missing_callback_param`. content: application/json: schema: $ref: '#/components/schemas/Error'