Eclipse Foundation
The Eclipse Foundation provides a global community of individuals and organizations with a mature, scalable, and business-friendly environment for open source software collaboration and innovation. This index aggregates the developer-facing APIs and services published by the Eclipse Foundation and its working groups.
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 Eclipse Foundation the way a machine reads it — 20 machine-readable artifacts across 13 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 39.1/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 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 13
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.
Scroll within the panel for all 13 ·
Open Collections 1
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).
Eclipse Marketplace REST API
OPEN COLLECTIONPricing 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.
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
FINOPSSecurity Posture 2
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 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
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
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/eclipse · machine-readable index on apis.io