University of California, Davis
The University of California, Davis (UC Davis) is a public land-grant research university located in Davis, California, and ranked #48 in the QS World University Rankings 2025. Its public developer footprint is decentralized across campus units rather than a single unified developer portal. Confirmed surfaces include IET Middleware Web Service APIs (identity/integration middleware), a UC Davis Health systems-integration program offering Epic/FHIR and custom REST/SOAP APIs, the CAES Computing Resources Unit APIs (PEAKS, ACE), an internal developer SIG community at developers.ucdavis.edu, and the official ucdavis GitHub organization with 441+ public repositories. Most administrative and identity APIs are gated behind institutional affiliation, SSO, or partner agreements rather than open self-service signup.
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 University of California, Davis the way a machine reads it — 29 machine-readable artifacts across 12 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 California, Davis scores 41.4/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile University of California, Davis
Each block below is one kind of artifact we hold for University of California, Davis. 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 12
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.
IET Middleware Web Service APIs
Information and Educational Technology (IET) Middleware Web Service APIs provide campus integration and identity-related middleware services. Usage instructions are published vi...
UC Davis Health Systems Integration APIs
UC Davis Health offers Epic (EHR), HL7 FHIR, and custom APIs accessed via SOAP or REST using JSON/XML. Authentication methods include API Key, OAuth2, and Direct Interconnect fo...
CAES ACE API
The CAES Computing Resources Unit publishes the ACE API with documentation supporting college administrative and content workflows.
University of California, Davis Access API
The Access API from University of California, Davis — 10 operation(s) for access.
University of California, Davis Documents API
The Documents API from University of California, Davis — 6 operation(s) for documents.
University of California, Davis Equipment API
The Equipment API from University of California, Davis — 17 operation(s) for equipment.
University of California, Davis Keys API
The Keys API from University of California, Davis — 10 operation(s) for keys.
University of California, Davis KeySerials API
The KeySerials API from University of California, Davis — 11 operation(s) for keyserials.
University of California, Davis People API
The People API from University of California, Davis — 4 operation(s) for people.
University of California, Davis PeopleAdmin API
The PeopleAdmin API from University of California, Davis — 4 operation(s) for peopleadmin.
University of California, Davis Spaces API
The Spaces API from University of California, Davis — 6 operation(s) for spaces.
University of California, Davis Workstations API
The Workstations API from University of California, Davis — 13 operation(s) for workstations.
Scroll within the panel for all 12 ·
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 six things the Kin Score reads for commercial clarity.
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.
Uc Davis 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.
Uc Davis 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.
Uc Davis Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 4
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.
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Uc Davis Equipment Structure
JSON STRUCTUREUc Davis Key Structure
JSON STRUCTUREExamples 2
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.
Uc Davis Keys List Example
EXAMPLESecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for University of California, Davis — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/uc-davis · machine-readable index on apis.io