University of Texas at Austin
The University of Texas at Austin is a flagship public research university in Austin, Texas, United States, and the largest institution in the University of Texas System. It operates no central developer portal, publishes no institution-wide API catalog, and its enterprise integration APIs (Identity and Access Management, student and financial systems) are gated behind UT EID authentication and an internal ServiceNow request process, so they are not publicly readable. What UT Austin does genuinely operate and expose publicly is narrower and more specific than a portal: the Tapis v3 research-computing platform, designed, built and run by the Texas Advanced Computing Center — an organized research unit of UT Austin — which serves five OpenAPI-described services (Systems, Files, Apps, Jobs, Notifications) on its production TACC tenant; an InCommon-registered Shibboleth identity provider publishing both SAML 2.0 metadata and an OpenID Connect discovery document; and Texas ScholarWorks, the UT Libraries DSpace repository, with a public REST API and an OAI-PMH 2.0 harvesting endpoint on the university's own host. Its research-data archive is a tenancy rather than an operation: UT Austin publishes into a Dataverse collection on the Texas Digital Library's shared instance, and the library discovery layer is Ex Libris Primo. Both are recorded here as relationships, not as UT Austin engineering.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles University of Texas at Austin the way a machine reads it — 16 machine-readable artifacts across 5 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 — University of Texas at Austin scores 50.8/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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 University of Texas at Austin'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/university-of-texas-at-austin/"
title="University of Texas at Austin on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-texas-at-austin.svg"
alt="University of Texas at Austin Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/university-of-texas-at-austin/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/university-of-texas-at-austin/"
title="University of Texas at Austin on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/university-of-texas-at-austin/card.svg"
alt="University of Texas at Austin 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 University of Texas at Austin
Each block below is one kind of artifact we hold for University of Texas at Austin. 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 5
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.
Tapis v3 Research Computing Platform (TACC production tenant)
Tapis is the API platform TACC builds and operates for programmatic access to research computing: registering storage and compute systems, moving files, defining applications, s...
UT Austin Enterprise Identity Provider (SAML 2.0 + OpenID Connect)
UT Austin's Shibboleth identity provider, and the most under-catalogued class of institutional API surface. It publishes SAML 2.0 metadata at /idp/shibboleth (entityID https://e...
Texas ScholarWorks DSpace REST API
Public DSpace REST API for Texas ScholarWorks, the UT Libraries institutional repository of theses, dissertations, faculty research and open-access scholarship. The root documen...
Texas ScholarWorks OAI-PMH Endpoint
OAI-PMH 2.0 metadata-harvesting endpoint for Texas ScholarWorks. An Identify request returns repositoryName "DSpace at UT Austin", baseURL https://repositories.lib.utexas.edu/se...
Texas Data Repository (Dataverse) — UT Austin collection
UT Austin publishes and archives research datasets in the Texas Data Repository, a Dataverse instance operated by the Texas Digital Library and shared across Texas institutions....
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.
Rate 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.
University Of Texas At Austin 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.
Semantic 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.
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for University of Texas at Austin — 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.
Documentation 2
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/university-of-texas-at-austin · machine-readable index on apis.io
This is an independent, third-party profile of University of Texas at Austin, 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.