Nagoya University

NAGOYA Repository OAI-PMH (NII WEKO3 / JAIRO Cloud tenant)

OAI-PMH 2.0 metadata harvesting interface for the NAGOYA Repository, Nagoya University's institutional repository. Verified live 2026-09-01 — verb=Identify returns 200 text/xml with repositoryName "NAGOYA Repository", baseURL https://nagoya.repo.nii.ac.jp/oai, protocolVersion 2.0, earliestDatestamp 2017-11-30T00:00:00Z, deletedRecord transient, granularity YYYY-MM-DDThh:mm:ssZ and adminEmail ir-admin@nul.nagoya-u.ac.jp (Nagoya University Library). verb=ListMetadataFormats returns seven prefixes — jpcoar_1.0, jpcoar, jpcoar_2.0, oai_dc, ddi, jpcoar_v1 and lom — i.e. the JPCOAR schema plus Dublin Core, DDI and LOM. verb=ListSets returns 100 setSpecs per page mapping the university's own organisational units and journal series. nagoya.repo.nii.ac.jp is an institution-specific subdomain on the National Institute of Informatics' WEKO3 / JAIRO Cloud platform: the records, the metadata and the library staff are Nagoya's; the software, the host and the contract are NII's. Recorded here as a tenant relationship — a real institutional fact — rather than credited to Nagoya as its own engineering. No WEKO3 contract is saved under this institution, because it is a product contract identical across every JAIRO Cloud repository in Japan. Operational note: the endpoint returns 406 to a browser User-Agent and 200 to a default client.

GitHub

Documentation

📖
Documentation
https://nagoya.repo.nii.ac.jp/about

Other Resources

🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/nagoya/refs/heads/main/conformance/nagoya-conformance.yml

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

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/repo-oai"
All apis 
curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: nagoya:repo-oai
name: NAGOYA Repository OAI-PMH (NII WEKO3 / JAIRO Cloud tenant)
x-operator: tenant
description: 'OAI-PMH 2.0 metadata harvesting interface for the NAGOYA Repository, Nagoya University''s
  institutional repository. Verified live 2026-09-01 — verb=Identify returns 200 text/xml with repositoryName
  "NAGOYA Repository", baseURL https://nagoya.repo.nii.ac.jp/oai, protocolVersion 2.0, earliestDatestamp
  2017-11-30T00:00:00Z, deletedRecord transient, granularity YYYY-MM-DDThh:mm:ssZ and adminEmail ir-admin@nul.nagoya-u.ac.jp
  (Nagoya University Library). verb=ListMetadataFormats returns seven prefixes — jpcoar_1.0, jpcoar, jpcoar_2.0,
  oai_dc, ddi, jpcoar_v1 and lom — i.e. the JPCOAR schema plus Dublin Core, DDI and LOM. verb=ListSets
  returns 100 setSpecs per page mapping the university''s own organisational units and journal series.
  nagoya.repo.nii.ac.jp is an institution-specific subdomain on the National Institute of Informatics''
  WEKO3 / JAIRO Cloud platform: the records, the metadata and the library staff are Nagoya''s; the software,
  the host and the contract are NII''s. Recorded here as a tenant relationship — a real institutional
  fact — rather than credited to Nagoya as its own engineering. No WEKO3 contract is saved under this
  institution, because it is a product contract identical across every JAIRO Cloud repository in Japan.
  Operational note: the endpoint returns 406 to a browser User-Agent and 200 to a default client.'
humanURL: https://nagoya.repo.nii.ac.jp/
baseURL: https://nagoya.repo.nii.ac.jp/oai
tags:
- Research Repository
- OAI-PMH
- JPCOAR
- WEKO
- Open Access
- Tenant
- Metadata
properties:
- type: Documentation
  url: https://nagoya.repo.nii.ac.jp/about
- type: Conformance
  url: conformance/nagoya-conformance.yml