data-pipeline

Validate and transform external API data with layered caching and failover.

4|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill data-pipeline-0xjc65eth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-pipeline
Source: https://github.com/0xjc65eth/CYPHER-V3/tree/main/skills/data-pipeline
Command: npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill data-pipeline-0xjc65eth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent, up-to-date, and validated data delivery from multiple external market APIs into the CYPHER V3 UI by enforcing layered caching, schema validation, deterministic transformations, and intelligent fallbacks so users never see stale or invalid values.

Core Features & Use Cases

  • Layered caching with TTLs: Edge CDN, Redis/Upstash, and client-side caches with explicit TTLs to balance freshness and availability.
  • Schema validation & transformation: Zod schemas and transform functions convert raw API payloads into safe, frontend-ready models.
  • Multi-source aggregation and failover: Prioritized sources (CoinGecko, Hiro, Binance) with automatic fallback and stale-cache acceptance when upstreams fail.
  • Operational pipelines: Dedicated pipelines for BTC price, ordinals collections, runes, and fee estimates with clear TTL guidance for each data class.
  • Use Case: Power a live trading dashboard that shows real-time BTC price, ordinals floor and volume, and mempool fee estimates without serving stale or malformed data.

Quick Start

Use the data-pipeline skill to fetch the current BTC price via CoinGecko with a 15s Redis TTL and fallback to Binance when CoinGecko fails.

Frequently Asked Questions about data-pipeline

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

FAQPage Schema
How do I prevent stale API data from showing in a live crypto trading dashboard?

Use a data-pipeline architecture with layered caching and TTL management to prevent stale API data in a live crypto trading dashboard. It enforces edge CDN, Redis, and client-side caches with schema validation and stale-cache fallback to ensure users never see invalid values during upstream failures.

How does Zod schema validation work for API response transformation?

Zod schema validation for API response transformation works by parsing raw external payloads into safe, frontend-ready models. The data pipeline applies deterministic transform functions alongside Zod schemas to guarantee that only structurally validated data passes through to the UI layer.

What is the best way to implement API failover for multi-source crypto data aggregation?

The best way to implement API failover for multi-source crypto data aggregation is using prioritized source failover with stale-cache acceptance. The pipeline automatically falls back from primary sources like CoinGecko to alternatives like Binance, serving cached data when upstreams fail.

Can I use Redis caching with TTLs for real-time Bitcoin ordinals and runes data?

Yes, you can use Redis caching with explicit TTLs for real-time Bitcoin ordinals and runes data. The pipeline includes dedicated operational pipelines for ordinals collections, runes, and fee estimates, providing clear TTL guidance to balance data freshness with availability.

Why does my external API deliver malformed data to the frontend interface?

External APIs deliver malformed data to the frontend interface when missing schema validation allows unstructured payloads to pass through. Implementing Zod-based schema validation and deterministic transformation pipelines within your data flow ensures raw payloads are converted into safe models.

Do I need multiple data sources for a resilient BTC price feed?

You need multiple data sources for a resilient BTC price feed to ensure continuous availability during API failures. The pipeline prioritizes sources like CoinGecko with a 15s Redis TTL and automatically falls back to Binance, accepting stale cache when all upstreams fail.