fetch

Validate HTTP API responses against Standard Schema with typed inference.

Updated Aug 23, 2026

Search Tags:#typescript #api #fetch #schema-validation #http-client #typed-response

Ready to run

npx skills add https://github.com/zap-studio/skills --skill fetch-zap-studio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fetch
Source: https://github.com/zap-studio/skills/tree/main/fetch
Command: npx skills add https://github.com/zap-studio/skills --skill fetch-zap-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a type-safe HTTP client that validates API responses against defined schemas, eliminating unsafe type assertions and runtime errors due to unexpected payloads.

Core Features & Use Cases

Type-safe HTTP client: Enforces runtime validation of responses against Standard Schema to infer typed results.
Schema-driven validation: Ensures API payloads conform to declared schemas, improving reliability and safety.
Unified error handling: Centralizes error management for GET, POST, PUT, PATCH, and DELETE operations across services.
Use Case: Ensure API responses for a user profile endpoint always include id, name, and email, with compile-time typing and runtime checks.

Quick Start

Create a configured api client and fetch a URL using a schema to validate and parse the response.

Frequently Asked Questions about fetch

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

FAQPage Schema

How do I validate API responses in TypeScript without unsafe type assertions?▼

You can validate API responses in TypeScript by using a type-safe HTTP client that checks payloads against standard schemas at runtime, eliminating unsafe type assertions and preventing errors from unexpected data structures.

What is schema-driven HTTP client validation and how does it work?▼

Schema-driven HTTP client validation enforces runtime checks of API payloads against declared schemas, ensuring API responses conform to expected structures while inferring typed results for consistent and safe data consumption.

How do I set up a configurable HTTP client factory for base URLs and authentication?▼

You can set up a configurable HTTP client factory to define base URLs and authentication headers centrally, ensuring all subsequent GET, POST, PUT, PATCH, and DELETE operations inherit the configuration consistently.

Can I use this type-safe HTTP client to handle errors across multiple HTTP methods?▼

Yes, this type-safe HTTP client provides unified error handling that centralizes error management across GET, POST, PUT, PATCH, and DELETE operations, ensuring consistent error behavior throughout your application services.

Why do I need runtime schema validation for typed HTTP responses?▼

Runtime schema validation for typed HTTP responses is needed because compile-time typing alone cannot guarantee external API payloads match your types, preventing runtime crashes when endpoints return unexpected or missing fields.

Does this schema validation HTTP client work with external APIs?▼

Yes, the schema validation HTTP client is designed for applications that consume external APIs, enabling runtime validation and typed response inference to safely handle unpredictable third-party data payloads.