Tsinghua University Agentic Access

generated: '2026-08-19'
method: generated
source: >-
  openapi/_original/tsinghua-tuna-mirror-status.yaml,
  openapi/_original/tsinghua-tuna-iso-catalog.yaml,
  openapi/_original/tsinghua-identity-federation.yaml
x-operator: institution
description: >-
  Recommended x-agentic-access execution contracts, classified heuristically from this
  institution's OpenAPIs. A governance starting point for exposing these surfaces to AI agents —
  review and bind audience per deployment. See research/curity/agentic-governance/.
  Every operation here is unauthenticated and read-only, which makes this an unusually simple
  case; the one real hazard is not consequence but reachability, recorded per operation below.
summary:
  operations: 4
  by_action_class:
    connected: 4
  by_consequence:
    read: 4
  human_in_the_loop_required: 0
operations:
- path: /static/tunasync.json
  method: get
  operationId: getMirrorSyncStatus
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
  x-agent-hazard: >-
    The origin answers 403 with an HTML denial page to requests carrying a desktop-browser
    User-Agent and 200 to a plain tool User-Agent. An agent that spoofs a browser to look
    human will be denied; an agent that identifies itself plainly will succeed.
- path: /static/status/isoinfo.json
  method: get
  operationId: getMirrorIsoCatalog
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: optional
    token:
      max-ttl: 3600
    audit: none
  x-agent-hazard: >-
    Same User-Agent filter as the status endpoint. Response is 461KB; agents should expect to
    stream or filter rather than load whole.
- path: /idp/shibboleth
  method: get
  operationId: getSamlFederationMetadata
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: none
    token:
      max-ttl: 86400
    audit: none
  x-agent-hazard: >-
    The document carries no validUntil, no cacheDuration and no XML signature, so an agent has
    no published refresh interval and no way to verify the document has not been altered in
    transit. Treat as advisory, not as a trust anchor.
- path: /idp/profile/SAML2/Redirect/SSO
  method: get
  operationId: samlRedirectSingleSignOn
  x-agentic-access:
    action-class: connected
    consequence: read
    subject: required
    human-in-the-loop: required
    token:
      max-ttl: 300
    audit: required
  x-agent-hazard: >-
    A SAML authentication endpoint, not a data endpoint. It is listed for discoverability only.
    An agent must never drive this flow on a human's behalf: it authenticates a natural person
    into a university identity estate and requires a federation relationship an agent cannot hold.