Nagoya University
Nagoya University (名古屋大学) is a national research university in Nagoya, Aichi, Japan, ranked #152 in the QS World University Rankings 2025. As a leading research institution it operates a range of academic and IT services through its Information & Communications (ICTS) division and university library. Its most clearly documented public, machine-readable API surface is the NAGOYA Repository institutional repository, which runs on the NII WEKO3 / JAIRO Cloud platform and exposes an OAI-PMH 2.0 interface for harvesting scholarly metadata. Most other systems (student portal, NU-ID identity, course registration) are gated behind THERS/GakuNin (Shibboleth/SAML) authentication and are not publicly documented developer APIs.
Nagoya University publishes 1 API on the APIs.io network. Tagged areas include Education, Higher Education, University, Research, and Open Access.
The Nagoya University catalog on APIs.io includes 1 JSON-LD context.
Nagoya University’s developer surface includes authentication, engineering blog, and 10 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
NAGOYA Repository OAI-PMH
OAI-PMH 2.0 metadata harvesting interface for the NAGOYA Repository, the Nagoya University institutional repository running on the NII WEKO3 / JAIRO Cloud platform. Supports the...
Pricing Plans 1
Published pricing tiers and plan structures.
Nagoya Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Nagoya Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Nagoya Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Nagoya Context
JSON-LDSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider 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 providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.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
curl "https://apis.io/api/v1/providers/nagoya"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/nagoya/operations?limit=25"
curl "https://apis.io/api/v1/providers/nagoya/evidence"
Discovery needs no key. Ratings and market analysis are Pro.