api-runner

Execute API tasks, log results to Langfuse, and persist events to ClickHouse.

Updated Aug 27, 2026

Search Tags:#automation #api #logging #task execution #data persistence #langfuse #clickhouse

Ready to run

npx skills add https://github.com/OrionArchitekton/cosmocrat-core --skill api-runner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-runner
Source: https://github.com/OrionArchitekton/cosmocrat-core/tree/main/skills/ops/api-runner
Command: npx skills add https://github.com/OrionArchitekton/cosmocrat-core --skill api-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of a defined list of API tasks, ensuring that their outcomes are logged for monitoring and analysis.

Core Features & Use Cases

Task Execution: Runs a predefined set of API calls.
Logging: Records execution details and results to Langfuse.
Data Persistence: Stores events and artifacts in ClickHouse for historical analysis.
Use Case: Automatically run daily health checks on a set of external APIs, logging any failures or performance degradations.

Quick Start

Run the api-runner skill for the date 2025-12-22.

Frequently Asked Questions about api-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate API health checks and log the results?▼

You can automate API health checks by defining task lists in a YAML file, which the runner executes sequentially. It logs execution details and failures to Langfuse, and persists all event artifacts to ClickHouse for historical monitoring.

How do I store API task execution events in ClickHouse?▼

To store API task execution events in ClickHouse, the runner automatically persists all artifacts and execution data to the database after completing your predefined API calls. You just need the specific environment variables configured for access.

What is the best way to run a scheduled data ingestion pipeline for external APIs?▼

Running a scheduled data ingestion pipeline is best handled by executing a predefined list of API tasks defined in a YAML configuration file. The runner processes these calls, logs outcomes to Langfuse, and stores the ingested data in ClickHouse.

Do I need Langfuse to log API task execution outcomes?▼

Yes, Langfuse is required to log API task execution outcomes. The runner integrates directly with Langfuse to record execution details, monitor performance degradations, and capture any failures during the automated API call process.

Can I use this API runner for daily external API monitoring without writing custom scripts?▼

Yes, you can use this runner for daily external API monitoring by defining your API calls as tasks in a YAML configuration file. The system executes these tasks automatically, logs results to Langfuse, and persists data to ClickHouse.

What limitations exist when persisting API artifacts to ClickHouse?▼

The primary limitation is that task definitions must be located in a specific YAML file, and specific environment variables must be set for API access. Without these exact configurations, the runner cannot execute tasks or persist artifacts to ClickHouse.