Keen.io is an embedded analytics API that enables developers to collect, analyze, and visualize event data seamlessly.
Available to claim
Build and ship the Keen.io plugin to earn 16 points when we merge it to main. You have 1 hour to link an issue, then 3 hours to open a PR with the plugin scaffold.
Retrieve schema information for all event collections in a Keen.io project. Use this tool to: - List all event collection names in a project - Discover the schema (property names and types) for each collection - Explore available data before running queries Returns up to 5000 event collections with their names, URLs, and optional property schemas.
Tool to return details for a specific property in an event collection. Use when you need to inspect a property's inferred type and resource URL.
Retrieve schema information for a single Keen.io event collection. Returns the inferred property types for all fields in the specified collection, useful for understanding data structure before running queries. Property types include 'num' (numbers), 'string' (text), 'bool' (booleans), and 'datetime' (timestamps). Use this tool when you need to: - Understand the structure of a specific event collection - Verify property names and types before building queries - Debug data type mismatches in analytics queries
List all cached dataset definitions for a Keen.io project. Returns paginated results of pre-computed dataset definitions including their query configuration, status, and timing information. Use limit and after_name parameters to page through large result sets. Cached datasets allow pre-computing analytics for hundreds or thousands of entities at once, enabling instant retrieval of results for any indexed entity.
Tool to return unique values for a target property. Use when distinct property values are required for matching events with optional filters and timeframe constraints.
Reactivate a previously revoked Keen.io access key. Use this tool when you need to restore access for a key that was previously revoked but not deleted. A revoked key has its 'active' flag set to false; this operation sets it back to true, allowing the key to be used for API authentication again. Note: This operation requires a Master API Key for authentication. The key must have been previously revoked (not deleted) to be unrevoked.
No webhooks.
