@rudra-js/anthropic 0.7.2 → 0.7.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +27 -7
  2. package/package.json +3 -3
package/README.md CHANGED
@@ -12,7 +12,7 @@ This adapter is documented at [rudrajs.com](https://rudrajs.com/docs#createAnthr
12
12
  ## Install
13
13
 
14
14
  ```sh
15
- npm install @rudra-js/anthropic @rudra-js/core
15
+ npm install @rudra-js/anthropic @rudra-js/core @rudra-js/attested
16
16
  ```
17
17
 
18
18
  ```ts
@@ -85,13 +85,33 @@ or a region-specific endpoint you have.
85
85
 
86
86
  What's in that request is listed under **What the model sees** in the
87
87
  [`@rudra-js/core` README](https://github.com/clivedsouza1010/rudra-js/tree/main/packages/core#what-the-model-sees).
88
- Read it before you send real shopper traffic. In cohort mode, the default, the
89
- request carries no individual. In per-shopper mode it carries that shopper's
90
- likes, dislikes, purchases, basket, views and recent searches.
88
+ Read it before you send real shopper traffic. Neither mode sends `user.id`. In
89
+ cohort mode, the default, the request can still be personal data: it names the
90
+ category that shopper leans towards most, says whether they have any history,
91
+ carries any `segment` you gave them as you wrote it, and lists candidates you
92
+ may have picked or ordered just for them. In per-shopper mode it also carries
93
+ the product that shopper is looking at, their current and recent searches,
94
+ whether they're returning, their likes, dislikes, purchases, basket, most-viewed
95
+ products, the categories they lean towards and interaction counts.
96
+
97
+ If your shop is in the EU or the UK, or sells to shoppers there, you're the one
98
+ sending personal data out. You'll need a data processing agreement with whoever
99
+ receives it, and a transfer mechanism if they're outside the EU or the UK, even
100
+ when your shop is outside them too.
101
+
102
+ Call Anthropic with a key from your own Anthropic account and the receiver is
103
+ Anthropic. Its data processing addendum is part of its Commercial Terms, makes
104
+ Anthropic your processor and includes the transfer clauses. Your shop is
105
+ Anthropic's customer. A proxy you run yourself that forwards to Anthropic
106
+ doesn't change that.
107
+
108
+ If you point `baseUrl` at a gateway or platform run by someone other than you or
109
+ Anthropic, its operator sees every request and the `apiKey` you pass. If that's
110
+ a key from your own Anthropic account, Anthropic is still your processor and the
111
+ operator is another one, so you need a DPA with the operator as well. If the
112
+ platform issued the key, Anthropic says the platform's terms govern that use:
113
+ you're the platform's customer, and its DPA is the one that covers you.
91
114
 
92
- If your shop is in the EU or the UK, you're the one sending personal data to
93
- Anthropic, so you'll need a data processing agreement with them plus a transfer
94
- mechanism for the data leaving your region. Your shop is Anthropic's customer.
95
115
  This package is a piece of code in the middle, and it _isn't_ a party to
96
116
  anything.
97
117
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rudra-js/anthropic",
3
- "version": "0.7.2",
3
+ "version": "0.7.4",
4
4
  "description": "An Anthropic adapter for @rudra-js/core, with no vendor SDK",
5
5
  "keywords": [
6
6
  "anthropic",
@@ -50,10 +50,10 @@
50
50
  "zod": "^4.0.0"
51
51
  },
52
52
  "peerDependencies": {
53
- "@rudra-js/core": "^0.7.2"
53
+ "@rudra-js/core": "^0.7.4"
54
54
  },
55
55
  "devDependencies": {
56
- "@rudra-js/core": "0.7.2",
56
+ "@rudra-js/core": "0.7.4",
57
57
  "@types/node": "^26.4.1"
58
58
  }
59
59
  }