[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_122":123},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_56":-5,"_57":49,"_58":59,"_60":61,"_62":63,"_64":65,"_66":67,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":79,"_80":-5,"_81":-5,"_82":-5,"_83":49,"_84":-5,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94,"_95":96},"apiUrl","https://odel.app/api","creator","rejifald","moduleId","stitchapi","@rejifald/stitchapi","displayName","StitchAPI Docs","tagline","Search and read the StitchAPI docs: search_docs finds relevant sections, get_doc reads a page.","iconKey","https://avatars.githubusercontent.com/u/42000283?v=4","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://stitchapi.dev/api/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1783333230000,"updatedAt",1788323606000,"sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=dev.stitchapi%2Fdocs","sourceVerified",false,"sourceMissingSince","importedAt","upstreamStars",17,"upstreamUpdatedAt",1788193488000,"detectedTransport","streamable-http","detectedAuthType","none","probeStatus","ok","lastProbedAt",1787632218000,"githubRepoUrl","https://github.com/rejifald/StitchAPI","githubRepoFullName","rejifald/StitchAPI","releaseId","ext-rejifald-stitchapi","version","1.1.0","descriptionMarkdown","

\n $\"Stand$ \n

\n\n

\n \n \n $\"StitchAPI$ \n \n

\n\n

\n API stitching: turn any API into a typed, resilient function. Declare an endpoint once — its types, auth, and resilience — and call it like a local function. No server, no codegen, no config files. The same definition answers to your code, the CLI, and an AI agent alike.\n

\n\n

\n 📚 stitchapi.dev — documentation, guides & live playground\n

\n\n

\n $\"Dependencies:$ \n $\"Bundle:$ \n $\"OpenSSF$ \n $\"npm$ \n

\n\n\n\n

\n $\"code$ \n $\"coverage:$ \n

\n\n\n\n

\n Zero runtime dependencies · ~25 kB min+gzip — a typical import { stitch } tree-shakes to ~22 kB, and with no transitive tree there is nothing else to install or audit. The size is an enforced budget in CI, not an aspiration.\n

\n\n

\n Verifiable supply chain — every package publishes from GitHub Actions over OIDC with a signed npm build-provenance attestation, so you can confirm which commit and which workflow produced the tarball you installed. Each release also ships an SBOM in both SPDX and CycloneDX, and the repo is scored publicly by OpenSSF Scorecard.\n

\n\n

\n \n \n \n $\"StitchAPI$ \n \n \n

\n\n

\n _{Watch more}\n

\n\n> [!NOTE]\n>\n> **StitchAPI is at `1.0.0-rc.7`.** The core runtime is feature-complete, zero-dependency, covered by a green test gate, and already running in production in two projects. We're validating in the wild before stamping a stable `1.0.0` — pin an exact version and expect only small, documented changes. Feedback is welcome.\n\n---\n\n## Table of Contents\n\n- [What is a stitch?](#what-is-a-stitch)\n- [Motivation](#motivation)\n- [Why StitchAPI](#why-stitchapi)\n- [What StitchAPI is not](#what-stitchapi-is-not)\n- [Features](#features)\n- [Install](#install)\n- [Quick start](#quick-start)\n- [Composition: seam, extends, `.with()`](#composition-seam-extends-with)\n- [Validation & leveled drift](#validation--leveled-drift)\n- [Resilience: retry, throttle, timeout](#resilience-retry-throttle-timeout)\n- [Caching](#caching)\n- [Auth as a boundary](#auth-as-a-boundary)\n- [Surfaces: any request style](#surfaces-any-request-style)\n- [Four front doors](#four-front-doors)\n- [Agent-native](#agent-native)\n- [Errors & pitfalls](#errors--pitfalls)\n- [Zero-infra observability](#zero-infra-observability)\n- [Packages](#packages)\n- [Documentation](#documentation)\n- [Contributing](#contributing)\n- [License](#license)\n\n## What is a stitch?\n\nA **stitch** is StitchAPI's core primitive: it takes a single endpoint and hands back a callable. You declare the contract once — input, output, auth, resilience — and call it like a local function. The same definition your code calls, the CLI runs and an AI agent invokes — and every caller gets a **capability, not a credential**. A service with more than one endpoint is a **seam** — a group of stitches that share a base URL, auth, and one runtime (throttle budget, store, trace sink).\n\n```ts\nimport { stitch } from 'stitchapi';\nimport { z } from 'zod';\n\nconst getUser = stitch({\n path: 'https://api.example.com/users/{id}',\n output: z.object({ id: z.number(), name: z.string() }),\n pick: 'data',\n});\n\nconst user = await getUser({ params: { id: 1 } }); // typed · validated\n```\n\nKeep the `fetch` or axios you already have — it's the adapter underneath. A stitch sits _above_ the transport and turns an endpoint into a function rather than replacing the call.\n\n## Motivation\n\nIn almost every project there's a `src/api/` folder of thin functions that fire an HTTP request and pull the payload out of the response. Everything that actually makes an integration reliable — auth lifecycle, retries, rate limits, timeouts, response validation, drift detection, observability — gets re-implemented at every call site, and each wrapper rots independently. `fetch` hands back opaque bytes, and raw bytes aren't what application code (or an AI agent) needs; both want structured, validated, observable results.\n\nA stitch folds all of that back into the call:\n\n| Around raw `fetch`, you hand-roll… | …a stitch declares it once |\n| --------------------------------------------------- | ------------------------------------------------------------- |\n| Opaque bytes you parse and hope are the right shape | Schema-validated, typed results — drift caught on every call |\n| A throw on the first failure, then it's on you | Retries with backoff + jitter, honoring `Retry-After` |\n| One coarse timeout, if you remember it | Layered total / per-attempt timeouts with real aborts |\n| No rate control — you meet the 429s in production | Proactive throttle: rate + concurrency caps, shared per host |\n| A raw byte stream you frame and paginate yourself | SSE framing, delta concatenation, auto-pagination |\n| Zero visibility into what the call did | A typed event stream + opt-in traces: latency, retries, drift |\n\n## Why StitchAPI\n\nThere are plenty of ways to get a typed API client — spec-based generators, hand-authored contract clients, workflow platforms, or a folder of hand-rolled fetch wrappers. StitchAPI sits in a spot none of them cover: it turns **one endpoint at a time** into a resilient, validated, observable function — no spec, no codegen, no config files, no server; only explicit composition.\n\n- **Atomic, not spec-first.** Spec-based generators (openapi-generator, Orval, Kubb, …) need a complete OpenAPI document first — and most real-world APIs (internal, undocumented, the long tail) never get one. A stitch needs a URL and one example response.\n- **A runtime, not a code generator.** No generated SDK to commit, diff, and regenerate. The declaration _is_ the client, validated on every live call — so a silently renamed field is a loud, leveled **drift** signal, not an `undefined` three layers downstream.\n- **Resilience is declared, not hand-rolled.** Retries, throttling, timeouts, circuit breaking, pagination — configuration on the stitch, uniform across every integration.\n- **Auth is a boundary.** A stitch owns its credential and lifecycle; callers get a **capability, not the credential**. That matters double when the caller is an AI agent.\n- **Agents are first-class callers.** One definition is a function, a CLI command, an HTTP endpoint, and an MCP tool — returning structured, schema-validated, traceable results instead of opaque bytes.\n- **A library, not a platform.** Zero runtime dependencies, embeds in your project, nothing to operate.\n\n| Alternative | Needs | You maintain | StitchAPI instead |\n| ------------------------------------------------------ | ------------------------ | ----------------------------------------------------- | ------------------------------------------------------------------------ |\n| Spec-based codegen (openapi-generator, Orval, Kubb, …) | a complete OpenAPI spec | a generated SDK, regenerated on every API change | one endpoint at a time, validated live at runtime |\n| Typed runtime clients (Zodios, ts-rest, …) | a hand-authored contract | your own retry / auth / rate-limit code around it | resilience, auth lifecycle, and drift detection built into the primitive |\n| Workflow platforms (Windmill, n8n, …) | a server to deploy | flows inside someone else's runtime | a zero-dependency library; composition is just code |\n| Hand-rolled `fetch` wrappers | nothing | bespoke auth, retries, limits — re-solved per project | the same concerns, declared once per stitch |\n\nFor the full competitive landscape and positioning, see the [Overview](https://github.com/rejifald/StitchAPI/blob/main/docs/OVERVIEW.md).\n\n## What StitchAPI is not\n\nKnowing what a tool refuses to be is how you trust what it is:\n\n- **Not an HTTP client or `fetch` replacement** — `fetch`/axios are the substrate underneath; a stitch sits above the transport.\n- **Not a code generator** — no SDK to commit, diff, and regenerate; the declaration is the runtime, validated live.\n- **Not spec-first** — no OpenAPI document required; a URL and one example response is enough.\n- **Not a server to deploy** — a zero-dependency library you import, for the APIs you don't control.\n- **Not a workflow engine or iPaaS** — no orchestration, queues, or visual builder; composition is plain TypeScript.\n- **No config files or hidden inheritance** — nothing ambient a stitch silently reads.\n\nNo server, no codegen, no config files, no implicit inheritance — **only explicit composition.**\n\n## Features\n\n- **One primitive, scoped to a surface** — `stitch(url | config)` returns a typed callable; **a service with more than one endpoint is a `seam`** that shares base, auth, throttle budget, store, and trace sink across its members.\n- **Event-stream core** — every call yields a typed stream (`start → progress → drift → result → done`); `await` is sugar that returns the final validated value.\n- **Bring-your-own validation** — [Zod](https://zod.dev) or any [Standard Schema](https://standardschema.dev) validator (Valibot, ArkType, …); types are inferred from the schemas.\n- **Leveled drift detection** — live responses validated against the declared schema (the contract); a required field missing/incompatible **throws**, while soft drift (a coercion, an undeclared or defaulted field) surfaces as a non-fatal `warn` / `info` / `verbose` finding instead of a silent `undefined`.\n- **Declared resilience** — retry with backoff and `Retry-After`, proactive throttle, layered timeouts, a circuit breaker, and idempotency keys.\n- **Read-through caching** — opt-in response cache + in-process coalescing, keyed by a derived, principal-scoped key, loaded lazily from `stitchapi/cache`.\n- **Auth as a boundary** — `bearer`, `apiKey`, `basic`, `cookieSession` (auto-login/re-login), `oauth2`; secrets resolve at call time and never reach the caller.\n- **Any request style** — `http` by default; `graphql`, `sse`, `stream`, `download`, `llm`, `shell`, and `postmessage` are peer surfaces behind subpath imports.\n- **Pluggable state store** — throttle counters and sessions behind a 3-method store; swap in Redis/Postgres to go distributed.\n- **Zero-infra observability** — tracing is **off by default**; opt in per stitch or via `STITCH_TRACE_*` env vars. No collector, no dashboard.\n- **Four front doors, one definition** — in-process function, CLI (`stitch run`), HTTP (`stitch serve`), and MCP (`stitch mcp`).\n- **Zero runtime dependencies** — `\"dependencies\": {}`, built on global `fetch`, tree-shakeable; **~25 kB min+gzip** for the whole entry, **~22 kB** for a typical `import { stitch }`.\n\n## Install\n\n```bash\nnpm install stitchapi@rc # or: pnpm add stitchapi@rc · yarn add stitchapi@rc\n```\n\nValidation is bring-your-own — pass a [Zod](https://zod.dev) schema or any [Standard Schema](https://standardschema.dev) validator; none is bundled. The examples below use Zod for familiarity, and `api.example.com` as an illustrative host — point them at your own API to run them, or try them as-is in the [playground](https://stitchapi.dev/?utm_source=github#playground), which serves that host from an in-browser simulator.\n\n## Quick start\n\nThe smallest stitch is a URL — declare once, call many times:\n\n```ts\nimport { stitch } from 'stitchapi';\n\nconst getUsers = stitch('https://api.example.com/users');\n\nconst users = await getUsers(); // GET, parsed JSON\n```\n\nPath params use [RFC 6570](https://datatracker.ietf.org/doc/html/rfc6570) URI templates; `params`, `query`, `headers`, and `body` all travel in one input object:\n\n```ts\nconst getUser = stitch('https://api.example.com/users/{id}');\n\nawait getUser({ params: { id: 1 }, query: { expand: 'roles' } });\n// → GET https://api.example.com/users/1?expand=roles\n```\n\nReach for the full set of knobs only when you need them — they default off:\n\n```ts\nconst getUser = stitch({\n path: 'https://api.example.com/users/{id}',\n output: User, // a validator of your choice\n pick: 'data',\n retry: 3, // ≡ { attempts: 3 }\n timeout: '5s', // ≡ { total: '5s' }\n cache: '1m', // ≡ { ttl: '1m' }\n});\n\nconst user = await getUser({ params: { id: 42 } });\n// → typed · validated · retried · cached\n```\n\nA stitch yields a typed **event stream**; `await` consumes it and returns the final value, while `.safe()` resolves to `{ ok, data, error }` and `.stream()` yields progress, throttle waits, retries, and drift as they happen.\n\n## Composition: seam, extends, `.with()`\n\nEverything reusable is a named value, and a stitch composes values — **no global config is ever required**. A service with more than one endpoint is a `seam`: declare the shared base, auth, and budget once; each endpoint is a member that inherits the config _and_ shares one runtime (throttle bucket, store, trace sink):\n\n```ts\nimport { seam } from 'stitchapi';\n\nconst api = seam({\n baseUrl: 'https://api.example.com',\n retry: { attempts: 3, on: [429, 503] },\n timeout: { total: '30s' },\n});\n\nconst listUsers = api.stitch({\n path: '/users',\n output: User.array(),\n pick: 'data',\n});\nconst getUser = api.stitch({\n path: '/users/{id}',\n output: User,\n pick: 'data',\n});\n```\n\nFor lighter reuse, `extends: [fragment | stitch]` merges config left→right (own fields win), and `.with()` pre-binds part of the input while reusing the same runtime. Full guide: [Authoring](https://stitchapi.dev/docs/guides/authoring/stitch?utm_source=github).\n\n## Validation & leveled drift\n\nThe declared `output` schema **is** the contract. Wrap it in `drift()`: a response is validated (the call returns the validated value — coerced, defaulted, unknown keys stripped), and the difference between the raw body and that validated value is reported as a leveled, non-fatal signal:\n\n| Change | What it means | Level |\n| -------------- | ---------------------------------------------------------- | --------- |\n| **invalid** | a required field missing or incompatible — **throws** | `error` |\n| **coerced** | a coercion (`\"42\"`→`42`): a wire-type shift validation hid | `warn` |\n| **undeclared** | a key the schema strips | `info` |\n| **defaulted** | a `.default()` fired (field absent) | `verbose` |\n\n```ts\nimport { drift, stitch } from 'stitchapi';\nimport { z } from 'zod';\n\nconst listOrders = stitch({\n path: 'https://api.example.com/users/{id}/orders',\n pick: 'data',\n output: drift(\n z.array(z.object({ id: z.number(), total: z.number().optional() })),\n {\n ignore: ['[].meta'], // acknowledged, unconsumed — don't report it\n severity: { coerced: 'info' }, // re-level a kind, or pass a level/list to filter\n },\n ),\n});\n```\n\nDrift is schema-anchored — no snapshot to manage. Severity lives in the schema: a required field missing/incompatible is a hard `invalid` that **throws**; everything else is non-fatal drift on the event stream. Declared variance (an optional field, a nullable, an empty array) validates clean, so it's never a false alarm; `ignore` silences known-but-unconsumed fields and `severity` filters or re-levels the soft signals. The request side validates too: `input` takes a schema per part and fails fast before any request is sent. Full guide: [Validation & drift](https://stitchapi.dev/docs/guides/validation/drift?utm_source=github).\n\n## Resilience: retry, throttle, timeout\n\nThe things every `src/api/` folder reinvents are configuration here — uniform across every stitch:\n\n```ts\nconst listUsers = stitch({\n baseUrl: 'https://api.example.com',\n path: '/users',\n retry: { attempts: 4, on: [429, 502, 503] },\n throttle: { rate: '1/s', concurrency: 2, pool: 'host' },\n timeout: { total: '30s', each: '10s' },\n});\n```\n\n`throttle` is proactive (keeps you under a limit before it bites; `pool: 'host'` shares a limiter across stitches), `retry` is reactive (backoff + `Retry-After`), and `timeout` aborts with a real `AbortSignal`. Three more knobs round it out: **`circuit`** fast-fails a dependency that's already down, **`idempotency`** injects a stable `Idempotency-Key` on writes, and **`verdict`** declares what counts as success — `accept` treats a non-2xx (e.g. `404`) as a normal result instead of a throw, `flag` fails a `200` whose body says it failed. Full guide: [Resilience](https://stitchapi.dev/docs/guides/resilience/retry?utm_source=github).\n\n## Caching\n\nA read-through response cache with in-process request coalescing — **off by default**, loaded lazily from `stitchapi/cache` only when a stitch sets `cache`. The key is **derived** from the resolved request (no caller-authored keys to drift) and **principal-scoped by default**, so user A is never served user B's cached response:\n\n```ts\nconst getUser = stitch({\n path: 'https://api.example.com/users/{id}',\n output: User,\n pick: 'data',\n cache: '5m',\n});\n\nconst listAnnouncements = stitch({\n path: 'https://api.example.com/announcements',\n output: z.array(z.object({ id: z.number(), title: z.string() })),\n pick: 'data',\n cache: {\n ttl: '1h',\n tenancy: 'app',\n vary: ['accept-language'],\n entries: 500,\n fingerprint: 1, // pins the shape — cacheable without a fingerprinter\n },\n});\n```\n\nCaching is sound by construction: a stitch with an `output` schema caches only when that schema can be fingerprinted or you pin a `fingerprint` tag — otherwise it **refuses to cache** rather than serve a stale shape. Mark sensitive data `sensitive: true` to opt out entirely.\n\n## Auth as a boundary\n\nAuth is a field on the stitch — never global. Secrets resolve **at call time** (`env()`, `secretsFile()`), the declaration is committable, and the caller gets data without ever seeing the credential:\n\n```ts\nimport { stitch } from 'stitchapi';\nimport { bearer, env } from 'stitchapi/auth';\n\nconst getUser = stitch({\n path: 'https://api.example.com/users/{id}',\n auth: bearer(env('API_TOKEN')), // resolved per call; the caller passes no secret\n});\n```\n\n`bearer`, `apiKey`, and `basic` are header strategies; `oauth2()` runs the client-credentials grant and caches/refreshes the token; and `cookieSession` runs a login, captures the cookie, replays it, and re-logs-in when the wall returns — the caller never sees the password or writes the cookie dance. Full guide: [Auth](https://stitchapi.dev/docs/guides/auth/bearer?utm_source=github).\n\n## Surfaces: any request style\n\nA **surface** is the request _style_ a stitch speaks. `http` is the default; the rest are peer surfaces on the same engine — `auth`, `retry`, `throttle`, `timeout`, validation, and the event stream compose with every one. Each ships as its own subpath import, so `import { stitch }` pulls in `http` alone.\n\n| Surface | Import | Shapes | `await` resolves to |\n| ------------- | ----------------------------- | ----------------------------------------- | ------------------------------ |\n| `http` | `stitch` (default) | a JSON-over-HTTP call | the validated body |\n| `graphql` | `stitchapi/graphql` | POST `{ query, variables }`, picks `data` | the `data` payload |\n| `sse` | `stitchapi/sse` | a `text/event-stream` reader (over fetch) | every parsed event, collected |\n| `stream` | `stitchapi/stream` | a raw `ReadableStream` reader | every decoded chunk, collected |\n| `download` | `stitchapi/download` | a buffered binary GET | `{ blob, filename }` |\n| `llm` | `stitchapi/llm` | a chat-completion via a provider contract | the normalised `{ text, … }` |\n| `shell` | `@stitchapi/shell` (peer pkg) | a local command, args + stdin | the command's stdout |\n| `postmessage` | `stitchapi/postmessage` | a typed iframe ↔ parent RPC / event call | the typed RPC response |\n\nFull guide: [Surfaces](https://stitchapi.dev/docs/reference/surfaces?utm_source=github).\n\n## Four front doors\n\nThe same typed unit is reachable four ways, so humans and agents call exactly the same validated, observable thing:\n\n| Front door | How | Example |\n| ----------------------- | --------------- | ------------------------- |\n| **In-process function** | import and call | `await listUsers()` |\n| **CLI command** | `stitch run` | `$ stitch run list-users` |\n| **HTTP endpoint** | `stitch serve` | `GET /list-users` |\n| **MCP / agent tool** | `stitch mcp` | `tool: list_users` |\n\n`stitch run` streams every event as one JSON line on stdout (ready for `jq`); `stitch trace` summarizes the run log — runs, failures, retries, drift, and latency percentiles. Full guide: [Surfaces → CLI](https://stitchapi.dev/docs/surfaces/cli?utm_source=github).\n\n## Agent-native\n\nA stitch is built to be invoked by an AI agent. Auth lives on the stitch, so an agent gets a **capability, not a credential**. And rather than one MCP tool per endpoint (which floods the model's context), an agent drives a single **code-mode** tool, `run_stitch`: it writes a small TypeScript snippet that imports `stitchapi` and calls the stitch, with `list_stitches` and `describe_stitch` for discovery — so the context budget stays flat as the catalog grows.\n\nAuthoring is agent-friendly too — hand an agent one `curl`/HAR/doc example and it emits a stitch declaration, with a deterministic shortcut for the common case:\n\n```bash\n$ stitch from-curl 'curl https://api.example.com/users/7 -H \"authorization: Bearer …\"'\n# prints a ready-to-commit stitch: id-like segments lifted to {params}, secrets → env()\n```\n\n`stitch init` writes the “declare a stitch, don't hand-roll `fetch`” rule into the files coding agents read (`AGENTS.md`, Cursor/Windsurf/Cline rules, a `CLAUDE.md` section), and the docs build emits an auto-generated [`llms.txt`](https://stitchapi.dev/llms.txt). Full guide: [Use from an agent](https://stitchapi.dev/docs/agents?utm_source=github).\n\n## Errors & pitfalls\n\nA failed stitch throws a `StitchError` — an `Error` subclass carrying `.status`, `.attempts`, and (for response failures) `.body` (the parsed error payload, on a non-enumerable channel that never reaches a trace sink) and `.url`. Prefer branching? `.safe()` resolves to `{ ok, data, error }`. Branch on `.status` and `.attempts` (plus `instanceof RateLimitError`) — the `STITCH_*` names below are **documentation IDs, not runtime values**, so there is no `error.code` to match on:\n\n| Catalog ID | When |\n| --------------------- | ----------------------------------------------------------------- |\n| `STITCH_VALIDATION` | a response failed its output schema |\n| `STITCH_DRIFT` | a response drifted past the level you allowed |\n| `STITCH_AUTH_WALL` | auth failed, or a soft `200` login wall couldn't be refreshed |\n| `STITCH_TIMEOUT` | a call exceeded its timeout budget |\n| `STITCH_CIRCUIT_OPEN` | the circuit breaker is open after repeated failures |\n| `STITCH_GRAPHQL` | a GraphQL response came back `200` but carried an `errors` array |\n| `RateLimitError` | a delegate-backoff stitch surfaced a rate-limit for an outer gate |\n\nFull catalog: [Errors & pitfalls](https://stitchapi.dev/docs/errors?utm_source=github).\n\n## Zero-infra observability\n\nObservability is a consumer of the event stream, not a separate system — and it's **off by default**. Opt in per stitch (`trace: 'console'` / `fileSink(path)` / a `TraceSink`) or globally with env vars — no collector, no dashboard, nothing to deploy:\n\n```bash\nSTITCH_TRACE_CONSOLE=1 node app.js # live, colored, one line per event on stderr\nSTITCH_TRACE_FILE=./run.jsonl node app.js # append JSONL to a path\nSTITCH_EXPORT=otlp node app.js # also fan events to an OTLP collector\n```\n\nBuilt-in sinks scrub secrets at the sink boundary (the live request is never touched). `stitch trace` summarizes the JSONL; [`@stitchapi/pino`](https://stitchapi.dev/docs/integrations/pino?utm_source=github) ships the same events as structured logs.\n\n## Packages\n\nThis repository is a [pnpm](https://pnpm.io) workspace. The published library is [`stitchapi`](https://github.com/rejifald/StitchAPI/blob/main/packages/core); the rest are thin, peer-dependency integrations that add no capability of their own. The table below is **generated** by `pnpm gen:readme` (and verified in CI by `pnpm check:readme`): it lists every publishable workspace package, so it never drifts as packages are added. Each package's own README links to it on npm.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Package	Description
Core
`stitchapi`	Turn any API into a typed, resilient function
Server frameworks
`@stitchapi/elysia`	Web-standard seam on the context; SSE and error mapping
`@stitchapi/express`	Request-scoped seam on req, with SSE and error mapping
`@stitchapi/fastify`	App/request seam with SSE, error and Pino-logger bridges
`@stitchapi/hono`	Edge-ready seam on the request context; SSE and errors
`@stitchapi/nest`	Injectable stitches wired into the Nest DI graph
`@stitchapi/next`	Stream a stitch as an SSE Response in the App Router
Client & UI bindings
`@stitchapi/angular`	Stitch lifecycle as Angular signals and an RxJS observable
`@stitchapi/expo`	Streaming over expo/fetch with a secure-store token store
`@stitchapi/query-core`	Framework-agnostic reactive store behind the UI bindings
`@stitchapi/react`	Tearing-free useStitch / useStitchStream hooks
`@stitchapi/react-native`	Streaming XHR adapter and AsyncStorage-backed store
`@stitchapi/solid`	createStitch primitives reconciled into a Solid store
`@stitchapi/svelte`	Stitch stores for Svelte 4 and 5 (unary + streaming)
`@stitchapi/vue`	Reactive useStitch / useStitchStream composables
Data-fetching libraries
`@stitchapi/rtk-query`	Run a stitch as an RTK Query endpoint, with stream updates
`@stitchapi/swr`	Run a stitch as an SWR fetcher; SWR owns caching
State stores
`@stitchapi/cloudflare-kv`	Edge cache and shared sessions on Workers KV
`@stitchapi/deno-kv`	Distributed throttle and sessions on Deno KV
`@stitchapi/redis`	Distributed throttle and shared sessions via Redis
Auth
`@stitchapi/aws-sigv4`	Sign requests with AWS SigV4 (edge-safe Web Crypto)
AI
`@stitchapi/vercel-ai`	Expose a stitch as a model-callable tool, credential-safe
Observability
`@stitchapi/pino`	The stitch event stream as structured Pino logs
`@stitchapi/sentry`	Stitch events as Sentry breadcrumbs, with error capture
Surfaces
`@stitchapi/download`	Batch file downloads with FIFO concurrency, cancel, and ETA
`@stitchapi/shell`	Run a static local command as a stitch (injection-proof)
Cache fingerprint adapters
`@stitchapi/fingerprint-arktype`	Cache-fingerprint strategy for ArkType schemas
`@stitchapi/fingerprint-effect`	Cache-fingerprint strategy for Effect Schema
`@stitchapi/fingerprint-typebox`	Cache-fingerprint strategy for TypeBox schemas
`@stitchapi/fingerprint-valibot`	Cache-fingerprint strategy for Valibot schemas
`@stitchapi/fingerprint-zod`	Cache-fingerprint strategy for Zod schemas
Other
`@stitchapi/docs-mcp`	StitchAPI documentation search, running locally over MCP stdio
`@stitchapi/json-schema`	Turn a runtime-discovered JSON Schema into a Standard Schema validator StitchAPI accepts
`@stitchapi/openapi`	Eject selected operations from an OpenAPI document into ready-to-own StitchAPI source

\n\n\n\n## Documentation\n\nThe full documentation site lives at **[stitchapi.dev](https://stitchapi.dev?utm_source=github)** — [Quickstart](https://stitchapi.dev/docs/getting-started/quickstart?utm_source=github), per-feature [Guides](https://stitchapi.dev/docs/guides/authoring/stitch?utm_source=github), [Concepts](https://stitchapi.dev/docs/concepts/the-stitch?utm_source=github), [Surfaces](https://stitchapi.dev/docs/surfaces/function?utm_source=github), [For agents](https://stitchapi.dev/docs/agents?utm_source=github), and the generated [Reference](https://stitchapi.dev/docs/reference/stitch?utm_source=github).\n\nThe published library's own README (what npm renders) is in [`packages/core/README.md`](https://github.com/rejifald/StitchAPI/blob/main/packages/core/README.md). Design notes live in [`docs/`](https://github.com/rejifald/StitchAPI/blob/main/docs): [Feature Lenses](https://github.com/rejifald/StitchAPI/blob/main/docs/FEATURE-LENSES.md), [Overview](https://github.com/rejifald/StitchAPI/blob/main/docs/OVERVIEW.md), [Design](https://github.com/rejifald/StitchAPI/blob/main/docs/DESIGN.md).\n\n## Contributing\n\nLocal setup, the dev loop, the bundle-size budget, and the worktree + PR workflow are documented in [`CONTRIBUTING.md`](https://github.com/rejifald/StitchAPI/blob/main/CONTRIBUTING.md).\n\n## License\n\n[Apache-2.0](https://github.com/rejifald/StitchAPI/blob/main/LICENSE)\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"upstream",{"_101":102,"_103":104,"_105":106,"_107":108,"_109":110,"_111":112},"requiredSecrets",[],"tags",[99,100],"assets",[],"stats",{"_97":86,"_98":86},"ratingAvg","reviewCount","npm-package","typescript","topics",[119,120,121,99,100],"license","Apache-2.0","language","TypeScript","registryName","dev.stitchapi/docs","homepage","https://stitchapi.dev","packages",[113],{"_114":115,"_116":117,"_76":118},"registryType","npm","identifier","@stitchapi/docs-mcp","1.0.0-rc.5","api","mcp","mcp-server","ENV",{"_124":125,"_126":127,"_128":129},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]