Nusano Discovery API
Type, taxonomy and status descriptors that describe the shape of the nusano.com content collections — the self-describing layer of the WordPress REST API.
Work with this as data
Every API 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 apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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 API
curl "https://apis.io/api/v1/apis/discovery"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
OpenAPI Specification
openapi: 3.2.0
info:
title: Nusano Content API (WordPress REST wp/v2) Discovery API
version: wp/v2
summary: 'Public read surface of nusano.com content: news releases, Nu Blog posts, HALEU knowledge-center and marketing pages, the media library, taxonomies and site search.'
description: 'Nusano publishes nusano.com on WordPress, which exposes the WordPress REST API at https://nusano.com/wp-json/. The `wp/v2` namespace is anonymously readable and returns the company''s news releases, Nu Blog posts, event notices, marketing and HALEU knowledge-center pages, the media library, categories, tags and a site-wide search endpoint as JSON.
This document was DERIVED mechanically by API Evangelist from the route-discovery document served at https://nusano.com/wp-json/wp/v2 on 2026-08-26 — every path, method and parameter below is taken verbatim from that descriptor. Nusano does not publish an OpenAPI definition of its own, and this is NOT a product API: Nusano manufactures radioisotopes, and this is the content API its CMS exposes. Write operations are declared by the route index but require authentication (WordPress Application Passwords over HTTP Basic); anonymous writes return 401 `rest_forbidden`.'
contact:
name: Nusano
url: https://nusano.com/
x-derived-by: API Evangelist enrichment pipeline
x-derived-from: https://nusano.com/wp-json/wp/v2
x-derived-on: '2026-08-26'
x-provider-published: false
servers:
- url: https://nusano.com/wp-json
description: Production
tags:
- name: Discovery
paths:
/wp/v2/types:
get:
operationId: getTypes
summary: GET /wp/v2/types
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: array
items:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/wp/v2/types/{type}:
get:
operationId: getTypesByType
summary: GET /wp/v2/types/{type}
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: type
in: path
required: true
schema:
type: string
description: Path parameter `type` as declared by the WordPress route index.
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/wp/v2/taxonomies:
get:
operationId: getTaxonomies
summary: GET /wp/v2/taxonomies
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
- name: type
in: query
required: false
schema:
type: string
description: Limit results to taxonomies associated with a specific post type.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: array
items:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/wp/v2/taxonomies/{taxonomy}:
get:
operationId: getTaxonomiesByTaxonomy
summary: GET /wp/v2/taxonomies/{taxonomy}
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: taxonomy
in: path
required: true
schema:
type: string
description: Path parameter `taxonomy` as declared by the WordPress route index.
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/wp/v2/statuses:
get:
operationId: getStatuses
summary: GET /wp/v2/statuses
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: array
items:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/wp/v2/statuses/{status}:
get:
operationId: getStatusesByStatus
summary: GET /wp/v2/statuses/{status}
description: Type, taxonomy and status descriptors that describe the shape of the content collections.
tags:
- Discovery
parameters:
- name: status
in: path
required: true
schema:
type: string
description: Path parameter `status` as declared by the WordPress route index.
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
responses:
'200':
description: Successful response.
content:
application/json:
schema:
type: object
'400':
description: Bad Request — a required parameter is missing or invalid (`rest_missing_callback_param`, `rest_invalid_param`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — the route requires authentication (`rest_forbidden`). WordPress returns 401 with a JSON error envelope.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'404':
description: Not Found — no route matched (`rest_no_route`) or the resource id does not exist (`rest_post_invalid_id`).
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
Error:
type: object
description: The WordPress REST error envelope.
properties:
code:
type: string
description: Machine-readable error code, e.g. `rest_forbidden`.
message:
type: string
description: Human-readable error message.
data:
type: object
properties:
status:
type: integer
description: HTTP status code.
required:
- code
- message
securitySchemes:
applicationPassword:
type: http
scheme: basic
description: WordPress Application Passwords over HTTP Basic. Anonymous read is permitted on these routes; every write requires credentials.