Rice University
Rice University is a private research university in Houston, Texas. Its programmable footprint is small, and most of what appears to be Rice's is not: the Rice Research Repository at repository.rice.edu is a CNAME to rice.dspacedirect.org and runs on DSpaceDirect, the Lyrasis-hosted DSpace service, so its REST and OAI-PMH contracts are the platform's engineering on Rice's content, recorded here as a tenancy rather than credited to Rice. What Rice genuinely operates is three things. It runs its own Shibboleth/SAML 2.0 identity provider at idp.rice.edu, on Rice's own ARIN allocation behind an InCommon-issued certificate, and registers it in the InCommon federation — the strongest machine-readable contract on Rice's public surface. It is a direct DataCite member (symbol RICE, eight prefixes, 2,169 DOIs) through Fondren Library. And its Kinder Institute for Urban Research operates the Urban Data Platform, a genuinely public, unauthenticated JSON API serving a 431-dataset Houston-region urban data catalog with its own controlled vocabularies and DataCite DOIs — undocumented, unadvertised, and the only self-operated callable API Rice has. There is no central developer portal, no llms.txt, no .well-known catalog, and the official RiceUniversity GitHub organization has zero public repositories; Rice's Center for Research Computing publishes separately at github.com/rice-crc.
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 Rice University the way a machine reads it — 19 machine-readable artifacts across 1 API, 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 — Rice University scores 46.9/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 Rice University'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/rice/"
title="Rice University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/rice.svg"
alt="Rice University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/rice/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/rice/"
title="Rice University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/rice/card.svg"
alt="Rice University 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 Rice University
Each block below is one kind of artifact we hold for Rice University. 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 8
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.
Rice Kinder Institute Urban Data Platform API
The only publicly callable API Rice University itself operates. Serves the Kinder Institute for Urban Research's Urban Data Platform: a 431-dataset catalog of Houston and Harris...
Rice Shibboleth SAML 2.0 Identity Provider
Rice University's own Shibboleth/SAML 2.0 identity provider, publishing a live EntityDescriptor with an IDPSSODescriptor, a shibmd:Scope of rice.edu and support for SAML 1.1, SA...
InCommon Federation registration
Rice's identity provider is registered in InCommon, the US research and education identity federation, and InCommon's metadata query service returns a signed EntityDescriptor fo...
DataCite membership — Fondren Library, Rice University
Rice University is a DataCite direct member, registered 2017-11-13 as provider `rice` (symbol RICE) under Fondren Library and linked to ROR https://ror.org/008zs3103. The member...
ROR registration — Rice University
Rice University's entry in the Research Organization Registry, ROR ID https://ror.org/008zs3103. It is the identifier DataCite's member record for Fondren Library points at, and...
Rice University Course Schedule
Rice's public course catalog and schedule search, served from courses.rice.edu on Rice's own network (128.42.207.157, RICENET). It is an Ellucian Banner self-service interface (...
Rice Research Repository (DSpaceDirect tenancy) — REST API
The Rice Research Repository (R-3) is Fondren Library's institutional repository, holding Rice theses, dissertations and scholarship back to 2005 and minting DOIs on Rice's own ...
Rice Research Repository (DSpaceDirect tenancy) — OAI-PMH
OAI-PMH 2.0 harvesting endpoint for the Rice Research Repository. Identify returns repositoryName "Rice Research Repository", repositoryIdentifier repository.rice.edu, adminEmai...
Scroll within the panel for all 8 ·
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.
Rice 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.
Rice 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.
Rice 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.
Rice Context
JSON-LDJSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
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.
Resources
Every other property we hold for Rice University — 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 1
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
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/rice · machine-readable index on apis.io
This is an independent, third-party profile of Rice University, 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.