SonarSource
SonarSource (Sonar) builds the industry-standard tooling for code quality and code security, trusted by large engineering organizations to keep code Clean. Its product line spans SonarQube Cloud (formerly SonarCloud, the hosted SaaS analysis service), SonarQube Server (self-managed), SonarQube for IDE (formerly SonarLint), and the SonarQube Community Build. SonarQube Cloud exposes a REST Web API for programmatically managing projects, issues, quality gates, quality profiles, rules, measures, hotspots, permissions, webhooks, and user tokens, plus a family of first-party scanners (npm, PyPI, Maven, Gradle, .NET, and Docker) for wiring analysis into CI/CD pipelines.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles SonarSource the way a machine reads it — 37 machine-readable artifacts across 33 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 — SonarSource scores 56.8/100 (developing), with a separate agent-readiness read of 69/100 (agent native). 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.
How we profile SonarSource
Each block below is one kind of artifact we hold for SonarSource. 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 33
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.
SonarSource authentication API
Handle authentication.
SonarSource ce API
Get information on Compute Engine tasks.
SonarSource components API
Get information about a component (file, directory, project, ...) and its ancestors or descendants. Update a project or module key.
SonarSource duplications API
Get duplication information for a project.
SonarSource favorites API
Manage user favorites
SonarSource favourites API
Removed since 6.3, please use api/favorites instead
SonarSource hotspots API
Read and update Security Hotspots. Hotspots are deprecated and replaced by security issues (software quality) and vulnerabilities (type). Please use the API of security issues /...
SonarSource issues API
Read and update issues.
SonarSource languages API
Get the list of programming languages supported in this instance.
SonarSource measures API
Get components or children with specified measures.
SonarSource metrics API
Get information on automatic metrics, and manage custom metrics. See also api/custom_measures.
SonarSource notifications API
Manage notifications of the authenticated user
SonarSource permissions API
Manage permission templates, and the granting and revoking of permissions at the global and project levels.
SonarSource project_analyses API
Manage project analyses.
SonarSource project_badges API
Generate badges based on quality gates or measures
SonarSource project_branches API
Manage branch (only available when the Branch plugin is installed)
SonarSource project_links API
Manage projects links.
SonarSource project_pull_requests API
Manage pull request (only available when the Branch plugin is installed)
SonarSource project_tags API
Manage project tags
SonarSource projects API
Manage project existence.
SonarSource properties API
This web service is deprecated, please use api/settings instead.
SonarSource qualitygates API
Manage quality gates, including conditions and project association.
SonarSource qualityprofiles API
Manage quality profiles.
SonarSource rules API
Get and update some details of automatic rules, and manage custom rules.
SonarSource settings API
Manage settings.
SonarSource sources API
Get details on source files. See also api/tests.
SonarSource timemachine API
Removed since 6.3, please use api/measures/search_history instead
SonarSource user_groups API
Manage user groups.
SonarSource user_properties API
Removed since 6.3, please use api/favorites and api/notifications instead
SonarSource user_tokens API
List, create, and delete a user's access tokens.
SonarSource users API
Manage users.
SonarSource webhooks API
Webhooks allow to notify external services when a project analysis is done
SonarSource webservices API
Get information on the web api supported on this instance.
Scroll within the panel for all 33 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sonarsource-mcp.yml
MCP SERVERSecurity 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 SonarSource — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
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/sonarsource · machine-readable index on apis.io