ES·pera API

ES·pera is an independent Spanish-language observatory that gathers scattered official Spanish National Health System (SNS) and autonomous-community publications on healthcare waiting lists and hospital activity, and republishes them as comparable, provenance-preserving open data. It exposes a free, open, unauthenticated read-only REST API (OpenAPI 3.1 at /api/v1) covering hospital entities, national activity metrics and autonomous waiting-list observations, served from immutable content-addressed data releases. Discovery is via an RFC 9727 API catalog, an llms.txt, and a provider-published Agent Skill; there is no MCP server, no A2A agent card, and no client SDK.

ES·pera API publishes 3 API contracts indexed on the APIs.io network: Estado API, Hospitales API, and Listas autonómicas API. Tagged areas include Healthcare, Open Data, Waiting Lists, hospital activity, and Spain.

The ES·pera API catalog on APIs.io includes 1 Spectral governance ruleset.

ES·pera API’s developer surface includes documentation, authentication, changelog, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

33.1/100 thin ▬ flat Agent 34/100 agent ready Front door AI 1/6 silent Heartbeat 100/100 alive Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessOpen

1 published contract 1 Agent Skills

Healthcare Open DataWaiting Listshospital activitySpain Public Sector Government Data SNS

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 33.1/100 · thin

Contract Quality 10.0 / 21

Developer Ergonomics 7.7 / 17

Access Clarity 0.0 / 17

Operational Transparency 3.7 / 11

Contract Governance 1.4 / 10

Discoverability 5.8 / 9

Regulatory Posture 1.6 / 15

Agent readiness — 34/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Government & Public Sector regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/es-pera/"><img src="https://apis.io/badge/es-pera/card.svg" alt="ES·pera API on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points Ask about this →
Contract Quality scores 46.9 — up to +13.3 composite points Ask about this →
Developer Ergonomics scores 45.2 — up to +11.0 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/es-pera/apis.yml: open an issue on github.com/api-evangelist/es-pera to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Open Data Portals (CKAN / DCAT)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent Skills

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

ES·pera API Estado API

Salud y releases fijadas por el despliegue.

ES·pera API Hospitales API

Métricas, directorio y detalle hospitalario nacional.

ES·pera API Listas autonómicas API

Catálogo acotado de listas de espera publicadas por las comunidades autónomas.

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

es-pera-public-data

AGENT SKILL

ES·pera API pricing

Rate limits

global-anonymous: 120 60s
waiting-facets-observations: 20 60s

Rate-limit details →

Pricing Plans 1

Published pricing tiers and plan structures.

ES·pera API Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

ES·pera API Rate Limits

2 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

ES·pera API API Rules

41 rules · 38 error-severity 1 warn-severity 2 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

ES·pera API Openapi Overlay

5 actions · update · es-pera-openapi.json

GENERATED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

ES·pera API Authentication

0 schemes

SECURITY

ES·pera API Domain Security

TLSv1.3

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

AgentSkill

AgentSkill

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Conformance

ErrorCatalog

Lifecycle

DataModel

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

Plans

Plans

Company 2

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

name: ES·pera API
description: ES·pera is an independent Spanish-language observatory that gathers scattered official Spanish National Health
  System (SNS) and autonomous-community publications on healthcare waiting lists and hospital activity, and republishes them
  as comparable, provenance-preserving open data. It exposes a free, open, unauthenticated read-only REST API (OpenAPI 3.1
  at /api/v1) covering hospital entities, national activity metrics and autonomous waiting-list observations, served from
  immutable content-addressed data releases. Discovery is via an RFC 9727 API catalog, an llms.txt, and a provider-published
  Agent Skill; there is no MCP server, no A2A agent card, and no client SDK.
url: https://raw.githubusercontent.com/api-evangelist/es-pera/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-13'
  method: derived
