@rely-net/sdk 1.0.2 → 1.0.4

package/README.md

@@ -5,6 +5,7 @@ Official SDK for [rely.net](https://rely.net) — monitor your application from
 ## What it does
 
 - Sends health check results from inside your app to rely.net
+- Attributes outgoing HTTP calls to vendors (Stripe, OpenAI, etc.) with per-vendor p95 + error rates
 - Tracks custom metrics alongside vendor status
 - Marks deployments on your monitoring charts
 - Captures request telemetry (error rate, response times)
@@ -16,6 +17,46 @@ Official SDK for [rely.net](https://rely.net) — monitor your application from
 npm install @rely-net/sdk
 ```
 
+## Install with a coding agent
+
+Paste the prompt below into Claude Code, Codex, Cursor, or your agent of choice. It will install the SDK, wire up health checks for the services your app actually depends on, and integrate the Next.js middleware.
+
+```
+Install the @rely-net/sdk package to monitor this Next.js app.
+
+Do the following:
+
+1. Install the package:
+   npm install @rely-net/sdk
+
+2. Create /instrumentation.ts at the project root with:
+   - A Rely client initialized from process.env.RELY_API_KEY
+   - One healthCheck() for each external service this app depends on.
+     Look through the codebase for env vars like SUPABASE_*, STRIPE_*,
+     ANTHROPIC_API_KEY, OPENAI_*, and add a health check for each.
+     Use the patterns in the README below.
+
+3. Update middleware.ts to wrap the existing middleware with
+   withRelyMiddleware(rely, existingMiddleware). If there is no existing
+   middleware, export withRelyMiddleware(rely) directly. Keep the matcher
+   excluding _next/static, _next/image, and favicon.ico.
+
+4. Add RELY_API_KEY= to .env.local and mention that the user needs to
+   get their API key from rely.net/settings/api-keys and add it to
+   production env vars as well.
+
+5. Run a build to verify nothing is broken.
+
+Reference README with health check snippets for common services:
+https://github.com/mdicarlo-scaled/rely-net
+
+The SDK automatically wraps global fetch to track outgoing vendor
+calls (Stripe, Anthropic, Supabase, etc.) with p50/p95/p99 latency and
+error rates, so no additional code is needed beyond the above steps.
+```
+
+For non-Next.js frameworks, drop step 3 (the middleware integration).
+
 ## Quick start (Next.js)
 
 ### 1. Get your API key
@@ -145,6 +186,21 @@ export const config = {
 }
 ```
 
+## Outgoing vendor calls
+
+The SDK wraps the global `fetch` on init to bucket outgoing HTTP calls by hostname and report p50/p95/p99 + error rates per vendor. rely.net matches hostnames to known vendors (Stripe, OpenAI, Supabase, etc.) so you see vendor latency from your app's perspective — the answer to "is it me or is it Stripe?" without writing any code.
+
+Enabled by default. Disable with:
+
+```ts
+new Rely({
+  apiKey: process.env.RELY_API_KEY!,
+  instrumentFetch: false,
+})
+```
+
+Self-calls to the rely.net ingest endpoint are always skipped.
+
 ## Deployment markers
 
 Deployment markers are sent automatically when the SDK initializes. They appear as vertical lines on your charts in rely.net, making it easy to correlate issues with deploys.
@@ -167,6 +223,7 @@ new Rely({
   environment?: string,     // default: process.env.NODE_ENV
   flushInterval?: number,   // default: 60000 (ms)
   sanitizeErrors?: boolean, // default: true (recommended)
+  instrumentFetch?: boolean,// default: true (wraps global fetch)
   debug?: boolean,          // default: false
 })
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rely-net/sdk",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Official SDK for rely.net — monitor your app from the inside",
   "main": "dist/index.js",
   "module": "dist/index.mjs",