Alzheon · Authentication Profile
Alzheon Authentication
Authentication
Alzheon secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.
CompanyBiotechnologyPharmaceuticalsLife SciencesClinical TrialsAlzheimers DiseaseNeurologyDrug DevelopmentHealthcarePrivate Company
Methods: http
Schemes: 1
OAuth flows:
API key in:
Security Schemes
applicationPassword http
scheme: basic
Source
Authentication Profile
generated: '2026-07-31'
method: derived
source: >-
openapi/alzheon-content-openapi.yml, plus the authentication block of the live route index
at https://alzheon.com/wp-json/ and anonymous probes on 2026-07-31
note: >-
Alzheon publishes no authentication documentation — there was no docs page to search, so
this stays derived. The whole public surface is anonymous: no key is issued, no signup
exists, and the only declared scheme is closed in practice.
summary:
types:
- http
anonymous_read: true
credentials_issued_publicly: false
api_keys: false
oauth2: false
oidc: false
mtls: false
signup_url: null
schemes:
- name: applicationPassword
type: http
scheme: basic
rfc: RFC 7617
description: >-
WordPress application passwords (HTTP Basic — WordPress username plus a generated
application password). Advertised by the site's own route index under
authentication.application-passwords, with the authorization endpoint at
https://alzheon.com/wp-admin/authorize-application.php. Required only for write and
administrative routes, none of which are in the OpenAPI. Alzheon issues no public
credentials, so this scheme is declared but unreachable for third parties.
applies_to: write and administrative routes
reachable_by_third_parties: false
sources:
- openapi/alzheon-content-openapi.yml
- https://alzheon.com/wp-json/
anonymous_access:
applies_to: every operation in openapi/alzheon-content-openapi.yml
verified: '2026-07-31'
detail: >-
All read operations were probed without any credential and returned HTTP 200.
Administrative routes excluded from the spec return 401 with code rest_forbidden or
rest_cannot_view_plugins.
cors:
allow_headers: [Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type]
expose_headers: [X-WP-Total, X-WP-TotalPages, Link]
note: >-
X-WP-Nonce is the cookie-authenticated browser flow used by the site's own admin
screens; it is not available to third-party clients.
not_present:
- mechanism: api-key
evidence: no apiKey securityScheme; no key issuance or signup page exists
- mechanism: oauth2
evidence: /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource both 404
- mechanism: openIdConnect
evidence: /.well-known/openid-configuration returns 404
- mechanism: mutualTLS
evidence: no mTLS requirement observed
- mechanism: jwt
evidence: no JWT plugin namespace present in the route index
see_also:
scopes: null
conventions: conventions/alzheon-conventions.yml
domain_security: security/alzheon-domain-security.yml
well_known: well-known/alzheon-well-known.yml
Work with this as data
Every security artifact 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 security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact 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.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/alzheon-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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.