image: https://es-pera.org/favicon-espera.svg
created: '2026-09-13'
modified: '2026-10-06'
specificationVersion: '0.21'
tags:
- Healthcare
- Open Data
- Waiting Lists
- hospital activity
- Spain
- Public Sector
- Government Data
- SNS
tags_raw:
- healthcare
- open data
- waiting lists
- hospital activity
- Spain
- public sector
- government data
- SNS
apis:
- aid: es-pera:es-pera-estado-api
  name: ES·pera API Estado API
  description: Salud y releases fijadas por el despliegue.
  humanURL: https://es-pera.org/metodologia/api/
  baseURL: https://es-pera.org/api/v1
  tags:
  - Estado
  properties:
  - type: OpenAPI
    url: openapi/es-pera-estado-api-openapi.yml
  - type: Documentation
    url: https://es-pera.org/metodologia/api/
  - type: APIReference
    url: https://es-pera.org/metodologia/api/
- aid: es-pera:es-pera-hospitales-api
  name: ES·pera API Hospitales API
  description: Métricas, directorio y detalle hospitalario nacional.
  humanURL: https://es-pera.org/metodologia/api/
  baseURL: https://es-pera.org/api/v1
  tags:
  - Hospitales
  properties:
  - type: OpenAPI
    url: openapi/es-pera-hospitales-api-openapi.yml
  - type: Documentation
    url: https://es-pera.org/metodologia/api/
  - type: APIReference
    url: https://es-pera.org/metodologia/api/
- aid: es-pera:es-pera-listas-auton-micas-api
  name: ES·pera API Listas autonómicas API
  description: Catálogo acotado de listas de espera publicadas por las comunidades autónomas.
  humanURL: https://es-pera.org/metodologia/api/
  baseURL: https://es-pera.org/api/v1
  tags:
  - Listas autonómicas
  properties:
  - type: OpenAPI
    url: openapi/es-pera-listas-auton-micas-api-openapi.yml
  - type: Documentation
    url: https://es-pera.org/metodologia/api/
  - type: APIReference
    url: https://es-pera.org/metodologia/api/
maintainers:
- FN: ES·pera API
  url: https://es-pera.org/
x-source:
  via: apis.io/add es-pera 1d7101bd, parked no_consumable_surface
  fetched: '2026-09-13'
  note: 'Enrichment corrected the prior round: the declared /data/ base 404s, but a real first-party OpenAPI 3.1 (9 read-only
    ops) is live at es-pera.org/openapi.json with servers https://es-pera.org/api/v1. baseURL and pointers corrected to the
    real API.'
common:
- url: https://es-pera.org/actualizaciones/feed.atom
  type: BlogRSS
- type: Overlay
  url: overlays/es-pera-openapi-overlay.yaml
- type: DomainSecurity
  url: security/es-pera-domain-security.yml
- type: Website
  url: https://es-pera.org/
- type: DeveloperPortal
  url: https://es-pera.org/metodologia/
- type: Documentation
  url: https://es-pera.org/metodologia/
- type: LLMsTxt
  url: llms/es-pera-llms.txt
- type: WellKnown
  url: well-known/es-pera-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Authentication
  url: authentication/es-pera-authentication.yml
- type: Conventions
  url: conventions/es-pera-conventions.yml
- type: RateLimits
  url: rate-limits/es-pera-rate-limits.yml
- type: Conformance
  url: conformance/es-pera-conformance.yml
- type: ErrorCatalog
  url: errors/es-pera-problem-types.yml
- type: Lifecycle
  url: lifecycle/es-pera-lifecycle.yml
- type: DataModel
  url: data-model/es-pera-data-model.yml
- type: Plans
  url: plans/es-pera-plans-pricing.yml
- type: ChangeLog
  url: changelog/es-pera-changelog.yml
- type: X-MCPServerCandidate
  url: mcp/es-pera-mcp.yml
x-enrichment:
  date: '2026-09-13'
  status: enriched
  artifacts_added: 19
  pass: local-v3

ES·pera API — frequently asked questions

Does ES·pera API have an API?

Yes. APIs.io lists 3 APIs from ES·pera API, including ES·pera API Estado API, ES·pera API Hospitales API and ES·pera API Listas autonómicas API.

Is there an OpenAPI specification for the ES·pera API?

Yes. APIs.io indexes 3 OpenAPI specifications for ES·pera API, each linked for download from this page.

How do I authenticate with the ES·pera API?

ES·pera API uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as ES·pera API Authentication.

Is the ES·pera API ready for AI agents?

ES·pera API has a Kin Score of 33.1 out of 100 (thin) and an Agent Readiness score of 33.7 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/es-pera"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/es-pera/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/es-pera/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.