diff --git a/docs/content/1.get-started/5.tips/6.response-caching.md b/docs/content/1.get-started/5.tips/6.response-caching.md
new file mode 100644
index 0000000..29710cb
--- /dev/null
+++ b/docs/content/1.get-started/5.tips/6.response-caching.md
@@ -0,0 +1,49 @@
+---
+title: Response Caching
+---
+
+Your server responses must [satisfy some criteria](https://vercel.com/docs/concepts/functions/serverless-functions/edge-caching) in order for them to be cached (i.e. by Vercel's Edge Network). Please refer to [this section of the tRPC.io documentation](https://trpc.io/docs/caching) for more information.
+
+The createNuxtApiHandler` function conveniently allows you to specify a `responseMeta` function.
+
+```ts [server/api/trpc/[trpc].ts]
+import { createNuxtApiHandler } from 'trpc-nuxt'
+import { appRouter } from '~/server/trpc/routers'
+
+export default createNuxtApiHandler({
+  router: appRouter,
+  /**
+   * @link https://trpc.io/docs/caching#api-response-caching
+   */
+  responseMeta(opts) {
+    // cache request for 1 day + revalidate once every second
+    const ONE_DAY_IN_SECONDS = 60 * 60 * 24;
+
+    return {
+      headers: {
+        'cache-control': `s-maxage=1, stale-while-revalidate=${ONE_DAY_IN_SECONDS}`,
+      },
+    };
+  },
+})
+```
+
+You can also take advantage of Nitro's [Cache API](https://nitro.unjs.io/guide/cache#cache-api) if doing server-side calls:
+
+```ts
+import { appRouter } from '@/server/trpc/routers'
+
+const caller = appRouter.createCaller({})
+
+export default cachedEventHandler(async (event) => {
+  const { name } = getQuery(event)
+
+  const greeting = await caller.greeting({ name })
+
+  return {
+    greeting
+  }
+}, {
+  swr: true, maxAge: 10
+})
+```