École Normale Supérieure de Lyon
École Normale Supérieure de Lyon (ENS de Lyon) is a French public research and higher-education institution in Lyon, ranked #187 in the QS World University Rankings 2025. Its primary public, machine-readable developer footprint is its open-access institutional repository, HAL-ENS-LYON (ens-lyon.hal.science), which is part of the national HAL (Hyper Articles en Ligne) open archive. That platform exposes the publication metadata of ENS de Lyon through HAL's shared, well-documented APIs — an OAI-PMH endpoint scoped to the ens-lyon collection plus HAL's Search, Reference, and SWORD deposit APIs hosted at api.archives-ouvertes.fr. ENS de Lyon does not publish its own dedicated, branded developer portal; the institutional GitHub organization exists but currently has no public repositories.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles École Normale Supérieure de Lyon the way a machine reads it — 9 machine-readable artifacts across 4 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 — École Normale Supérieure de Lyon scores 24.7/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 École Normale Supérieure de Lyon
Each block below is one kind of artifact we hold for École Normale Supérieure de Lyon. 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 4
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.
HAL-ENS-LYON OAI-PMH
OAI-PMH 2.0 metadata harvesting endpoint scoped to the ENS de Lyon (ens-lyon) collection of the national HAL open archive. Exposes the institution's open-access scholarly public...
HAL Search API (ens-lyon collection)
HAL's Solr-backed REST/Search API for querying publications. Can be scoped to the ENS de Lyon collection (e.g. /search/ens-lyon/) to retrieve ENS de Lyon research output as JSON...
HAL Reference (Référentiels) API
HAL's reference-data API for querying controlled vocabularies and authorities (authors, structures/labs, journals, domains, ANR projects) used across HAL, including ENS de Lyon'...
HAL SWORD Deposit API
HAL's SWORD protocol API for programmatic deposit of documents into HAL, including into the ENS de Lyon collection. Requires authenticated HAL credentials.
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.
Ens Lyon 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.
Ens Lyon 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.
Ens Lyon Context
JSON-LDSecurity Posture 1
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.
Resources
Every other property we hold for École Normale Supérieure de Lyon — 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
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 2
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/ens-lyon · machine-readable index on apis.io