@secure-ai/guard 0.2.0 → 0.2.1
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.
- package/README.md +1 -1
- package/dist/index.js +14 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -133,7 +133,7 @@ cause in a process already carrying too many.
|
|
|
133
133
|
## Also available over MCP
|
|
134
134
|
|
|
135
135
|
Agents that speak MCP can reach the same controls as tools at
|
|
136
|
-
`https://
|
|
136
|
+
`https://secureai.one/mcp` — `inspect_action`, `check_policy`,
|
|
137
137
|
`recent_activity`, plus `redact` and `restore`.
|
|
138
138
|
|
|
139
139
|
Full reference: <https://secureai.one/developers>
|
package/dist/index.js
CHANGED
|
@@ -82,7 +82,20 @@ export class SecureAIError extends Error {
|
|
|
82
82
|
this.code = code;
|
|
83
83
|
}
|
|
84
84
|
}
|
|
85
|
-
|
|
85
|
+
/**
|
|
86
|
+
* Where the client talks to, when nobody says otherwise.
|
|
87
|
+
*
|
|
88
|
+
* This was an api. subdomain in 0.2.0, and that host does not
|
|
89
|
+
* exist -- it was never created. Nothing caught it: the tests
|
|
90
|
+
* pass a baseUrl, the typecheck has no opinion about a string, and the
|
|
91
|
+
* package published cleanly. The first person to install the SDK and follow
|
|
92
|
+
* the README would have got ENOTFOUND on their first call.
|
|
93
|
+
*
|
|
94
|
+
* secureai.one/v1 is the address the docs have always given and it is
|
|
95
|
+
* proxied to the Worker, so this is the same endpoint the curl examples hit.
|
|
96
|
+
* Keep the two in step: docs/api.md in the web repo is the other half.
|
|
97
|
+
*/
|
|
98
|
+
const DEFAULT_BASE = "https://secureai.one";
|
|
86
99
|
export class SecureAI {
|
|
87
100
|
apiKey;
|
|
88
101
|
baseUrl;
|