Looker
Looker is a business intelligence and data analytics platform that enables organizations to explore, analyze, and share real-time business analytics.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Looker the way a machine reads it — 124 machine-readable artifacts across 10 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 — Looker scores 66.0/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.
How we profile Looker
Each block below is one kind of artifact we hold for Looker. 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 10
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.
LookML API
API for programmatically managing LookML projects, models, and views.
Looker Action API
The Looker Action API enables developers to define custom actions, or destinations, to which Looker can send query results, dashboard results, or user interactions via a webhook...
Looker Embed SDK
The Looker Embed SDK is a JavaScript library for embedding Looker content such as dashboards, Looks, Explores, reports, and extensions into web applications, with support for si...
Looker Extension Framework API
The Looker Extension Framework provides APIs and SDKs for building custom extensions that run inside the Looker UI, with access to the Looker API, Looker components library, and...
Looker (Google Cloud core) API
The Looker (Google Cloud core) REST API provides management capabilities for Looker instances running on Google Cloud, including instance lifecycle management, backups, and oper...
Looker Auth API
Authentication endpoints for obtaining and managing API access tokens using client credentials.
Looker Dashboard API
Manage dashboards, which are collections of tiles displaying visualizations from queries. Dashboards support filters, layouts, and can be shared across the organization.
Looker Look API
Manage Looks, which are saved queries with visualizations. A Look contains a query definition and visualization configuration that can be shared, scheduled, and embedded.
Looker Query API
Create and run queries against your Looker models. Queries define the fields, filters, sorts, and limits used to retrieve data from the underlying database through LookML models.
Looker User API
Manage Looker users including creating, updating, and retrieving user accounts, credentials, roles, and sessions.
Scroll within the panel for all 10 ·
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).
Looker 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.
Looker Plans Pricing
PLANSRate 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.
Looker 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.
Looker Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Self-Service Analytics
Enable business users to explore data, build visualizations, and create dashboards without SQL knowledge using LookML models.
Data Modeling with LookML
Define reusable data models in LookML that provide a semantic layer between databases and end-user analytics.
Embedded Analytics
Embed interactive dashboards, reports, and data explorations directly into web applications using SSO and cookieless authentication.
Scheduled Reports
Schedule and deliver reports and dashboards via email, Slack, S3, or custom action destinations.
Custom Actions
Build webhook-based actions to send query results to any external destination or trigger workflows.
API-Driven Administration
Programmatically manage users, roles, dashboards, queries, and platform settings through the Looker API.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Looker Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Looker API Rules
SPECTRALLooker API Rules
SPECTRALJSON Schema 40
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessToken
JSON SCHEMAAccessToken
JSON SCHEMACredentialsApi3
JSON SCHEMACredentialsEmail
JSON SCHEMACredentialsApi3
JSON SCHEMACredentialsEmail
JSON SCHEMADashboardElement
JSON SCHEMADashboardFilter
JSON SCHEMADashboardLayoutComponent
JSON SCHEMADashboardLayout
JSON SCHEMADashboard
JSON SCHEMADashboardElement
JSON SCHEMADashboardFilter
JSON SCHEMADashboardLayout
JSON SCHEMADashboardLayoutComponent
JSON SCHEMAErrorResponse
JSON SCHEMAErrorResponse
JSON SCHEMAFolderBase
JSON SCHEMAFolderBase
JSON SCHEMALookModel
JSON SCHEMALook
JSON SCHEMALookModel
JSON SCHEMAModelSet
JSON SCHEMAModelSet
JSON SCHEMAPermissionSet
JSON SCHEMAPermissionSet
JSON SCHEMAQuery
JSON SCHEMARole
JSON SCHEMASession
JSON SCHEMASpaceBase
JSON SCHEMASpaceBase
JSON SCHEMAUser
JSON SCHEMAWriteDashboard
JSON SCHEMAWriteLookWithQuery
JSON SCHEMAWriteQuery
JSON SCHEMAWriteUser
JSON SCHEMAWriteDashboard
JSON SCHEMAWriteLookWithQuery
JSON SCHEMAWriteQuery
JSON SCHEMAWriteUser
JSON SCHEMAScroll within the panel for all 40 ·
JSON Structure 24
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Looker Access Token Structure
JSON STRUCTURELooker Credentials Api3 Structure
JSON STRUCTURELooker Credentials Email Structure
JSON STRUCTURELooker Dashboard Element Structure
JSON STRUCTURELooker Dashboard Filter Structure
JSON STRUCTURELooker Dashboard Layout Component Structure
JSON STRUCTURELooker Dashboard Layout Structure
JSON STRUCTURELooker Dashboard Structure
JSON STRUCTURELooker Error Response Structure
JSON STRUCTURELooker Folder Base Structure
JSON STRUCTURELooker Look Model Structure
JSON STRUCTURELooker Look Structure
JSON STRUCTURELooker Model Set Structure
JSON STRUCTURELooker Permission Set Structure
JSON STRUCTURELooker Query Structure
JSON STRUCTURELooker Role Structure
JSON STRUCTURELooker Session Structure
JSON STRUCTURELooker Space Base Structure
JSON STRUCTURELooker Structure
JSON STRUCTURELooker User Structure
JSON STRUCTURELooker Write Dashboard Structure
JSON STRUCTURELooker Write Look With Query Structure
JSON STRUCTURELooker Write Query Structure
JSON STRUCTURELooker Write User Structure
JSON STRUCTUREScroll within the panel for all 24 ·
Examples 23
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Looker Access Token Example
EXAMPLELooker Dashboard Example
EXAMPLELooker Folder Base Example
EXAMPLELooker Look Example
EXAMPLELooker Look Model Example
EXAMPLELooker Model Set Example
EXAMPLELooker Query Example
EXAMPLELooker Role Example
EXAMPLELooker Session Example
EXAMPLELooker Space Base Example
EXAMPLELooker User Example
EXAMPLELooker Write Query Example
EXAMPLELooker Write User Example
EXAMPLEScroll within the panel for all 23 ·
Security 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.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Executive Dashboards
Build real-time executive dashboards aggregating KPIs from multiple data sources for leadership visibility.
Customer-Facing Analytics
Embed analytics into SaaS products to provide customers with self-service reporting and data exploration.
Data Governance Reporting
Monitor data quality, usage patterns, and access controls across the organization through audit reports.
Marketing Performance Analytics
Analyze campaign performance, attribution, and ROI across marketing channels with unified data models.
Operational Monitoring
Track operational metrics and KPIs in real time with automated alerting and scheduled report delivery.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Google BigQuery
Native optimized connector for querying and analyzing data in Google BigQuery data warehouse.
Snowflake
High-performance connector for Snowflake cloud data warehouse with push-down query optimization.
Amazon Redshift
Native connector for querying and visualizing data in Amazon Redshift data warehouse.
Slack
Deliver scheduled reports and dashboard snapshots to Slack channels with interactive query capabilities.
Google Sheets
Export query results and dashboard data directly to Google Sheets for collaborative analysis.
Salesforce
Connect to Salesforce data for CRM analytics and combine with other data sources for unified views.
Resources
Every other property we hold for Looker — 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 2
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
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
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
← All providers · Data indexed from github.com/api-evangelist/looker · machine-readable index on apis.io