University of North Carolina at Chapel Hill
The University of North Carolina at Chapel Hill is a leading public research university in Chapel Hill, North Carolina, United States, ranked #155 in the QS World University Rankings 2025. Its public developer and API footprint is centered on research and open-data infrastructure rather than a single unified developer portal: UNC Dataverse exposes a live, documented native REST API for social-science and research data (running Dataverse 6.8), the campus ArcGIS Hub open-data site publishes geospatial data through DCAT-US feeds and ArcGIS REST services, and the UNC Libraries software-development team maintains a public GitHub organization with the box-c Digital Collections Repository and other open-source tooling. Most administrative and student-information-system APIs (such as the Facilities SPOTS REST API and campus single sign-on) are gated behind Onyen/Shibboleth authentication.
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 North Carolina at Chapel Hill the way a machine reads it — 53 machine-readable artifacts across 39 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 North Carolina at Chapel Hill scores 39.2/100 (thin), 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 University of North Carolina at Chapel Hill
Each block below is one kind of artifact we hold for University of North Carolina at Chapel Hill. 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 39
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.
UNC GIS Open Data Hub
UNC-Chapel Hill's ArcGIS Hub open-data site publishing geospatial and institutional datasets. Data is programmatically accessible via ArcGIS Hub DCAT-US 1.1 catalog feeds and th...
UNC Libraries Digital Collections Repository (box-c)
The UNC Libraries Digital Collections Repository, powered by the open-source box-c application maintained by the UNC Libraries software development team on GitHub. Provides web ...
Facilities SPOTS REST API
REST API for the Space Planning and Occupancy Tracking System (SPOTS) provided by UNC Facilities Services for campus space and occupancy data. Documentation is gated behind UNC ...
University of North Carolina at Chapel Hill Access API
The Access API from University of North Carolina at Chapel Hill — 23 operation(s) for access.
University of North Carolina at Chapel Hill addFilesToDataset API
Uploads a set of files to a dataset
University of North Carolina at Chapel Hill addFileToDataset API
Uploads a file for a dataset
University of North Carolina at Chapel Hill addGlobusFilesToDataset API
Uploads a Globus file for a dataset
University of North Carolina at Chapel Hill Admin API
The Admin API from University of North Carolina at Chapel Hill — 127 operation(s) for admin.
University of North Carolina at Chapel Hill Batch API
The Batch API from University of North Carolina at Chapel Hill — 3 operation(s) for batch.
University of North Carolina at Chapel Hill Builtin Users API
The Builtin Users API from University of North Carolina at Chapel Hill — 4 operation(s) for builtin users.
University of North Carolina at Chapel Hill Datasetfields API
The Datasetfields API from University of North Carolina at Chapel Hill — 1 operation(s) for datasetfields.
University of North Carolina at Chapel Hill Datasets API
The Datasets API from University of North Carolina at Chapel Hill — 94 operation(s) for datasets.
University of North Carolina at Chapel Hill Datatags API
The Datatags API from University of North Carolina at Chapel Hill — 1 operation(s) for datatags.
University of North Carolina at Chapel Hill DataverseFeaturedItems API
The DataverseFeaturedItems API from University of North Carolina at Chapel Hill — 1 operation(s) for dataversefeatureditems.
University of North Carolina at Chapel Hill Dataverses API
The Dataverses API from University of North Carolina at Chapel Hill — 40 operation(s) for dataverses.
University of North Carolina at Chapel Hill Edit API
The Edit API from University of North Carolina at Chapel Hill — 1 operation(s) for edit.
University of North Carolina at Chapel Hill ExternalTools API
The ExternalTools API from University of North Carolina at Chapel Hill — 2 operation(s) for externaltools.
University of North Carolina at Chapel Hill Files API
The Files API from University of North Carolina at Chapel Hill — 21 operation(s) for files.
University of North Carolina at Chapel Hill Harvest API
The Harvest API from University of North Carolina at Chapel Hill — 7 operation(s) for harvest.
University of North Carolina at Chapel Hill Inbox API
The Inbox API from University of North Carolina at Chapel Hill — 1 operation(s) for inbox.
University of North Carolina at Chapel Hill Info API
The Info API from University of North Carolina at Chapel Hill — 50 operation(s) for info.
University of North Carolina at Chapel Hill Ingest API
The Ingest API from University of North Carolina at Chapel Hill — 1 operation(s) for ingest.
University of North Carolina at Chapel Hill Licenses API
The Licenses API from University of North Carolina at Chapel Hill — 6 operation(s) for licenses.
University of North Carolina at Chapel Hill Localcontexts API
The Localcontexts API from University of North Carolina at Chapel Hill — 2 operation(s) for localcontexts.
University of North Carolina at Chapel Hill Logout API
The Logout API from University of North Carolina at Chapel Hill — 1 operation(s) for logout.
University of North Carolina at Chapel Hill Mail API
The Mail API from University of North Carolina at Chapel Hill — 1 operation(s) for mail.
University of North Carolina at Chapel Hill Meta API
The Meta API from University of North Carolina at Chapel Hill — 2 operation(s) for meta.
University of North Carolina at Chapel Hill Metadatablocks API
The Metadatablocks API from University of North Carolina at Chapel Hill — 2 operation(s) for metadatablocks.
University of North Carolina at Chapel Hill Mydata API
The Mydata API from University of North Carolina at Chapel Hill — 2 operation(s) for mydata.
University of North Carolina at Chapel Hill Notifications API
The Notifications API from University of North Carolina at Chapel Hill — 8 operation(s) for notifications.
University of North Carolina at Chapel Hill Pids API
The Pids API from University of North Carolina at Chapel Hill — 6 operation(s) for pids.
University of North Carolina at Chapel Hill replaceFilesInDataset API
Replace a file to a dataset
University of North Carolina at Chapel Hill Roles API
The Roles API from University of North Carolina at Chapel Hill — 3 operation(s) for roles.
University of North Carolina at Chapel Hill saveAuxiliaryFileWithVersion API
Save Auxiliary File With Version
University of North Carolina at Chapel Hill Search API
The Search API from University of North Carolina at Chapel Hill — 2 operation(s) for search.
University of North Carolina at Chapel Hill Sendfeedback API
The Sendfeedback API from University of North Carolina at Chapel Hill — 1 operation(s) for sendfeedback.
University of North Carolina at Chapel Hill uploadDatasetLogo API
Uploads a logo for a dataset
University of North Carolina at Chapel Hill Users API
The Users API from University of North Carolina at Chapel Hill — 10 operation(s) for users.
University of North Carolina at Chapel Hill Workflows API
The Workflows API from University of North Carolina at Chapel Hill — 1 operation(s) for workflows.
Scroll within the panel for all 39 ·
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.
FinOps 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.
Spectral 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 2
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 Dataset
JSON SCHEMADataverse Info Version Response
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.
Examples 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.
University Of North Carolina At Chapel Hill Agentic Access
541 operations · 258 acting · 7 human-in-the-loop
AGENTICResources
Every other property we hold for University of North Carolina at Chapel Hill — 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/university-of-north-carolina-at-chapel-hill · machine-readable index on apis.io