@webdecoy/ai-protection 0.1.0-alpha.1

package/ARCHITECTURE.md

@@ -0,0 +1,166 @@
+# Local rules + cloud detection
+
+The SDK makes deterministic application-policy decisions locally and delegates bot
+classification to WebDecoy. No detector weights, threat intelligence, WebAssembly
+engine, prompt inspection or remote executable policies are shipped here.
+
+```text
+Customer authenticates, validates input and loads trusted application context
+  → synchronous local rules
+      enforced denial/error → decision (no blocking cloud check)
+      otherwise → resolve trusted IP → WebDecoy account/config + detection
+  → immutable combined decision
+  → customer's application or convenience wrapper enforces it
+  → response streams unchanged
+  → bounded, best-effort central reporting and application observation sink
+```
+
+## Decision API
+
+`createAIProtection(options)` remains callable as
+`protect(request, handler, context?)`. It also exposes:
+
+- `check(request, context)` → immutable decision, no automatic normal-outcome report.
+- `report(decision, outcome?)` → best-effort reporting promise; once per decision
+  created by that instance. Foreign/already-reported decisions are ignored.
+- `flush()` → waits for currently queued reports up to their individual timeouts.
+
+A decision contains `id`, `conclusion` (`allow`/`deny`), a stable `reason`, denial
+`status`, `degraded`, and `checks`. Each check has its source, mode, verdict, reason
+and duration. A remote denial observed in cloud observation mode remains visible
+in `checks` while the overall decision allows. Missing IP/account/detector or a
+failed local rule marks coverage degraded; deliberate remote skipping after a
+local denial does not.
+
+`check()` does not invoke a model or grant authentication. Keep auth, origin
+validation, input validation and quotas before it. For direct use, recheck
+`request.signal.throwIfAborted()` immediately before starting inference. The
+wrapper does this automatically and returns the original Response unmodified.
+Cancellation during remote admission throws and emits a best-effort cancellation
+record; it never produces a usable allow decision.
+
+## Trusted context and local rules
+
+Context comes from the application's server code. The SDK cannot establish its
+truth: use verified sessions, database entitlements and validated operation names.
+Never spread a request body into this context or accept a browser's plan/user claim.
+Context is passed only to local rules. The SDK neither serializes it to detection
+nor copies it into observation records.
+
+```ts
+const protect = createAIProtection<{canGenerate: boolean}>({
+  // ...existing connection and trusted-IP configuration
+  rules: [{
+    id: 'generation_entitlement',
+    mode: 'enforce',
+    evaluate: context => ({
+      allowed: context.canGenerate,
+      reason: 'generation_entitlement_required',
+    }),
+  }],
+});
+```
+
+Rules must be synchronous, deterministic and cheap; load external state before
+calling protection. A rule returns `{allowed, reason?, status?}`. Denial status
+may be 403 or 429. `id` and `reason` must be stable non-sensitive codes: a lowercase
+letter followed by up to 63 lowercase letters, digits or underscores. Do not put
+user identifiers, prompts or exception messages in codes; these enter reports
+and denial reasons can reach the caller.
+
+Rules default to **observe**. Each rule's mode is independent of cloud
+`protectionMode`, plan entitlement and the dashboard's AI mode. Setting cloud
+observation does not disable explicitly enforced customer rules. Customer rules
+are application policies, not paid WebDecoy detection features.
+
+All local rules run in declaration order; the first enforced denial determines
+HTTP status/reason. Local allow means continue evaluation, never bypass cloud
+protection. Any enforced local denial skips the blocking detection request; reporting follows asynchronously. Rule throws,
+malformed values and accidental promises are `local_rule_error`; raw exceptions
+are never logged. A rule in enforce mode defaults to `failureMode: 'closed'`
+(503); explicit `open` permits later checks. Observe rules never enforce errors.
+
+## Availability matrix
+
+| Condition | Default outcome |
+|---|---|
+| Enforced local rule denies | Deny locally, including during a WebDecoy outage |
+| Enforced local rule fails | 503, unless that rule explicitly opts into fail-open |
+| Observed local rule denies/fails | Continue, expose result in decision |
+| Remote detector unavailable | Allow, expose degraded coverage |
+| Account unavailable/mismatched | Observe and skip remote scoring |
+| Missing trusted IP | Skip remote scoring; successful local checks still apply |
+| Report fails, times out or queue fills | Decision/response unchanged; log a generic warning |
+| Caller aborts | Stop; never start the protected callback |
+
+Only the existing verified account configuration is cached (60 seconds; failures
+5 seconds). We do not cache detector allow verdicts or turn the process-local shadow counter
+into a spend limit. Explicit shared quota, concurrency and budget hooks use the
+server state protocols; they are independent of the detector cache.
+A secure decision cache needs explicit scoping, policy versions and invalidation;
+cached allow results must not accidentally bypass fresh checks or counters.
+
+## Reporting and hosting lifecycle
+
+The remote `/sdk/detect` request still creates its existing server-side detection
+record. A separate `POST /api/v1/sdk/ai-abuse/reports` endpoint receives the SDK's
+final decision/outcome, including local-only denials and degraded checks. The
+property-scoped key and matching `X-WebDecoy-Property-ID` assertion bind attribution;
+the payload cannot select a tenant. Unknown fields are rejected. Only request ID,
+timestamp, decision/reason, check IDs/sources/modes/verdicts/durations, degraded
+status, handler invocation/status and action are sent. Prompts, user IDs, context,
+raw IPs and subject hashes are excluded from this reporting payload.
+
+Central reporting is enabled by default (`reportToWebDecoy: true`). Set it to
+false to keep application observation without sending these reports. The local
+`onObservation` sink still defaults to JSON stdout and is independent: a failing
+custom sink cannot prevent central delivery, and vice versa. Do not place sensitive
+values in rule IDs/reason codes.
+
+Ingest deduplicates by organization/property/request ID: the first accepted report
+wins, including its receipt time. There are no automatic retries. Reports are
+bounded to 32 KiB and 36 checks (32 local rules, quota, concurrency, cloud and browser evidence). The pilot endpoint
+limits traffic to 6000 reports/minute per source IP with a burst of 200; excess
+reports are dropped by this SDK after a generic warning, without affecting chat.
+
+The dashboard presents these as **SDK-reported application decisions**, separate
+from server-derived detector evidence. They are not summed into detection counts,
+charged as detections, or treated as proof of blocked inference or savings. The
+same request ID lets users correlate the two sources. Counts use receipt time;
+reports have a seven-day window and hourly retention cleanup. A prolonged outage
+can prevent delivery, so this is not complete audit coverage.
+
+`onObservation(event, {signal})` can return a promise. `report()` catches rejection,
+limits outstanding reports (`maxPendingReports`, default 100), and stops waiting
+at `reportingTimeoutMs` (default 1000). Sinks must honor the AbortSignal and avoid
+CPU-heavy synchronous work; JavaScript cannot forcibly stop arbitrary sink code.
+No retries, durable queue or exactly-once delivery is claimed.
+
+Use `waitUntil(task)` to attach reporting to the deployment's request lifecycle.
+For a Next.js route:
+
+```ts
+import { after } from 'next/server';
+// In createAIProtection options:
+// waitUntil: task => after(() => task)
+```
+
+This registers delivery with Next.js's supported lifecycle mechanism; the hosting
+adapter must support it and execution remains subject to host duration limits.
+Do not use an untracked fire-and-forget promise as a delivery guarantee. In a
+long-lived Node service, call `flush()` during graceful shutdown. Tests can await
+`report()`/`flush()` directly. Neither mechanism proves stream completion or actual
+provider usage; wrapper records stop at Response creation.
+
+Reference: [Next.js after](https://nextjs.org/docs/app/api-reference/functions/after).
+
+## Current controls and usage reporting
+
+Shared account quotas run before remote detection. `concurrent` explicitly wraps
+bounded model work with distributed leases. `createAIBudget` reserves/settles each
+provider attempt; it is not an automatic middleware spending cap. Both controls
+default to observe/open; enforce/closed is an explicit state-availability tradeoff.
+Usage events are separate from schema-1 request reports and include numeric rates,
+tokens and call/request/reservation UUIDs. They do not include raw identities or
+model content. See README and RELEASE.md; backend contracts are maintained in the
+private app repository's integrations/ai-abuse documentation.

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NEXTJS.md

@@ -0,0 +1,177 @@
+# Next.js / AI SDK pilot integration
+
+Status: local, experimental Node server adapter with local rules and cloud detection. Not published to npm or deployed.
+No Next.js dependency in the adapter: it uses standard `Request` / `Response` and
+can be called by other Node frameworks, but only the Next.js example is tested.
+
+## Where it runs
+
+```
+Browser → customer's /api/chat → existing auth / input checks
+                             → WebDecoy admission (metadata only)
+                             → customer's model provider → original stream
+```
+
+Install in the application server that owns the model call, not the browser,
+Next.js middleware, or the model provider. Node >=22.22.3 is required; Edge runtime
+is not supported. The application and provider traffic remain on customer
+infrastructure. WebDecoy receives the client IP, URL pathname (no query string),
+method, user agent, header names and accept-language/accept-encoding values.
+Request bodies, session cookies, authorization values and responses are not sent
+to WebDecoy. Opt-in browser evidence forwards only its WebDecoy receipt cookie.
+Avoid sensitive identifiers in route paths. This is a remote metadata decision,
+not proof that a caller is human. Optional browser evidence is a separate opt-in.
+
+## Install the local pilot
+
+From this repository:
+
+```sh
+cd ai-protection
+npm pack --pack-destination /tmp
+```
+
+From the customer's application:
+
+```sh
+npm install /tmp/webdecoy-ai-protection-0.1.0-alpha.1.tgz
+```
+
+The tarball contains the adapter, declarations and shared core; it does not
+need this checkout at runtime. The initial npm release is pending. Once published, install the pilot with
+`npm install @webdecoy/ai-protection@alpha`. There is no automatic marketplace installer.
+
+1. In WebDecoy, select an existing property on **AI Abuse Protection**.
+2. Create a property-scoped key with Write Detections permission.
+3. Set server-only environment variables: `WEBDECOY_URL` (your ingest origin),
+   `WEBDECOY_KEY`, `WEBDECOY_PROPERTY_ID`, and `WEBDECOY_SUBJECT_SECRET` (random,
+   at least 32 characters). Never use `NEXT_PUBLIC_` for these.
+4. Create one protection instance per application scope, outside the route.
+5. Call it after your authentication, origin/input checks and quotas, immediately
+   before the code that invokes the model.
+
+```ts
+// app/api/chat/route.ts — incorporate into your existing authenticated route
+import { createAIProtection } from '@webdecoy/ai-protection';
+import { after } from 'next/server';
+
+export const runtime = 'nodejs';
+const protect = createAIProtection({
+  webdecoyUrl: process.env.WEBDECOY_URL!,
+  webdecoyKey: process.env.WEBDECOY_KEY!,
+  propertyId: process.env.WEBDECOY_PROPERTY_ID!,
+  subjectSecret: process.env.WEBDECOY_SUBJECT_SECRET!,
+  scopeId: 'support-chat',
+  route: '/api/chat',
+  protectionMode: 'observe',
+  waitUntil: task => after(() => task),
+  resolveClientIP: trustedClientIP, // Your ingress-specific implementation; see below.
+});
+
+// Inside POST, AFTER your existing authentication and input validation:
+// return protect(request, () => {
+//   const result = streamText({ model, messages, abortSignal: request.signal });
+//   return result.toUIMessageStreamResponse({ consumeSseStream: consumeStream });
+// });
+```
+
+`trustedClientIP` is intentionally application supplied. Use a hosting API that
+vouches for the address, or a header overwritten by a reverse proxy you control
+with direct origin access blocked. Do not simply read arbitrary `X-Forwarded-For`
+or `X-Real-IP` from public requests. The adapter validates a single IPv4/IPv6
+address, not a comma-separated forwarding chain. Missing/invalid addresses allow
+the request without scoring and emit `webdecoy_admission_skipped`; this is degraded
+coverage, not successful protection. Resolver exceptions propagate as application errors. Async resolution has a
+1000ms default timeout and receives `{signal}` as a second argument; timeout skips
+cloud scoring as degraded coverage. Use `route` for an explicit non-sensitive
+route template. Test spoofed forwarding headers against the deployed ingress before
+switching to enforcement.
+
+Keep existing request-size limits at the ingress and application. The adapter
+never reads, clones or buffers the body. It does not add authentication, CORS or CSRF protection. Shared quota, concurrency
+and budget controls require their separate explicit configuration; the basic
+wrapper alone supplies none of those limits.
+
+## Local policies and explicit decisions
+
+The callable wrapper accepts a third argument containing trusted server context.
+Configure `rules` to inspect that context locally, or use `protect.check()` and
+`protect.report()` for custom response handling. See [the architecture contract](ARCHITECTURE.md).
+Context stays local. Rule IDs/reasons are stable non-sensitive codes that can enter logs.
+
+**Cloud observation does not override explicitly enforced local rules.** Each
+local rule defaults to observe; when explicitly enforced, its denial/error remains
+active during a cloud outage. The example's local `plan_input_limit` rule allows
+up to 4000 input characters for its server-configured free plan, while the route's
+input validation caps all prompts at 8000 characters. `EXAMPLE_PLAN` is a local
+fixture setting; production should load entitlements from authenticated server state.
+A `plan` field in the request body is ignored.
+
+The example uses Next.js `after()` to keep best-effort observation delivery tied
+to the request lifecycle. Local-only outcomes and degraded checks are sent to
+WebDecoy's application-decision reporting endpoint and the local sink (stdout by
+default). The dashboard distinguishes SDK reports from server-generated detector
+records; the same request ID correlates them. `reportToWebDecoy: false` opts out
+of central outcome reporting. Deploy the compatible reporting endpoint before
+enabling the pilot; absent/unavailable reporting never changes request decisions.
+
+## Behavior customers should expect
+
+- Start with cloud and dashboard observation, and each local rule in observe mode. Review real traffic and false
+  positives before enabling both enforcement settings on an entitled plan.
+- Enforced cloud block/challenge: JSON 403 before the protected callback. There is no
+  interactive challenge flow; handle `verification_required` in the chat UI.
+- WebDecoy outage/timeouts: allow by default. Unknown account binding always
+  observes and skips scoring. Missing trusted IP also skips scoring.
+- Cancellation during admission: throw the request's abort reason, never invoke
+  the callback. Forward `request.signal` to the AI SDK for later cancellation.
+- Allowed response: exact original Response, including streaming body and headers.
+  No buffering, background stream reader or response rewriting by WebDecoy.
+- Logs record callback invocation and returned HTTP status, **not** stream
+  completion, model invocation, tokens saved or provider billing. Existing core
+  `upstream_attempted` remains false: this adapter cannot observe model activity.
+- Account policy caches and per-call timeouts are documented in README. Cold remote admission can wait roughly two seconds with defaults, plus up to
+  one second of IP resolution. Optional quota, lease acquisition and reservation
+  each add their own deadline. See RELEASE.md.
+
+Use the AI SDK's documented `consumeSseStream: consumeStream` handling alongside
+`abortSignal` when returning UI streams. Provider cancellation/billing remains
+provider dependent. The adapter cannot promise refunded or unbilled tokens.
+
+## Runnable example and validation
+
+`examples/nextjs` contains an authenticated POST endpoint using a deterministic
+local AI SDK model; it cannot incur model-provider costs. Its hardcoded test IP
+is enabled only by `WEBDECOY_LOCAL_FIXTURE=1` and is not production configuration.
+
+```sh
+cd examples/nextjs
+npm ci
+npm run build -- --webpack
+npm test
+```
+
+The test starts a real Next.js production server and a local detector/account
+fixture; no secrets required. It checks authentication/input validation before
+scoring, UI-message SSE response, enforced rejection, and outage fail-open.
+Root `npm test` covers local decisions, reporting failure isolation, cancellation during admission, streaming cancellation,
+unchanged response identity, metadata privacy and missing-IP behavior.
+
+For a real pilot, replace the mock model with the application's existing model,
+configure trusted ingress/IP resolution, connect staging ingest/backend and
+verify a stored check appears for the selected property. Real abuse/legitimate
+traffic labels are still needed to measure detection value. These tests validate
+integration mechanics, not detection accuracy or demand.
+
+## Why this integration, and the competitive limit
+
+Vercel already offers [BotID for AI endpoints](https://vercel.com/kb/guide/protect-ai-endpoints-with-vercel-botid),
+including browser-side challenges and server checks. This is not evidence of an
+unprotected Vercel market. The hypothesis is existing WebDecoy customers and
+applications wanting the same account/policies on other Node hosting. Portability
+is an integration property, not yet demonstrated differentiation or demand.
+
+The integration follows Next.js's [standard Route Handler APIs](https://nextjs.org/docs/app/getting-started/route-handlers)
+and the AI SDK's [abort handling guidance](https://ai-sdk.dev/docs/troubleshooting/stream-abort-handling).
+Versions pinned for this fixture: Next.js 16.3.6, AI SDK 7.0.117, React 19.3.0.
+No compatibility claim for every Next.js/AI SDK version or other hosting platform.

package/NOTICE

@@ -0,0 +1,2 @@
+WebDecoy AI Protection
+Copyright 2026 WebDecoy