Cribl
Cribl is an observability pipeline company providing a suite of products for collecting, processing, routing, searching, and storing telemetry data at scale. Cribl's developer platform offers REST APIs across Stream, Edge, Search, Lake, and the As Code product line, exposing programmatic control over data pipelines, edge agents, federated search jobs, lake datasets, and infrastructure-as-code configuration management. The Cribl Cloud API acts as a centrally managed control plane across all deployments and authenticates with OAuth 2.0 client credentials.
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 Cribl the way a machine reads it — 93 machine-readable artifacts across 32 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 — Cribl scores 54.8/100 (developing), 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Cribl
Each block below is one kind of artifact we hold for Cribl. 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 32
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.
Cribl API Credentials API
Manage API credentials used for OAuth 2.0 client credentials authentication. Credentials consist of a client ID and client secret used to obtain bearer tokens for API access.
Cribl Authentication API
Obtain and manage authentication tokens for API access.
Cribl Collectors API
Manage scheduled and on-demand data collection jobs from REST APIs, databases, scripts, and other sources.
Cribl Database Connections API
Configure and manage database connections used by collectors and lookup functions.
Cribl Datasets API
Manage Cribl Lake datasets that define storage buckets for observability and security data in open formats.
Cribl Destinations API
Manage data output destinations where processed events are sent, including Splunk, S3, Elasticsearch, and webhook endpoints.
Cribl Edge Destinations API
Manage data output destinations for edge nodes including forwarding to Stream workers, cloud storage, and analytics platforms.
Cribl Edge Fleets API
Manage edge fleets that organize groups of edge nodes deployed on endpoints for local data collection and processing.
Cribl Edge Nodes API
Monitor and manage individual edge nodes deployed on endpoints including their status, version, and resource utilization.
Cribl Edge Pipelines API
Manage processing pipelines running on edge nodes for local data transformation and filtering before forwarding.
Cribl Edge Routes API
Manage routes on edge nodes for directing collected data to appropriate pipelines and destinations.
Cribl Edge Sources API
Manage data input sources on edge nodes including file monitors, Windows Event Log, system metrics, AppScope, and other local collection methods.
Cribl Functions API
Retrieve available processing functions that can be used within pipelines for data transformation.
Cribl Groups API
Manage Worker Groups and Edge Fleets, which organize and deploy configurations to sets of worker nodes or edge agents.
Cribl Health API
Check the health and availability of the Cribl Cloud management plane services.
Cribl Jobs API
Monitor and manage running and completed collection and processing jobs.
Cribl Lake Datasets API
Manage Cribl Lake datasets for storing and organizing observability data in open formats.
Cribl Lookups API
Manage lookup files and tables used for data enrichment in pipelines.
Cribl Nodes API
Monitor and manage individual worker nodes and edge nodes within groups and fleets.
Cribl Notifications API
Configure notification rules and targets for alerting on data flow anomalies and system events.
Cribl Packs API
Install, manage, and distribute reusable configuration packs containing pipelines, routes, and other resources.
Cribl Pipelines API
Manage processing pipelines that contain ordered sequences of functions for transforming, filtering, and enriching events.
Cribl Retention API
Configure data retention policies that control how long data is stored in Lake datasets before automatic cleanup.
Cribl Routes API
Manage routes that filter and direct incoming data across pipelines and destinations using filter expressions.
Cribl Saved Searches API
Create and manage saved search queries for reuse and sharing across teams and workflows.
Cribl Search Jobs API
Execute and manage search queries across live and stored observability data with support for federated search across multiple data sources.
Cribl Search Notifications API
Configure notification rules that trigger alerts based on search results using webhook and other notification targets.
Cribl Sources API
Manage data input sources that collect events from various systems including Syslog, HTTP, Kafka, Splunk, and other protocols.
Cribl System API
Access system-level settings including Git configuration, licensing, and global preferences.
Cribl Versioning API
Manage configuration versions, commits, and deployment history.
Cribl Worker Groups API
Manage Stream worker groups that organize worker nodes and deploy shared pipeline configurations across clusters.
Cribl Workspaces API
Manage Cribl Cloud workspaces which are unique VPC containers each isolating an instance of the Cribl Product Suite including Stream, Edge, Search, and Lake.
Scroll within the panel for all 32 ·
Open Collections 6
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).
Cribl As Code API
OPEN COLLECTIONCribl Cloud API
OPEN COLLECTIONCribl Edge API
OPEN COLLECTIONCribl Lake API
OPEN COLLECTIONCribl Search API
OPEN COLLECTIONCribl Stream 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.
Cribl 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.
Cribl 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.
Cribl Finops
FINOPSSemantic 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.
Cribl Context
JSON-LDSpectral Rules 7
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.
Cribl API Rules
SPECTRALCribl API Rules
SPECTRALCribl API Rules
SPECTRALCribl API Rules
SPECTRALCribl API Rules
SPECTRALCribl API Rules
SPECTRALCribl API Rules
SPECTRALScroll within the panel for all 7 ·
JSON Schema 38
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.
ApiCredential
JSON SCHEMAApiCredentialCreate
JSON SCHEMAApiCredentialUpdate
JSON SCHEMAApiCredentialWithSecret
JSON SCHEMACollector
JSON SCHEMADatabaseConnection
JSON SCHEMACribl Destination
JSON SCHEMADestinationStatus
JSON SCHEMAEdgeDestination
JSON SCHEMAEdgeFleet
JSON SCHEMAEdgeNode
JSON SCHEMAEdgePipeline
JSON SCHEMAEdgeRoute
JSON SCHEMAEdgeSource
JSON SCHEMAFunction
JSON SCHEMAGitSettings
JSON SCHEMAGroup
JSON SCHEMAHealthStatus
JSON SCHEMAJob
JSON SCHEMALakeDataset
JSON SCHEMALookup
JSON SCHEMANode
JSON SCHEMANotification
JSON SCHEMAPack
JSON SCHEMACribl Pipeline
JSON SCHEMAPipelineFunction
JSON SCHEMARetentionPolicy
JSON SCHEMACribl Route
JSON SCHEMASavedSearch
JSON SCHEMASearchDataset
JSON SCHEMASearchJob
JSON SCHEMASearchJobRequest
JSON SCHEMACribl Source
JSON SCHEMACribl Worker Group
JSON SCHEMAWorkerGroup
JSON SCHEMAWorkspace
JSON SCHEMAWorkspaceCreate
JSON SCHEMAWorkspaceUpdate
JSON SCHEMAScroll within the panel for all 38 ·
JSON Structure 1
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.
Cribl Structure
JSON STRUCTURESecurity 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 Cribl — 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 6
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cribl · machine-readable index on apis.io