RIPE NCC
RIPE NCC is the Regional Internet Registry for Europe, the Middle East and parts of Central Asia. It is a not‑for‑profit membership association that allocates IP address space, manages the DNS root for the .ripe region, and provides a range of services to support the RIPE community, including RIPE Atlas measurements, training, and policy development.
RIPE NCC is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Internet, Regional Internet Registry, Not-for-profit, and IP Allocation.
The RIPE NCC catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
RIPE NCC’s developer surface includes changelog, getting-started guide, support, engineering blog, signup flow, and 29 more developer resources.
Kin Score
Used by apps
1 of the reference apps in Applications, across 1 category, integrate with this provider, read from each app's own code, build or integrations page.
- Duolicious Dating
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
RIPE Database REST API
RIPE Database RESTful API
RIPE NCC API
RIPE NCC API as documented publicly: 28 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider's own document.
Terms of Service 1
What its API terms permit and prohibit, quoted from its own page.
Privacy & Data 1
Its role, the data it processes, retention and transfers, quoted from its own privacy page.
Eligibility 1
Who may sign up and where, quoted from its own terms.
Data License 1
How its data and outputs may be reused, quoted from its own terms.
Semantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Ripe Ncc Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.
RIPE NCC API Rules
SPECTRALOpenAPI 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.
JSON Schema 6
Standalone JSON Schema definitions for this provider's data models.
GetSourceObjecttypeKeyVersionsResponse
JSON SCHEMAPostSourceObjecttypeRequest
JSON SCHEMAPostSourceObjecttypeResponse
JSON SCHEMAPutSourceObjecttypeKeyRequest
JSON SCHEMAPutSourceObjecttypeKeyResponse
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 10
Authentication, authorization, and security posture
Scroll for all 10
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
Source (apis.yml)
RIPE NCC API — frequently asked questions
Does RIPE NCC have an API?
Yes. APIs.io lists 2 APIs from RIPE NCC, including RIPE Database REST API and RIPE NCC API.
Is there an OpenAPI specification for the RIPE NCC API?
Yes. APIs.io indexes 1 OpenAPI specification for RIPE NCC, each linked for download from this page.
How do I authenticate with the RIPE NCC API?
RIPE NCC uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as RIPE NCC Authentication.
Is the RIPE NCC API ready for AI agents?
RIPE NCC has a Kin Score of 39.9 out of 100 (developing) and an Agent Readiness score of 14.3 (agent-aware), scored by API Evangelist on 2026-11-21.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.