Eclipse Foundation
The Eclipse Foundation is a non-profit (Belgian AISBL) that provides a global community of individuals and organizations with a mature, scalable and business-friendly environment for open source software collaboration and innovation. It is also a substantial API provider in its own right: it publishes 294 REST operations across 18 first-party OpenAPI specifications, covering Eclipse project and release metadata (Projects PMI), the Eclipse Marketplace, the Eclipse Newsroom, Foundation downloads and GeoIP, Eclipse Contributor Agreement validation, committer paperwork and document signing, mailing lists, member organizations and working groups, Eclipse account profiles, and the Eclipse Open VSX Registry — the vendor-neutral marketplace for VS Code-compatible extensions, which also implements the Microsoft VS Code Extension Gallery wire protocol. Read access across the entire surface is anonymous, unmetered and free; writes authenticate against Keycloak OpenID Connect on auth.eclipse.org or, for Open VSX publishing, a personal access token.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Eclipse Foundation the way a machine reads it — 45 machine-readable artifacts across 19 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 — Eclipse Foundation scores 61.5/100 (strong), 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Eclipse Foundation's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/eclipse/"
title="Eclipse Foundation on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/eclipse.svg"
alt="Eclipse Foundation Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/eclipse/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/eclipse/"
title="Eclipse Foundation on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/eclipse/card.svg"
alt="Eclipse Foundation Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Eclipse Foundation
Each block below is one kind of artifact we hold for Eclipse Foundation. 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 26
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.
Eclipse Marketplace API
REST API for accessing Eclipse Marketplace data including listings, categories, favorites, and installation statistics for plugins, IDEs, and other extensions.
Eclipse Foundation Web API
Foundation-wide REST APIs for accessing project data, releases, committer paperwork, GeoIP, downloads, mailing lists, profiles, working groups, and other Eclipse Foundation serv...
Eclipse Projects API
REST API exposing Eclipse Foundation project metadata, releases, committers, and project lifecycle data.
Open VSX Registry API
REST API for the Eclipse Open VSX Registry, an open-source alternative to the Visual Studio Marketplace for distributing VS Code-compatible extensions.
Eclipse Newsroom REST API
REST API providing access to news, events, and announcements from the Eclipse Foundation newsroom.
Eclipse Foundation Eclipse Marketplace REST API API
The Eclipse Marketplace REST API API from Eclipse Foundation — 1 operation(s) for eclipse marketplace rest api.
Eclipse Foundation Favorites API
The Favorites API from Eclipse Foundation — 1 operation(s) for favorites.
Eclipse Foundation Featured API
The Featured API from Eclipse Foundation — 1 operation(s) for featured.
Eclipse Foundation Node API
The Node API from Eclipse Foundation — 1 operation(s) for node.
Eclipse Foundation Popular API
The Popular API from Eclipse Foundation — 1 operation(s) for popular.
Eclipse Foundation Recent API
The Recent API from Eclipse Foundation — 1 operation(s) for recent.
Eclipse Foundation Search API
The Search API from Eclipse Foundation — 1 operation(s) for search.
Eclipse Foundation Taxonomy API
The Taxonomy API from Eclipse Foundation — 1 operation(s) for taxonomy.
Eclipse Foundation Downloads API
REST API for Eclipse Foundation release and download metadata — active release trains, release versions and individual file records used to drive the eclipse.org download pages ...
Eclipse GeoIP REST API
REST API resolving a client IP address to a country, city or country IP-range set. Used by the Eclipse Foundation to select download mirrors and regionalise content.
Eclipse Foundation Git ECA API
REST API that validates Git contributions against the Eclipse Contributor Agreement. Exposes ECA lookup and commit validation as a callable service, plus inbound GitHub and GitL...
Eclipse Foundation Info API
REST API exposing Eclipse Foundation reference data — board members, registered trademarks and CVE records — plus a Slack membership webhook receiver.
Eclipse Foundation Mailing List API
REST API for Eclipse Foundation mailing list metadata and subscription records, authenticated against the auth.eclipse.org foundation realm.
Eclipse Profile API
REST API for Eclipse account profiles and user metadata, including the two-phase user deletion request flow the Foundation operates for data-protection erasure requests.
Eclipse Working Groups API
REST API for Eclipse working groups and special interest groups — participation levels, resources, participation agreements and committee membership.
Eclipse Committer Paperwork API
REST API for Eclipse committer paperwork records, authenticated against the auth.eclipse.org document-signature realm with dedicated committer_paperwork_retrieve, _update and _d...
Eclipse HelloSign API
REST API wrapping Dropbox Sign (HelloSign) for Eclipse Foundation document signing — signature requests for committer paperwork, membership and working-group agreements — plus t...
Eclipse Membership Portal API
REST API for the Eclipse Foundation membership portal — member organisations, contacts, products, yearly activity, industry collaborations, project and working-group relations. ...
Eclipse Membership Application API
REST API backing the Eclipse Foundation membership application forms — form creation, contacts, organizations, working-group selections and submission.
Eclipse Open VSX Publisher Agreement API
REST API for submitting and revoking the Eclipse Open VSX publisher agreement against an Eclipse account, gated by the openvsx_publisher_agreement OAuth scope.
Eclipse Project Adopters API
REST API listing the organisations that have declared adoption of an Eclipse Foundation project, per project or across the whole estate.
Scroll within the panel for all 26 ·
Open Collections 10
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONEclipse Marketplace REST Eclipse Marketplace REST API API
OPEN COLLECTIONEclipse Marketplace REST API
OPEN COLLECTIONScroll within the panel for all 10 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
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.
Eclipse 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.
Eclipse Finops
FINOPSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Eclipse Webhooks
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Eclipse Foundation — 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.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 6
Pricing, plans, and the legal terms of use
Company 4
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/eclipse · machine-readable index on apis.io
This is an independent, third-party profile of Eclipse Foundation, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.