University of Chile
The University of Chile (Universidad de Chile, UChile) is the country's oldest public university, founded in 1842 in Santiago, and is ranked #139 in the QS World University Rankings 2025. Its public, machine-readable footprint is centered on research and scholarly infrastructure rather than a single branded developer portal: a Dataverse-based research data repository (datos.uchile.cl) that exposes the standard Dataverse REST API, and a DSpace institutional repository (repositorio.uchile.cl) that exposes an OAI-PMH interface for metadata harvesting. The university also maintains official open-source GitHub organizations for its Open edX online-education platform. No general-purpose, self-service developer program with API keys was confirmed; access is via open standards and open data.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles University of Chile the way a machine reads it — 41 machine-readable artifacts across 25 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 — University of Chile scores 34.6/100 (thin), with a separate agent-readiness read of 39/100 (agent aware). 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 University of Chile
Each block below is one kind of artifact we hold for University of Chile. 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 25
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.
Repositorio Academico OAI-PMH
The University of Chile institutional repository (Repositorio Academico), managed by SISIB and built on DSpace, exposes an OAI-PMH 2.0 interface for harvesting Dublin Core / met...
University of Chile Access API
The Access API from University of Chile — 20 operation(s) for access.
University of Chile Admin API
The Admin API from University of Chile — 120 operation(s) for admin.
University of Chile Batch API
The Batch API from University of Chile — 3 operation(s) for batch.
University of Chile Builtin Users API
The Builtin Users API from University of Chile — 4 operation(s) for builtin users.
University of Chile Datasets API
The Datasets API from University of Chile — 62 operation(s) for datasets.
University of Chile Datatags API
The Datatags API from University of Chile — 1 operation(s) for datatags.
University of Chile Dataverses API
The Dataverses API from University of Chile — 28 operation(s) for dataverses.
University of Chile Edit API
The Edit API from University of Chile — 1 operation(s) for edit.
University of Chile Files API
The Files API from University of Chile — 13 operation(s) for files.
University of Chile Harvest API
The Harvest API from University of Chile — 7 operation(s) for harvest.
University of Chile Inbox API
The Inbox API from University of Chile — 1 operation(s) for inbox.
University of Chile Info API
The Info API from University of Chile — 40 operation(s) for info.
University of Chile Ingest API
The Ingest API from University of Chile — 1 operation(s) for ingest.
University of Chile Licenses API
The Licenses API from University of Chile — 6 operation(s) for licenses.
University of Chile Mail API
The Mail API from University of Chile — 1 operation(s) for mail.
University of Chile Meta API
The Meta API from University of Chile — 2 operation(s) for meta.
University of Chile Metadatablocks API
The Metadatablocks API from University of Chile — 2 operation(s) for metadatablocks.
University of Chile Mydata API
The Mydata API from University of Chile — 1 operation(s) for mydata.
University of Chile Notifications API
The Notifications API from University of Chile — 6 operation(s) for notifications.
University of Chile Pids API
The Pids API from University of Chile — 4 operation(s) for pids.
University of Chile Roles API
The Roles API from University of Chile — 2 operation(s) for roles.
University of Chile Search API
The Search API from University of Chile — 1 operation(s) for search.
University of Chile Users API
The Users API from University of Chile — 8 operation(s) for users.
University of Chile Workflows API
The Workflows API from University of Chile — 1 operation(s) for workflows.
Scroll within the panel for all 25 ·
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.
University Of Chile 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.
Semantic 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.
University Of Chile 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.
University of Chile API Rules
SPECTRALUniversity of Chile API Rules
SPECTRALJSON Schema 4
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.
Dataverse DataFile
JSON SCHEMADataverse Dataset
JSON SCHEMADataverse Collection
JSON SCHEMADataverse Search Result Item (dataset)
JSON SCHEMAJSON Structure 2
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.
University Of Chile Dataset Structure
JSON STRUCTUREUniversity Of Chile Dataverse 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 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.
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 University of Chile — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-chile · machine-readable index on apis.io