# Allay Therapeutics > Clinical-stage biopharmaceutical company (San Jose, CA and Singapore) developing ultra-sustained, > non-opioid analgesic products for post-surgical pain management. Its platform is a tunable > drug-biopolymer architecture that pairs validated non-opioid analgesics with dissolvable > biopolymers to release relief at a targeted surgical site over weeks rather than days. Lead > candidate ATX-101 is a bupivacaine-based implant for total knee replacement, holding FDA > Breakthrough Therapy Designation and in a pivotal Phase 2b registration trial. Allay Therapeutics is a therapeutics developer, not a software company. It runs **no developer program**: no developer portal, no API documentation, no SDKs, no CLI, no webhooks, no MCP server, no A2A agent card, no status page and no sandbox. The only machine-readable interface reachable without credentials is the WordPress REST content API behind the marketing site, catalogued below. This file was generated by API Evangelist from the public surface at www.allaytx.com on 2026-08-06. Allay Therapeutics does not publish an llms.txt of its own (`/llms.txt` returned 404). ## APIs - [Allay Therapeutics Content API](https://www.allaytx.com/wp-json): the anonymously readable WordPress REST API behind www.allaytx.com — 19 news posts (2021-05-13 to 2025-06-05), 9 corporate pages, 4 news categories, cross-content search, type/taxonomy/status discovery, and the oEmbed 1.0 provider endpoint. Read-only, no credentials, page-number pagination with X-WP-Total headers. - [WordPress REST API handbook](https://developer.wordpress.org/rest-api/): the upstream contract that defines the `wp/v2` namespace. Allay Therapeutics publishes no reference of its own. ## Specs - [OpenAPI 3.1 (derived)](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/openapi/allay-therapeutics-content-openapi.yml): 20 anonymously verified GET operations derived from the live /wp-json route index. Not a provider publication. - [Overlay](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/overlays/allay-therapeutics-content-overlay.yaml): the API Evangelist enhancements layered on the derived spec. - [Authentication profile](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/authentication/allay-therapeutics-authentication.yml): no security schemes; open read surface. - [Conventions](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/conventions/allay-therapeutics-conventions.yml): pagination, field selection, caching, error envelope. No idempotency contract, no rate-limit signalling. - [Error catalog](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/errors/allay-therapeutics-problem-types.yml): the WordPress error envelope `{code, message, data:{status}}`. Not RFC 9457. - [Data model](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/data-model/allay-therapeutics-data-model.yml): Post, Page, Attachment, Term, SearchResult, PostType, Taxonomy, PostStatus and their relationships. - [Lifecycle](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/lifecycle/allay-therapeutics-lifecycle.yml): no versioning policy, no deprecation policy, no SLA, no status page. - [Conformance](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/conformance/allay-therapeutics-conformance.yml): standards asserted and refuted, each with evidence. - [Well-known index](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/well-known/allay-therapeutics-well-known.yml): every /.well-known/ path probed returned 404. - [Domain security](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/security/allay-therapeutics-domain-security.yml): TLS 1.3, HSTS max-age 63072000, SPF and DMARC (p=quarantine) present; no DNSSEC, no CAA. ## Agent skills - [Track press releases](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/skills/allay-therapeutics-track-press-releases.md) - [Read the pipeline and science pages](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/skills/allay-therapeutics-read-pipeline-and-science.md) - [Search content and resolve a hit](https://raw.githubusercontent.com/api-evangelist/allay-therapeutics/refs/heads/main/skills/allay-therapeutics-search-and-resolve.md) ## Company - [Home](https://www.allaytx.com/) - [About Us](https://www.allaytx.com/about-us/) - [Our Science](https://www.allaytx.com/our-science/): the tunable drug-biopolymer delivery platform. - [Pipeline](https://www.allaytx.com/pipeline/): ATX-101, ATX-201, ATX-301, ATX-401, ATX-501. - [News](https://www.allaytx.com/news/) - [Careers](https://www.allaytx.com/careers/) - [Contact Us](https://www.allaytx.com/contact-us/): San Jose, CA and Singapore offices; contact@allaytx.com. - [Privacy Notices](https://www.allaytx.com/privacy-policy/) - [Terms of Service](https://www.allaytx.com/terms-of-service/) - [LinkedIn](https://www.linkedin.com/company/allaytx/) ## Not published The following were probed on 2026-08-06 and do not exist. Do not look for them again: - `/openapi.json`, `/swagger.json`, `/api-docs`, `/graphql` — 404 (HTML) - `/.well-known/security.txt`, `/.well-known/openid-configuration`, `/.well-known/oauth-authorization-server`, `/.well-known/api-catalog`, `/.well-known/ai-plugin.json` — 404 - `/.well-known/agent-card.json`, `/.well-known/agent.json` — 404, so no A2A agent card - `api.allaytx.com`, `developer.allaytx.com`, `docs.allaytx.com`, `trust.allaytx.com`, `status.allaytx.com` — NXDOMAIN - No GitHub organization (`api.github.com/orgs/allaytx` and `/allay-therapeutics` both 404) - No npm / PyPI / Maven / NuGet / RubyGems / crates.io first-party client library - No MCP server; the `wp-abilities/v1` capability registry returns 401 anonymously