CloudQuery
CloudQuery is a cloud infrastructure data platform that gives platform engineering and cloud operations teams a queryable SQL data layer for visibility, governance, and automation. It syncs configuration data from AWS, GCP, Azure, and 70+ SaaS sources into normalized tables, powering cloud asset inventory, security and compliance monitoring, and FinOps use cases. CloudQuery exposes Platform REST APIs for managing tenants, syncs, destinations, and API keys, authenticated via API key.
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 CloudQuery the way a machine reads it — 32 machine-readable artifacts across 26 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 — CloudQuery scores 32.5/100 (thin), with a separate agent-readiness read of 41/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 CloudQuery
Each block below is one kind of artifact we hold for CloudQuery. 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.
CloudQuery Platform API
REST API for managing CloudQuery Platform multi-tenant accounts, syncs, sources, destinations, and API keys. Authentication uses API keys generated from the CloudQuery Platform UI.
CloudQuery admin API
The admin API from CloudQuery — 7 operation(s) for admin.
CloudQuery alerts API
The alerts API from CloudQuery — 10 operation(s) for alerts.
CloudQuery api-keys API
The api-keys API from CloudQuery — 2 operation(s) for api-keys.
CloudQuery apps API
The apps API from CloudQuery — 1 operation(s) for apps.
CloudQuery audit-logs API
The audit-logs API from CloudQuery — 2 operation(s) for audit-logs.
CloudQuery chat API
The chat API from CloudQuery — 7 operation(s) for chat.
CloudQuery custom-columns API
The custom-columns API from CloudQuery — 2 operation(s) for custom-columns.
CloudQuery filters API
The filters API from CloudQuery — 7 operation(s) for filters.
CloudQuery healthcheck API
The healthcheck API from CloudQuery — 2 operation(s) for healthcheck.
CloudQuery insights API
The insights API from CloudQuery — 8 operation(s) for insights.
CloudQuery notifications API
The notifications API from CloudQuery — 1 operation(s) for notifications.
CloudQuery onboardings API
The onboardings API from CloudQuery — 21 operation(s) for onboardings.
CloudQuery Openapi.json API
The Openapi.json API from CloudQuery — 1 operation(s) for openapi.json.
CloudQuery platform API
The platform API from CloudQuery — 2 operation(s) for platform.
CloudQuery plugins API
The plugins API from CloudQuery — 8 operation(s) for plugins.
CloudQuery policies API
The policies API from CloudQuery — 10 operation(s) for policies.
CloudQuery queries API
The queries API from CloudQuery — 11 operation(s) for queries.
CloudQuery rbac API
The rbac API from CloudQuery — 4 operation(s) for rbac.
CloudQuery reports API
The reports API from CloudQuery — 4 operation(s) for reports.
CloudQuery sync-integrations API
The sync-integrations API from CloudQuery — 1 operation(s) for sync-integrations.
CloudQuery syncs API
The syncs API from CloudQuery — 37 operation(s) for syncs.
CloudQuery tables API
The tables API from CloudQuery — 12 operation(s) for tables.
CloudQuery teams API
The teams API from CloudQuery — 1 operation(s) for teams.
CloudQuery usage API
The usage API from CloudQuery — 2 operation(s) for usage.
CloudQuery users API
The users API from CloudQuery — 11 operation(s) for users.
Scroll within the panel for all 26 ·
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).
CloudQuery Platform OpenAPI Spec
OPEN COLLECTIONSecurity Posture 4
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 CloudQuery — 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 4
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cloudquery · machine-readable index on apis.io