ETH Zurich – Swiss Federal Institute of Technology
ETH Zurich (Eidgenössische Technische Hochschule Zürich) is a public science and technology university founded in 1855, ranked #7 in the QS World University Rankings 2025. Its most visible public developer footprint is the ETH Library API Platform, an Apigee-managed developer portal exposing six documented OpenAPI 3.0 REST APIs (Discovery, ETHorama, Geo, Persons, Research Collection, Vector) for the library's open bibliographic, georeferenced, and research-output data. The ETH Zurich Research Collection additionally offers a public OAI-PMH harvesting interface, and the eth-library GitHub organization publishes the OpenAPI specifications and related open-source tooling. All REST APIs require a free one-time registration to obtain an API key.
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 ETH Zurich – Swiss Federal Institute of Technology the way a machine reads it — 49 machine-readable artifacts across 35 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 — ETH Zurich – Swiss Federal Institute of Technology scores 49.0/100 (developing), 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 ETH Zurich – Swiss Federal Institute of Technology
Each block below is one kind of artifact we hold for ETH Zurich – Swiss Federal Institute of Technology. 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 35
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.
ETH Zurich – Swiss Federal Institute of Technology bitstreams API
The bitstreams API from ETH Zurich – Swiss Federal Institute of Technology — 4 operation(s) for bitstreams.
ETH Zurich – Swiss Federal Institute of Technology collections API
The collections API from ETH Zurich – Swiss Federal Institute of Technology — 3 operation(s) for collections.
ETH Zurich – Swiss Federal Institute of Technology communities API
The communities API from ETH Zurich – Swiss Federal Institute of Technology — 5 operation(s) for communities.
ETH Zurich – Swiss Federal Institute of Technology Content Item API
The Content Item API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for content item.
ETH Zurich – Swiss Federal Institute of Technology Contributors API
The Contributors API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for contributors.
ETH Zurich – Swiss Federal Institute of Technology Core API
The Core API from ETH Zurich – Swiss Federal Institute of Technology — 9 operation(s) for core.
ETH Zurich – Swiss Federal Institute of Technology Discover API
The Discover API from ETH Zurich – Swiss Federal Institute of Technology — 7 operation(s) for discover.
ETH Zurich – Swiss Federal Institute of Technology Dossier API
The Dossier API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for dossier.
ETH Zurich – Swiss Federal Institute of Technology Dossiers API
The Dossiers API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for dossiers.
ETH Zurich – Swiss Federal Institute of Technology e-maps API
The e-maps API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for e-maps.
ETH Zurich – Swiss Federal Institute of Technology E-Pics items API
The E-Pics items API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for e-pics items.
ETH Zurich – Swiss Federal Institute of Technology e-rara API
The e-rara API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for e-rara.
ETH Zurich – Swiss Federal Institute of Technology ETH Research Collection API V2 API
The ETH Research Collection API V2 API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for eth research collection api v2.
ETH Zurich – Swiss Federal Institute of Technology Geo Container API
The Geo Container API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for geo container.
ETH Zurich – Swiss Federal Institute of Technology geo-topics API
The geo-topics API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for geo-topics.
ETH Zurich – Swiss Federal Institute of Technology Geodata API
The Geodata API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for geodata.
ETH Zurich – Swiss Federal Institute of Technology handle API
The handle API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for handle.
ETH Zurich – Swiss Federal Institute of Technology Information about a person API
The Information about a person API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for information about a person.
ETH Zurich – Swiss Federal Institute of Technology items API
The items API from ETH Zurich – Swiss Federal Institute of Technology — 5 operation(s) for items.
ETH Zurich – Swiss Federal Institute of Technology List of persons API
The List of persons API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for list of persons.
ETH Zurich – Swiss Federal Institute of Technology Locations API
The Locations API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for locations.
ETH Zurich – Swiss Federal Institute of Technology Maps API
The Maps API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for maps.
ETH Zurich – Swiss Federal Institute of Technology Places API
The Places API from ETH Zurich – Swiss Federal Institute of Technology — 3 operation(s) for places.
ETH Zurich – Swiss Federal Institute of Technology Poi API
The Poi API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for poi.
ETH Zurich – Swiss Federal Institute of Technology Poi items API
The Poi items API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for poi items.
ETH Zurich – Swiss Federal Institute of Technology Pois API
The Pois API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for pois.
ETH Zurich – Swiss Federal Institute of Technology provenance items API
The provenance items API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for provenance items.
ETH Zurich – Swiss Federal Institute of Technology Publication places API
The Publication places API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for publication places.
ETH Zurich – Swiss Federal Institute of Technology Route API
The Route API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for route.
ETH Zurich – Swiss Federal Institute of Technology Routes API
The Routes API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for routes.
ETH Zurich – Swiss Federal Institute of Technology search API
The search API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for search.
ETH Zurich – Swiss Federal Institute of Technology Search Portal resources API
The Search Portal resources API from ETH Zurich – Swiss Federal Institute of Technology — 2 operation(s) for search portal resources.
ETH Zurich – Swiss Federal Institute of Technology Suggestion API
The Suggestion API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for suggestion.
ETH Zurich – Swiss Federal Institute of Technology Topics API
The Topics API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for topics.
ETH Zurich – Swiss Federal Institute of Technology Util API
The Util API from ETH Zurich – Swiss Federal Institute of Technology — 1 operation(s) for util.
Scroll within the panel for all 35 ·
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.
Eth Zurich 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.
Eth Zurich 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.
Eth Zurich 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 1
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.
ETH Research Collection Item
JSON SCHEMAJSON Structure 1
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.
Eth Zurich Research Collection Item 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.
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.
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 ETH Zurich – Swiss Federal Institute of Technology — 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 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/eth-zurich · machine-readable index on apis.io