Texas A&M University
Texas A&M University is a public land-grant research university in College Station, Texas, the flagship of the Texas A&M University System, and ranked #154 in the QS World University Rankings 2025. Unlike most institutions in this cohort it is not a pure buyer: several of the surfaces recorded here are Texas A&M's own engineering on Texas A&M's own hosts, and each one below was fetched and given a status code before it was written down. The genuinely institution-operated tier is four contracts wide. Texas A&M GeoServices (geoservices.tamu.edu) publishes a documented, free, self-service geocoding and address normalisation API at version 5.0.0 that returns up to 172 output fields — a research product of the university's geospatial group and the strongest institution-authored API in the higher-education catalog. The Aggie Map application backend (api.aggiemap.tamu.edu) serves campus dining locations with live open/closed state as GeoJSON, and a companion feed on geoservices.tamu.edu serves live shared-micromobility vehicle positions; both are undocumented, unauthenticated backends rather than offered products, and are recorded as such. Texas A&M IT runs a public Esri ArcGIS Server (gis.it.tamu.edu, mirrored at gis.tamu.edu) whose services directory answers anonymously across seven folders of campus base maps, construction, transit and event-flow layers. Two further institution-operated surfaces are protocol surfaces rather than REST APIs. The university's Shibboleth Identity Provider publishes SAML 2.0 metadata unauthenticated from idp.tamu.edu and is registered in InCommon as urn:mace:incommon:tamu.edu, which carries it into eduGAIN — the surface class this cohort was most completely missing. The OAKTrust institutional repository exposes a working OAI-PMH 2.0 endpoint whose Identify response names Texas A&M Libraries' own help desk and no vendor at all, which is rare in this cohort. Against that, the enterprise tier is closed. The Texas A&M University System API Developer Portal (api-doc.sea.system.tamus.edu) is live but renders nothing without a sponsored System account; the UIN Services API is documented in prose and gated behind subscription approval by the System Enterprise Applications DevOps group, so no base URL and no specification is published. There is no open-data portal — data.tamu.edu resolves in DNS but every HTTPS connection times out — no llms.txt, and no student-facing course or registrar API. The course catalog is a Leepfrog CourseLeaf tenancy and the LMS is an Instructure Canvas tenancy; both are real relationships and neither is Texas A&M's contract. Texas A&M Libraries holds DOI prefix 10.21423 as a registrant at both DataCite and Crossref, and the university carries ROR id 01f5ytq51.
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 Texas A&M University the way a machine reads it — 26 machine-readable artifacts across 4 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 — Texas A&M University scores 42.7/100 (developing), with a separate agent-readiness read of 22/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 Texas A&M 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/texas-a-m-university/"
title="Texas A&M University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/texas-a-m-university.svg"
alt="Texas A&M University Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/texas-a-m-university/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/texas-a-m-university/"
title="Texas A&M University on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/texas-a-m-university/card.svg"
alt="Texas A&M 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 Texas A&M University
Each block below is one kind of artifact we hold for Texas A&M 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 13
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.
Texas A&M GeoServices Geocoding API
Free geocoding, address normalisation and standardisation, census intersection and reverse geocoding from Texas A&M GeoServices. Version 5.0.0 returns up to 172 output fields; a...
Aggie Map Dining Locations API
Read-only GeoJSON feed of Texas A&M campus dining locations with live open/closed state, status message, street address and an occupancy signal, served from the university's own...
Campus Micromobility Vehicle Positions API
Live positions of shared micromobility vehicles on and around campus as GeoJSON, served from veoride.geoservices.tamu.edu inside Texas A&M's own geoservices estate. Verified 200...
Texas A&M IT ArcGIS REST Services
Public Esri ArcGIS Server operated by Texas A&M IT, serving campus base maps, ADA routes, construction, department search, transit lots, bike maps and event pedestrian/vehicle f...
OAKTrust Institutional Repository — OAI-PMH
OAI-PMH 2.0 harvesting endpoint for OAKTrust, the Texas A&M University Libraries institutional repository. Verified 200 on 2026-09-01: repositoryName "OAKTrust", repositoryIdent...
Texas A&M Shibboleth Identity Provider Metadata
SAML 2.0 metadata for Texas A&M University's own Shibboleth Identity Provider, published unauthenticated from idp.tamu.edu. Verified 200 with content-type application/xml on 202...
InCommon Federation Registration
Texas A&M University's registration in the InCommon identity federation, resolvable through InCommon's per-entity Metadata Query service under entityID urn:mace:incommon:tamu.ed...
UIN Services API
Texas A&M University System enterprise API to search, verify, create and update Universal Identification Numbers. Gated: access requires registering an application, subscribing ...
Texas A&M Course Catalog (CourseLeaf)
The Texas A&M academic catalog runs on Leepfrog CourseLeaf at catalog.tamu.edu. Its machine-readable course-detail route answered 200 as text/xml on 2026-09-01 for /ribbit/?page...
Canvas Learning Management System (tenancy)
Texas A&M's learning management system is Instructure Canvas: canvas.tamu.edu is a CNAME to texasam-vanity.instructure.com. The tenancy is a real institutional fact and is recor...
DataCite Registrant — Texas A&M Libraries
Texas A&M Libraries is a DataCite consortium organization (provider CXAU) whose record carries Texas A&M University's own ROR id, https://ror.org/01f5ytq51, and which owns the r...
Crossref Member — Texas A&M University Libraries
Texas A&M University Libraries is Crossref member 14385, holding DOI prefix 10.21423 with 7,464 registered DOIs (706 current, 6,758 backfile) as of 2026-09-01. The same prefix i...
ROR Registration
Texas A&M University is registered in the Research Organization Registry as https://ror.org/01f5ytq51, with domain tamu.edu, established 1876, types education and funder, and cr...
Scroll within the panel for all 13 ·
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.
Texas A M University 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.
Texas A M University Context
JSON-LDJSON Schema 2
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.
Texas A&M Aggie Map Dining Location
JSON SCHEMAExamples 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 3
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 Texas A&M 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 3
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 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/texas-a-m-university · machine-readable index on apis.io
This is an independent, third-party profile of Texas A&M 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.