Nusano · Authentication Profile

Nusano Authentication

Authentication

Nusano secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyRadioisotopesNuclear MedicineLife SciencesHealthcareOncologyRadiopharmaceuticalsPhysicsAdvanced ManufacturingNuclear EnergyHALEUCritical MineralsContent
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

applicationPassword http
scheme: basic

Source

Authentication Profile

Raw ↑
generated: '2026-08-26'
method: derived
source: openapi/nusano-categories-api-openapi.yml, openapi/nusano-comments-api-openapi.yml, openapi/nusano-discovery-api-openapi.yml,
  openapi/nusano-media-api-openapi.yml, openapi/nusano-pages-api-openapi.yml, openapi/nusano-posts-api-openapi.yml,
  openapi/nusano-search-api-openapi.yml, openapi/nusano-tags-api-openapi.yml, openapi/nusano-users-api-openapi.yml
summary:
  types:
  - http
schemes:
- name: applicationPassword
  type: http
  scheme: basic
  description: WordPress Application Passwords over HTTP Basic. Anonymous read is permitted on these routes;
    every write requires credentials.
  sources:
  - openapi/nusano-categories-api-openapi.yml
  - openapi/nusano-comments-api-openapi.yml
  - openapi/nusano-discovery-api-openapi.yml
  - openapi/nusano-media-api-openapi.yml
  - openapi/nusano-pages-api-openapi.yml
  - openapi/nusano-posts-api-openapi.yml
  - openapi/nusano-search-api-openapi.yml
  - openapi/nusano-tags-api-openapi.yml
  - openapi/nusano-users-api-openapi.yml
note: 'Nusano publishes no authentication documentation — there is no developer portal on nusano.com.
  This profile was DERIVED from the specs in openapi/, which were themselves derived from the live WordPress
  route index. It was then confirmed against live probes: anonymous GET on the wp/v2 content collections
  returns 200, and every write plus the MCP and abilities endpoints return 401 with the WordPress rest_forbidden
  envelope.'
anonymous_read: true
authorization_endpoint: https://nusano.com/wp-admin/authorize-application.php
authorization_endpoint_source: https://nusano.com/wp-json/ (authentication.application-passwords.endpoints.authorization)
self_service_signup: false
probes:
- url: https://nusano.com/wp-json/wp/v2/posts?per_page=1
  method: GET
  auth: none
  status: 200
- url: https://nusano.com/wp-json/wp/v2/settings
  method: GET
  auth: none
  status: 401
  code: rest_forbidden
- url: https://nusano.com/wp-json/mcp/mcp-adapter-default-server
  method: POST tools/list
  auth: none
  status: 401
  code: rest_forbidden
- url: https://nusano.com/.well-known/openid-configuration
  method: GET
  auth: none
  status: 404
- url: https://nusano.com/.well-known/oauth-authorization-server
  method: GET
  auth: none
  status: 404
oauth:
  supported: false
  note: No OAuth or OIDC metadata is served; no scopes/ artifact is emitted.

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.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/nusano-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 email required.

A second provider on the same verified email joins the account you already have.