Universiti Teknologi Malaysia
Universiti Teknologi Malaysia (UTM) is a public research university in Johor Bahru and Kuala Lumpur, Malaysia, one of the five institutions designated a Research University by the Ministry of Higher Education and ranked #181 in the QS World University Rankings 2025. UTM publishes no developer portal, no API documentation and no OpenAPI, AsyncAPI or JSON Schema of its own, and there is no route by which an unaffiliated developer can obtain a credential for anything it runs. Its programmable footprint is entirely made of standards it exposes rather than interfaces it designed, and every one of them sits on UTM's own APNIC allocation (161.139.0.0/16, netname UTM-MY): the UTMIK Repository, a DSpace-CRIS institutional knowledge repository whose OAI-PMH 2.0 endpoint answers anonymously in twelve metadata formats including rioxx, etdms and an OpenAIRE CERIF-for-CRIS profile; the UTM Press journal platform, whose Open Journal Systems OAI-PMH interface has been harvestable since 2011 and whose REST API v1 answers 401; and a Microsoft Entra ID tenant whose signed SAML 2.0 metadata and OpenID Connect discovery document are the most completely specified machine contract in this profile. UTM is registered in ROR, and its own publishing arm, Penerbit UTM Press, is Crossref member 4787 with prefix 10.11113 and 12,640 registered DOIs. The older EPrints repository at eprints.utm.my, still listed by ROAR, OpenDOAR and Sherpa and still linked from the UTM Library, refused connections on both ports from three independent networks on 2026-09-01 and is recorded here as unreachable rather than as a surface.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Universiti Teknologi Malaysia the way a machine reads it — 12 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Universiti Teknologi Malaysia scores 28.4/100 (thin), with a separate agent-readiness read of 5/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
UTM operates real institution-owned surfaces and they were read, but nothing it runs is consumable as an API by an unaffiliated caller. The two anonymously readable interfaces are metadata-harvesting protocols, not APIs UTM designed: OAI-PMH 2.0 on the UTMIK DSpace-CRIS repository and on the UTM Press OJS journal platform, both on UTM's own APNIC allocation. Every REST interface behind them is closed — the OJS REST API v1 answers 401 with a JSON authorization error and publishes no route to request a token, and the DSpace REST collections answered 403 even though the HAL root is public. The one fully specified machine contract, UTM's Microsoft Entra ID tenant, publishes signed SAML 2.0 metadata and an OIDC discovery document that anyone can read, but no registration_endpoint, so a client_id exists only if UTM Digital creates one. There is no developer portal: the www.utm.my sitemap contains exactly one policy page and no API, developer or open-data page, api.utm.my resolves and returns HTTP 200 with a 17-byte empty IIS document and 404s on every documented path, and no official UTM GitHub organization exists (the two name-matching orgs hold zero and one unrelated repository). Two limits are recorded rather than treated as findings about UTM. eprints.utm.my, the legacy EPrints repository still listed by ROAR, OpenDOAR and Sherpa, refused connections on both ports from three independent networks and is not credited as live. And utmik.utm.my answered fully at 17:26Z on 2026-09-01 — the OAI-PMH responseDate is the server's own proof — then stopped answering this environment and two public proxies later the same day, so its pointers may grade dead on a re-probe while the surface is real. This is a correct thin profile, not a failed probe: more than fifty URLs were fetched successfully across eleven UTM hosts.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Universiti Teknologi Malaysia's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://utmik.utm.my/server/oai/request?verb=Identify→ HTTP 200https://utmik.utm.my/server/oai/request?verb=ListMetadataFormats→ HTTP 200https://utmik.utm.my/server/oai/request?verb=ListSets→ HTTP 200https://utmik.utm.my/server/api→ HTTP 200https://utmik.utm.my/server/api/core/communities→ HTTP 403https://journals.utm.my/index.php/index/oai?verb=Identify→ HTTP 200https://journals.utm.my/index.php/index/oai?verb=ListSets→ HTTP 200https://journals.utm.my/jurnalteknologi/api/v1/issues→ HTTP 401https://login.microsoftonline.com/utm.my/v2.0/.well-known/openid-configuration→ HTTP 200https://login.microsoftonline.com/9c827912-3502-4333-ba47-1b242c3d20e6/federationmetadata/2007-06/federationmetadata.xml→ HTTP 200https://login.microsoftonline.com/getuserrealm.srf?login=user@utm.my&json=1→ HTTP 200https://api.crossref.org/members/4787→ HTTP 200https://api.crossref.org/journals/2180-3722→ HTTP 200https://api.ror.org/organizations/026w31v75→ HTTP 200https://www.utm.my/→ HTTP 200https://www.utm.my/wp-sitemap.xml→ HTTP 200https://www.utm.my/privacy-policy/→ HTTP 200https://www.utm.my/llms.txt→ HTTP 404https://www.utm.my/.well-known/security.txt→ HTTP 404https://api.utm.my/→ HTTP 200https://api.utm.my/swagger/v1/swagger.json→ HTTP 404https://library.utm.my/utm-institutional-repository/→ HTTP 200https://my.utm.my/login→ HTTP 200https://news.utm.my/→ HTTP 200https://news.utm.my/feed/→ HTTP 403https://elearning.utm.my/mod/lti/auth.php→ HTTP 404https://technical.edugain.org/api.php?action=list_entities&format=json→ HTTP 200https://www.sifulan.my/→ HTTP 403https://api.datacite.org/clients?query=Universiti+Teknologi+Malaysia→ HTTP 200http://eprints.utm.my/cgi/oai2?verb=Identify→ HTTP 0https://openscience.utm.my/→ HTTP 0https://hpc.utm.my/→ HTTP 0
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Universiti Teknologi Malaysia's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/utm/"
title="Universiti Teknologi Malaysia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/utm.svg"
alt="Universiti Teknologi Malaysia Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/utm/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/utm/"
title="Universiti Teknologi Malaysia on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/utm/card.svg"
alt="Universiti Teknologi Malaysia Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Universiti Teknologi Malaysia
Each block below is one kind of artifact we hold for Universiti Teknologi Malaysia. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
UTMIK Repository (DSpace-CRIS) — OAI-PMH and REST
UTM's institutional knowledge repository, running DSpace-CRIS on utmik.utm.my (161.139.22.165, inside UTM's own APNIC allocation 161.139.0.0/16, netname UTM-MY). The OAI-PMH 2.0...
UTM Press Journals (Open Journal Systems) — OAI-PMH
Penerbit UTM Press runs the university's journal estate on PKP Open Journal Systems at journals.utm.my (161.139.22.105, UTM's own allocation). The site-wide OAI-PMH 2.0 interfac...
UTM identity federation — Microsoft Entra ID tenant (SAML 2.0 / OpenID Connect)
UTM's institutional identity provider. The tenant (9c827912-3502-4333-ba47-1b242c3d20e6) is bound to UTM by domain ownership — realm discovery on user@utm.my returns FederationB...
Crossref membership — Penerbit UTM Press (member 4787, prefix 10.11113)
UTM's own university press is a Crossref member in its own right, not a customer of someone else's prefix: member id 4787, DOI prefix 10.11113, 12,640 registered DOIs. Its flags...
ROR registration — https://ror.org/026w31v75
UTM is registered in the Research Organization Registry as ror.org/026w31v75, with domain utm.my, established 1975, GRID grid.410877.d, ISNI 0000 0001 2296 1505, Wikidata Q24401...
UTM Institutional Repository (UTM-IR) EPrints OAI-PMH — unreachable
The older EPrints institutional repository, registered with ROAR (record 1358), OpenDOAR and Sherpa (record 987) and still linked from the UTM Library as http://eprints.utm.my. ...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Utm Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Utm Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Utm Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Utm Context
JSON-LDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Universiti Teknologi Malaysia — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/utm · machine-readable index on apis.io
This is an independent, third-party profile of Universiti Teknologi Malaysia, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.