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.
University of California, Davis publishes 13 APIs on the APIs.io network, including PEAKS (CAES) — Access API, PEAKS (CAES) — Documents API, PEAKS (CAES) — Equipment API, and 10 more. Tagged areas include University, Higher Education, Education, United States, and California.
The University of California, Davis catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
University of California, Davis’ developer surface includes status page, support, documentation, API reference, authentication, and 25 more developer resources.
5 APIs
Individual APIs this provider publishes, each with its own machine-readable definition.
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 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' ...
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 offers Epic (EHR), HL7 FHIR and custom SOAP/REST APIs, authenticated with API keys, OAuth2 or Epic Interconnect and fronted by InterSystems A...
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...
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...
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...
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...
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...
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...
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...
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...
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...
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...
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...
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:...
The collection API from University of California, Davis — 2 operation(s) for collection.
The item API from University of California, Davis — 1 operation(s) for item.
The page search API from University of California, Davis — 1 operation(s) for page search.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Published pricing tiers and plan structures.
Documented rate limits and quota policies.
Cost, billing, and metering signals for API financial operations.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral governance rulesets for linting and validating these APIs.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure definitions describing this provider's data shapes.
Example request and response payloads for these APIs.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
OAuth scopes governing access to this provider's APIs.
Recommended x-agentic-access execution contracts for AI agents.
aid: uc-davis
name: University of California, Davis
description: '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.'
type: Index
x-type: university
x-category: Public Research University
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: free
onboarding: restricted
trial: false
try_now: true
public: true
label: Free · No self-service signup
confidence: high
source:
- authentication
- openapi
- probed
generated: '2026-08-19'
method: probed
note: Corrected 2026-08-19. The previous record said 'self-serve signup', which no UC Davis surface offers. Aggie Experts
and DAMS answer anonymously with no registration at all; PEAKS requires an X-Auth-Token issued to a campus team; IET middleware
and UC Davis Health APIs require institutional affiliation or a written agreement.
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/uc-davis.png
url: https://raw.githubusercontent.com/api-evangelist/uc-davis/refs/heads/main/apis.yml
tags:
- University
- Higher Education
- Education
- United States
- California
- UC System
- Public Research University
- Research
- Research Data
- Identity Federation
- Digital Collections
- Library
- Health
- Open-Source
tags_raw:
- University
- Higher Education
- Education
- United States
- California
- UC System
- Public Research University
- Research
- Research Data
- Identity Federation
- Digital Collections
- Library
- Health
- Open Source
created: '2026-06-03'
modified: '2026-08-19'
specificationVersion: '0.23'
x-coverage:
state: gated
generated: '2026-08-19'
method: probed
reason: partial_bot_block_and_no_self_service
detail: '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.'
evidence:
- url: https://experts.ucdavis.edu/api/
status: 200
note: Aggie Experts OpenAPI 3.0.0 v5.0 — institution-authored
- url: https://experts.ucdavis.edu/api/expert/browse?p=A&size=3
status: 200
note: callable anonymously, 196 results
- url: https://experts.ucdavis.edu/api/search/?q=genomics&size=1
status: 200
note: 1,625 hits
- url: https://digital.ucdavis.edu/api/
status: 200
note: DAMS OpenAPI 3.0.0 — institution-authored
- url: https://digital.ucdavis.edu/api/collection
status: 200
note: 'soft-200: body is an Elasticsearch error with a stack trace'
- url: https://peaks.ucdavis.edu/swagger/v1/swagger.json
status: 200
note: PEAKS API v1, 214KB
- url: https://shibboleth.ucdavis.edu/idp/shibboleth
status: 200
note: SAML 2.0 IdP metadata
- url: https://mdq.incommon.org/entities/urn%3Amace%3Aincommon%3Aucdavis.edu
status: 200
note: signed InCommon entity
- url: https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/metadata
status: 200
note: FHIR R4 CapabilityStatement — Epic-authored, not claimed
- url: https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/.well-known/smart-configuration
status: 200
- url: https://escholarship.org/oai?verb=Identify
status: 200
note: CDL-operated; tenant relationship only
- url: https://escholarship.org/uc/ucd
status: 202
note: AWS WAF challenge, zero bytes — landing page unreadable
- url: https://search.library.ucdavis.edu/
status: 200
note: Ex Libris Primo — tenant
- url: https://aggiedata.ucdavis.edu/
status: 403
note: Cloudflare bot challenge — LIVE, unreadable by us
- url: https://registrar-apps.ucdavis.edu/courses/search/index.cfm
status: 403
note: Cloudflare bot challenge
- url: https://hpc.ucdavis.edu/
status: 403
note: Cloudflare bot challenge
- url: https://it.ucdavis.edu/artificial-intelligence/
status: 403
note: Cloudflare bot challenge — no AIPolicy pointer emitted because none could be verified
- url: https://catalog.ucdavis.edu/
status: 200
note: General Catalog, HTML only, no machine-readable course feed found
- url: https://iet-ws.ucdavis.edu/api/
status: 200
note: 1KB HTML welcome page, no contract
- url: https://ucdavis.figshare.com/
status: 202
note: AWS WAF challenge; no Figshare tenant claimed without evidence
- url: https://www.ucdavis.edu/llms.txt
status: 404
- url: https://www.ucdavis.edu/.well-known/security.txt
status: 404
- url: https://stage.experts.library.ucdavis.edu/api/schema/context.jsonld
status: 0
note: the @context the PRODUCTION Aggie Experts API emits does not resolve
- url: https://digital.ucdavis.edu/oai?verb=Identify
status: 404
note: no institution-operated OAI-PMH
- url: https://api.ucdavis.edu/
status: 404
note: host resolves (18.144.178.99) but serves nothing
apis:
- aid: uc-davis:shibboleth-idp
name: UC Davis Shibboleth Identity Provider (SAML 2.0 / InCommon)
description: '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-operated by definition, and almost never catalogued:
no vendor can be running it, because the metadata is served from UC Davis address space (shibboleth.gdc.ucdavis.edu, 169.237.248.65)
and carries UC Davis''s own organization name. Four SSO bindings and two SLO bindings are advertised across Shibboleth
1.x, SAML 1.1 and SAML 2.0. Verified 200 at both the campus endpoint and the InCommon MDQ service on 2026-08-19.'
humanURL: https://shibboleth.ucdavis.edu/idp/shibboleth
tags:
- Identity Federation
- SAML
- Shibboleth
- InCommon
- Single Sign-On
x-operator: institution
x-operator-evidence: Metadata Organization/OrganizationName is 'University of California, Davis'; all endpoints are on shibboleth.ucdavis.edu.
properties:
- type: x-identity-federation
url: identity/uc-davis-identity-federation.yml
- type: x-saml-metadata
url: identity/uc-davis-shibboleth-idp-metadata.xml
- type: x-saml-metadata
url: identity/uc-davis-incommon-entity-metadata.xml
- type: APIReference
url: https://shibboleth.ucdavis.edu/idp/shibboleth
x-metadata-url: https://shibboleth.ucdavis.edu/idp/shibboleth
- aid: uc-davis:health-fhir-r4
name: UC Davis Health FHIR R4 endpoint
description: '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'' (active since 2024-11-09). Verified 2026-08-19:
/metadata returns a 93KB CapabilityStatement instantiating the US Core server profile and the bulk-data profile, and /.well-known/smart-configuration
returns a SMART on FHIR discovery document with authorization and token endpoints on the same host. IMPORTANT ATTRIBUTION
NOTE: the host and the operation are UC Davis Health''s, but the CapabilityStatement is Epic''s — its own copyright line
reads ''Copyright Epic 1979-2026''. Epic''s contract is therefore NOT saved into this repo; only the relationship and
the live discovery documents are recorded, so UC Davis is credited for operating a FHIR endpoint and not for Epic''s engineering.'
humanURL: https://health.ucdavis.edu/systems-integration/developers
baseURL: https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/
tags:
- Health
- FHIR
- US Core
- SMART on FHIR
- Epic
x-operator: institution
x-contract-author: Epic Systems
x-operator-evidence: emrrp.ucdmc.ucdavis.edu resolves to 152.79.5.54 and is under ucdavis.edu; Epic endpoint directory names
the managing organization 'UC Davis'.
properties:
- type: APIReference
url: https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/metadata
- type: x-smart-configuration
url: https://emrrp.ucdmc.ucdavis.edu/FHIR/api/FHIR/R4/.well-known/smart-configuration
- type: Documentation
url: https://health.ucdavis.edu/systems-integration/developers
- type: x-scopes
url: scopes/uc-davis-scopes.yml
x-baseurl-note: A bare GET on the FHIR base returns 404 by design; the base is verified through /metadata (200) and /.well-known/smart-configuration
(200), both recorded as properties.
- aid: uc-davis:iet-middleware
name: IET Middleware Web Service APIs
description: 'Information and Educational Technology (IET) Middleware Web Service APIs provide campus integration and identity-related
middleware. Probed 2026-08-19: the endpoint returns HTTP 200 but the body is a 1KB HTML welcome page pointing at internal
documentation — there is no machine-readable contract, no OpenAPI, and no self-service signup. Access is gated to affiliated
campus developers. Listed because the surface is real and institution-operated, not because it is consumable.'
humanURL: https://iet-ws.ucdavis.edu/api/
tags:
- Identity
- Middleware
- Integration
properties:
- type: Documentation
url: https://iet-ws.ucdavis.edu/api/
x-operator: institution
x-operator-evidence: iet-ws.ucdavis.edu resolves to 128.120.39.111 in UC Davis address space.
- aid: uc-davis:health-integration
name: UC Davis Health Systems Integration APIs
description: '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 API Manager. There is no self-service portal and no
published contract on this page: onboarding runs through sysintpool@health.ucdavis.edu or an internal ServiceNow request.
The callable FHIR surface behind it is catalogued separately as uc-davis:health-fhir-r4.'
humanURL: https://health.ucdavis.edu/systems-integration/developers
tags:
- Health
- FHIR
- Epic
- Integration
properties:
- type: Documentation
url: https://health.ucdavis.edu/systems-integration/developers
- type: Signup
url: https://health.ucdavis.edu/systems-integration/developers
x-operator: institution
x-operator-evidence: health.ucdavis.edu is under ucdavis.edu.
- aid: uc-davis:ace
name: CAES ACE API
description: '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 no ACE host resolves (ace.caes.ucdavis.edu NXDOMAIN) and
no machine-readable contract was found. Recorded as a documented but unverifiable surface — no spec was generated to fill
the gap.'
humanURL: https://computing.caes.ucdavis.edu/documentation/ace/api
tags:
- Administration
- Integration
properties:
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/ace/api
x-operator: institution
x-operator-evidence: computing.caes.ucdavis.edu is under ucdavis.edu; built by the CAES Computing Resources Unit.
- aid: uc-davis:uc-davis-access-api
name: PEAKS (CAES) — Access API
description: '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 Computing Resources Unit builds and runs at peaks.ucdavis.edu.
10 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Access
- peaks
- Campus Operations
tags_raw:
- Access
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-access-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-documents-api
name: PEAKS (CAES) — Documents API
description: 'The Documents resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application
the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at peaks.ucdavis.edu.
6 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Documents
- peaks
- Campus Operations
tags_raw:
- Documents
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-documents-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-equipment-api
name: PEAKS (CAES) — Equipment API
description: 'The Equipment resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking application
the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at peaks.ucdavis.edu.
17 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Equipment
- peaks
- Campus Operations
tags_raw:
- Equipment
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-equipment-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-keys-api
name: PEAKS (CAES) — Keys API
description: '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 Computing Resources Unit builds and runs at peaks.ucdavis.edu.
10 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Keys
- peaks
- Campus Operations
tags_raw:
- Keys
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-keys-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-keyserials-api
name: PEAKS (CAES) — KeySerials API
description: 'The KeySerials resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking
application the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at
peaks.ucdavis.edu. 11 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS
entries in this file split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software
— source at github.com/ucdavis/Peaks under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token
API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- KeySerials
- peaks
- Campus Operations
tags_raw:
- KeySerials
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-keyserials-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-people-api
name: PEAKS (CAES) — People API
description: '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 Computing Resources Unit builds and runs at peaks.ucdavis.edu.
4 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- People
- peaks
- Campus Operations
tags_raw:
- People
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-people-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-peopleadmin-api
name: PEAKS (CAES) — PeopleAdmin API
description: 'The PeopleAdmin resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking
application the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at
peaks.ucdavis.edu. 4 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries
in this file split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source
at github.com/ucdavis/Peaks under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key
issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- PeopleAdmin
- peaks
- Campus Operations
tags_raw:
- PeopleAdmin
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-peopleadmin-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-spaces-api
name: PEAKS (CAES) — Spaces API
description: '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 Computing Resources Unit builds and runs at peaks.ucdavis.edu.
6 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS entries in this file
split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software — source at github.com/ucdavis/Peaks
under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Spaces
- peaks
- Campus Operations
tags_raw:
- Spaces
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-spaces-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:uc-davis-workstations-api
name: PEAKS (CAES) — Workstations API
description: 'The Workstations resource of PEAKS (People, Equipment, Access, Keys, Space), the asset- and access-tracking
application the UC Davis College of Agricultural and Environmental Sciences Computing Resources Unit builds and runs at
peaks.ucdavis.edu. 13 operation(s). This entry is ONE TAG of a single application, not a separate API: all nine PEAKS
entries in this file split one contract (openapi/_original/uc-davis-peaks.yaml) by tag. PEAKS is UC Davis''s own software
— source at github.com/ucdavis/Peaks under MIT — so the engineering is genuinely theirs. Access requires an X-Auth-Token
API key issued to a campus team.'
humanURL: https://computing.caes.ucdavis.edu/documentation/peaks/api
baseURL: https://peaks.ucdavis.edu
tags:
- Workstations
- peaks
- Campus Operations
tags_raw:
- Workstations
- PEAKS
- Campus Operations
properties:
- type: OpenAPI
url: openapi/uc-davis-workstations-api-openapi.yml
- type: x-json-schema
url: json-schema/uc-davis-key-schema.json
- type: x-json-structure
url: json-structure/uc-davis-key-structure.json
- type: x-examples
url: examples/uc-davis-keys-list-example.json
- type: x-rules
url: rules/uc-davis-rules.yml
- type: x-vocabulary
url: vocabulary/uc-davis-vocabulary.yml
- type: x-json-ld
url: json-ld/uc-davis-context.jsonld
- type: Documentation
url: https://computing.caes.ucdavis.edu/documentation/peaks/api
- type: APIReference
url: https://peaks.ucdavis.edu/swagger/index.html
- type: x-source-repository
url: https://github.com/ucdavis/Peaks
x-operator: institution
x-application: PEAKS
x-operator-evidence: peaks.ucdavis.edu is under ucdavis.edu; info.contact.url is caeshelp.ucdavis.edu; source repo github.com/ucdavis/Peaks.
- aid: uc-davis:escholarship-tenant
name: eScholarship — UC Davis unit (tenant)
description: '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 deposits and the DOIs are UC Davis''s; the platform and
the contract are the California Digital Library''s, and the OAI-PMH endpoint at escholarship.org/oai serves all ten UC
campuses from a single set (''everything'') with no UC Davis setSpec. Recorded as a TENANT relationship: this is a real
institutional fact and one of the few programmable research surfaces UC Davis has, but no eScholarship or CDL contract
is saved under this slug. Note escholarship.org answers automated clients with an AWS WAF challenge (HTTP 202, zero bytes),
so the human landing page could not be status-verified — the OAI-PMH verbs did answer 200.'
humanURL: https://escholarship.org/uc/ucd
tags:
- Research Repository
- Open Access
- OAI-PMH
- Tenant
x-operator: tenant
x-operator-evidence: escholarship.org is operated by the California Digital Library and shared across all UC campuses; it
is not under ucdavis.edu.
x-platform-operator: California Digital Library (University of California)
properties:
- type: APIReference
url: https://escholarship.org/oai?verb=Identify
x-audit-reconciliation: 'audit-university-contracts.py grades the bare host escholarship.org as VENDOR because three institutions
in the cohort point at it. That is correct about the HOST and does not conflict with the tenant label here: the surface
recorded is the UC Davis unit path /uc/ucd, an institution-specific account on a shared platform, which is the definition
of tenant. No CDL or eScholarship contract is saved under this slug either way. Do not ''correct'' this back to a saved
contract.'
- aid: uc-davis:library-primo-tenant
name: UC Davis Library discovery — Ex Libris Primo (tenant)
description: 'Library discovery at
# --- truncated at 32 KB (40 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/uc-davis/refs/heads/main/apis.yml
Every provider here is available over the APIs.io API and to AI agents over MCP.
Kin Score
How this is scored →