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 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.2/100 thin Agent 17/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 APIs

Company InternetRegional Internet RegistryNot-for-profitIP Allocation

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 38.2/100 · thin

Contract Quality 5.1 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 7.2 / 17

Operational Transparency 5.2 / 11

Contract Governance 2.0 / 10

Discoverability 5.0 / 9

Regulatory Posture 5.9 / 15

Agent readiness — 17/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 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 0 / 5

Distinct Operations 0 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/ripe-ncc/"><img src="https://apis.io/badge/ripe-ncc/card.svg" alt="RIPE NCC 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)

12 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 24.0 — up to +19.0 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points
Access Clarity scores 42.1 — up to +11.6 composite points

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.

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/ripe-ncc/apis.yml: open an issue on github.com/api-evangelist/ripe-ncc 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 →

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.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Ripe Ncc Context

22 classes · 3 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

RIPE NCC API Rules

9 rules · 8 errors 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetSourceObjecttypeKeyVersionsResponse

1 properties

JSON SCHEMA

GetSourceObjecttypeKeyVersionsVersionnumberResponse

1 properties

JSON SCHEMA

PostSourceObjecttypeRequest

1 properties

JSON SCHEMA

PostSourceObjecttypeResponse

1 properties

JSON SCHEMA

PutSourceObjecttypeKeyRequest

1 properties

JSON SCHEMA

PutSourceObjecttypeKeyResponse

1 properties

JSON SCHEMA

Security Posture 3

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

Ripe Ncc Authentication

0 schemes

SECURITY

Ripe Ncc Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Ripe Ncc Vulnerability Disclosure

security.txt · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Ripe Ncc Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 10

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

SecurityTxt

SecurityTxt

SecurityTxt

SecurityTxt

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Scroll for all 10

Operate 3

Status, limits, changes, and where to get help

StatusPage

StatusPage

ChangeLog

ChangeLog

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: ripe-ncc
name: RIPE NCC
description: 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.
url: https://artifacts.apis.io/ripe-ncc/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Company
- Internet
- Regional Internet Registry
- Not-for-profit
- IP Allocation
image: https://www.ripe.net/static/images/ripe-ncc-logo-2025.svg
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: SecurityTxt
  url: well-known/ripe-ncc-trust-security.txt
- type: SecurityTxt
  url: well-known/ripe-ncc-status-security.txt
- type: Spectral
  url: rules/ripe-ncc-rules.yml
- type: JSONLD
  url: json-ld/ripe-ncc-context.jsonld
- type: Vocabulary
  url: vocabulary/ripe-ncc-vocabulary.yml
- type: DataModel
  url: data-model/ripe-ncc-data-model.yml
- type: Security
  url: https://www.ripe.net/about-us/support/contact/responsible-disclosure-policy/
- type: Conformance
  url: conformance/ripe-ncc-conformance.yml
- type: SecurityTxt
  url: well-known/ripe-ncc-security.txt
- type: SecurityTxt
  url: well-known/ripe-ncc-ripe-security.txt
- type: SecurityTxt
  url: well-known/ripe-ncc-labs-security.txt
- type: SecurityTxt
  url: well-known/ripe-ncc-apps-security.txt
- type: WellKnown
  url: well-known/ripe-ncc-well-known.yml
- type: Hosts
  url: hosts/ripe-ncc-hosts.yml
- type: Vendors
  url: vendors/ripe-ncc-vendors.yml
- type: TrustCenter
  url: https://trust.ripe.net/
- type: StatusPage
  url: https://status.ripe.net/
- type: Newsroom
  url: https://www.ripe.net/about-us/news/
- type: ChangeLog
  url: https://www.ripe.net/manage-ips-and-asns/db/release-notes/
- type: GettingStarted
  url: https://docs.db.ripe.net/RIPE-Database-Mirror/Setup-RIPE-Database-Mirror/
- type: VulnerabilityDisclosure
  url: security/ripe-ncc-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/ripe-ncc-domain-security.yml
- type: Website
  url: https://ripe.net/
- type: DeveloperPortal
  url: https://www.ripe.net/publications/documentation/developer-documentation/
- type: Support
  url: https://www.ripe.net/about-us/support/
- type: Blog
  url: https://labs.ripe.net/
- type: GitHubOrganization
  url: https://github.com/RIPE-NCC
- type: SignUp
  url: https://www.ripe.net/membership/member-support/become-a-member/
- type: TermsOfService
  url: https://www.ripe.net/about-us/legal/terms-of-service/
- type: PrivacyPolicy
  url: https://www.ripe.net/about-us/legal/ripe-ncc-privacy-statement/
apis:
- name: RIPE Database REST API
  description: RIPE Database RESTful API
  humanURL: https://apps.db.ripe.net/docs/Update-Methods/RESTful-API/
  aid: ripe-ncc:ripe-database-rest-api
- aid: ripe-ncc:ripe-ncc-api
  name: RIPE NCC API
  description: '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.'
  humanURL: https://docs.db.ripe.net/Update-Methods/RESTful-API
  baseURL: https://rest.db.ripe.net
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/ripe-ncc-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/ripe-ncc-put-source-objecttype-key-response-schema.json
  - type: JSONSchema
    url: json-schema/ripe-ncc-get-source-objecttype-key-versions-response-schema.json
  - type: JSONSchema
    url: json-schema/ripe-ncc-put-source-objecttype-key-request-schema.json
  - type: JSONSchema
    url: json-schema/ripe-ncc-get-source-objecttype-key-versions-versionnumber-response-schema.json
  - type: JSONSchema
    url: json-schema/ripe-ncc-post-source-objecttype-request-schema.json
  - type: JSONSchema
    url: json-schema/ripe-ncc-post-source-objecttype-response-schema.json
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: Documentation page lists the RIPE Database RESTful API but no machine‑readable OpenAPI/AsyncAPI/GraphQL spec is
    provided.
  evidence:
  - url: https://apps.db.ripe.net/docs/Update-Methods/RESTful-API/
    status: 200
  checked: '2026-10-29'
x-submission-probe: 200, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: nochange
  artifacts_added: 0
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

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 38.2 out of 100 (thin) and an Agent Readiness score of 17.3 (agent-aware), scored by API Evangelist on 2026-10-31.

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/ripe-ncc"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/ripe-ncc/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.