Use @zap-studio/fetch in an application. Use when writing typed HTTP clients with $fetch, api.get/post/put/patch/delete, createFetch defaults, Standard Schema response validation, searchParams, json request bodies, FetchError handling, or throwOnFetchError/throwOnValidationError modes.
Use @zap-studio/retry in an application. Use when adding retries to async operations, choosing FixedDelay or ExponentialBackoff, handling RetryError, using RetryRunResult, configuring throwOnExhausted modes, supplying custom sleep functions, or creating custom BaseRetryPolicy next/onExhausted behavior.
Use @zap-studio/validation in an application or library. Use when validating unknown data with Standard Schema, standardValidate, standardValidateSync, createStandardValidator, createSyncStandardValidator, isStandardSchema, ValidationError, throwOnError modes, sync-vs-async schemas, or shared validation across Zod, Valibot, ArkType, and other Standard Schema libraries.
Use @zap-studio/webhooks in an application or framework adapter. Use when creating webhook routers with createWebhookRouter, registering schema-validated handlers, handling NormalizedRequest/NormalizedResponse, adding before/after/onError hooks, writing verify functions, using HMAC signature verification, or implementing BaseAdapter adapters.
Use @zap-studio/permit in an application. Use when defining authorization resource schemas, Actions, Resources, PermitConfig, createPolicy rules, allow/deny/when helpers, and/or/not conditions, has/hasRole role checks, role hierarchies, mergePolicies, mergePoliciesAny, or type-safe permission strings like "post:read".