University of California, Davis
The University of California, Davis is a public land-grant research university in Davis, California and a member of the ten-campus University of California system. Its programmable footprint is real but decentralized: there is no campus-wide developer portal, no API gateway, no published deprecation policy and no self-service signup for anything. What UC Davis genuinely operates and authored itself is three things — the Aggie Experts API (UC Davis Library, OpenAPI 3.0.0 v5.0, twelve operations over experts, works and grants, callable anonymously and returning JSON-LD with ORCID iDs and UC Davis ARK identifiers), the DAMS API behind digital.ucdavis.edu (built on the Library's own open-source 'fin' framework, though several documented operations return soft-200 errors), and the PEAKS asset- and access-tracking API run by the College of Agricultural and Environmental Sciences (MIT-licensed, source at github.com/ucdavis/Peaks, API-key gated). Alongside those it runs a SAML 2.0 Shibboleth identity provider published to InCommon as urn:mace:incommon:ucdavis.edu, and UC Davis Health operates a live FHIR R4 endpoint on its own domain — although that endpoint's CapabilityStatement is Epic's work, not UC Davis's, and is deliberately not claimed here. Two further surfaces are TENANT relationships and are labelled as such rather than credited as UC Davis engineering: scholarly output in eScholarship (operated by the California Digital Library for all of UC) and library discovery on Ex Libris Primo. Several campus surfaces that plainly exist — the open data portal aggiedata.ucdavis.edu, the registrar's course search, research computing at hpc.ucdavis.edu — sit behind a Cloudflare bot challenge and could not be read; that is a limit on this profile, not evidence of absence.
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 California, Davis the way a machine reads it — 53 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 California, Davis scores 47.3/100 (developing), with a separate agent-readiness read of 20/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.
Why this profile is thin
Three genuinely institution-authored contracts were found, fetched and verified callable, so this is not a thin profile. It is a GATED one. Everything UC Davis operates is either open with no registration path at all (Aggie Experts, DAMS — no securitySchemes, no plans, no rate-limit headers) or closed behind institutional affiliation with no public onboarding (PEAKS API keys, IET middleware, UC Davis Health integration). Separately, a cluster of campus surfaces that certainly exist sits behind a Cloudflare bot challenge and returned 403 to every user agent tried, including a current desktop browser string: the AggieData open data portal, the registrar's course search, research computing, and the campus IT AI pages. Those 403s are a limit on this measurement, not a finding about UC Davis — they are live hosts we could not read. eScholarship and ucdavis.figshare.com answer automated clients with an AWS WAF challenge (HTTP 202, zero bytes); the eScholarship tenant relationship was confirmed instead through its OAI-PMH verbs, and no Figshare tenant was claimed because none could be verified. No campus-wide developer portal, changelog, deprecation policy, pricing or rate-limit documentation exists to find.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is University of California, Davis'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://experts.ucdavis.edu/api/→ HTTP 200https://experts.ucdavis.edu/api/expert/browse?p=A&size=3→ HTTP 200https://experts.ucdavis.edu/api/search/?q=genomics&size=1→ HTTP 200https://digital.ucdavis.edu/api/→ HTTP 200https://digital.ucdavis.edu/api/collection→ HTTP 200https://peaks.ucdavis.edu/swagger/v1/swagger.json→ HTTP 200https://shibboleth.ucdavis.edu/idp/shibboleth→ HTTP 200https://mdq.incommon.org/entities/urn%3Amace%3Aincommon%3Aucdavis.edu→ HTTP 200https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/metadata→ HTTP 200https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/.well-known/smart-configuration→ HTTP 200https://escholarship.org/oai?verb=Identify→ HTTP 200https://escholarship.org/uc/ucd→ HTTP 202https://search.library.ucdavis.edu/→ HTTP 200https://aggiedata.ucdavis.edu/→ HTTP 403https://registrar-apps.ucdavis.edu/courses/search/index.cfm→ HTTP 403https://hpc.ucdavis.edu/→ HTTP 403https://it.ucdavis.edu/artificial-intelligence/→ HTTP 403https://catalog.ucdavis.edu/→ HTTP 200https://iet-ws.ucdavis.edu/api/→ HTTP 200https://ucdavis.figshare.com/→ HTTP 202https://www.ucdavis.edu/llms.txt→ HTTP 404https://www.ucdavis.edu/.well-known/security.txt→ HTTP 404https://stage.experts.library.ucdavis.edu/api/schema/context.jsonld→ HTTP 0https://digital.ucdavis.edu/oai?verb=Identify→ HTTP 404https://api.ucdavis.edu/→ HTTP 404
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 California, Davis'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/uc-davis/"
title="University of California, Davis on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uc-davis.svg"
alt="University of California, Davis Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/uc-davis/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/uc-davis/"
title="University of California, Davis on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/uc-davis/card.svg"
alt="University of California, Davis 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 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 20
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.
UC Davis Shibboleth Identity Provider (SAML 2.0 / InCommon)
UC Davis operates its own SAML 2.0 identity provider and publishes signed federation metadata as entityID urn:mace:incommon:ucdavis.edu. This is machine-readable, institution-op...
UC Davis Health FHIR R4 endpoint
UC Davis Health runs a live HL7 FHIR R4 endpoint on its own domain at emrrp.ucdmc.ucdavis.edu, registered in Epic's public endpoint directory as 'UC Davis' and 'UC Davis - MMC' ...
IET Middleware Web Service APIs
Information and Educational Technology (IET) Middleware Web Service APIs provide campus integration and identity-related middleware. Probed 2026-08-19: the endpoint returns HTTP...
UC Davis Health Systems Integration APIs
UC Davis Health Systems Integration offers Epic (EHR), HL7 FHIR and custom SOAP/REST APIs, authenticated with API keys, OAuth2 or Epic Interconnect and fronted by InterSystems A...
CAES ACE API
The CAES Computing Resources Unit documents an ACE API supporting college administrative and content workflows. Probed 2026-08-19: the documentation page returns HTTP 200, but n...
PEAKS (CAES) — Access API
The Access resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences...
PEAKS (CAES) — Documents API
The Documents resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Scien...
PEAKS (CAES) — Equipment API
The Equipment resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Scien...
PEAKS (CAES) — Keys API
The Keys resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences C...
PEAKS (CAES) — KeySerials API
The KeySerials resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Scie...
PEAKS (CAES) — People API
The People resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences...
PEAKS (CAES) — PeopleAdmin API
The PeopleAdmin resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sci...
PEAKS (CAES) — Spaces API
The Spaces resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sciences...
PEAKS (CAES) — Workstations API
The Workstations resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application the UC Davis College of Agricultural and Environmental Sc...
eScholarship — UC Davis unit (tenant)
UC Davis's open-access scholarly output is deposited into eScholarship, the University of California's shared repository, under the campus unit path /uc/ucd. The content, the de...
UC Davis Library discovery — Ex Libris Primo (tenant)
Library discovery at search.library.ucdavis.edu is an Ex Libris Primo instance. The subdomain is UC Davis's and the collection is UC Davis's, but the application is Ex Libris's:...
University of California, Davis Collection API
The collection API from University of California, Davis — 2 operation(s) for collection.
University of California, Davis Expert API
Expert Information
University of California, Davis Item API
The item API from University of California, Davis — 1 operation(s) for item.
University of California, Davis page search API
The page search API from University of California, Davis — 1 operation(s) for page search.
Scroll within the panel for all 20 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPEAKS API v1 Access API
OPEN COLLECTIONPEAKS API v1 Access Documents API
OPEN COLLECTIONPEAKS API v1 Access Equipment API
OPEN COLLECTIONPEAKS API v1 Access Keys API
OPEN COLLECTIONPEAKS API v1 Access KeySerials API
OPEN COLLECTIONPEAKS API v1 Access People API
OPEN COLLECTIONPEAKS API v1 Access PeopleAdmin API
OPEN COLLECTIONPEAKS API v1 Access Spaces API
OPEN COLLECTIONPEAKS API v1 Access Workstations API
OPEN COLLECTIONScroll within the panel for all 10 ·
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.
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 7
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.
UC Davis Aggie Experts — Expert
JSON SCHEMAUC Davis Aggie Experts — Grant
JSON SCHEMAUC Davis Aggie Experts — Work
JSON SCHEMAPEAKS Equipment
JSON SCHEMAPEAKS Key
JSON SCHEMAPEAKS Person
JSON SCHEMAPEAKS Space
JSON SCHEMAScroll within the panel for all 7 ·
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 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.
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
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
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 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 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/uc-davis · machine-readable index on apis.io
This is an independent, third-party profile of University of California, Davis, 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.