cortexhub 1.0.0__tar.gz → 1.0.2__tar.gz

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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: cortexhub
3
- Version: 1.0.0
3
+ Version: 1.0.2
4
4
  Summary: MCP gateway client for cortexhub agents — authenticate, hand the MCP URL to your framework of choice, done.
5
5
  Project-URL: Homepage, https://cortexhub.ai
6
6
  Project-URL: Documentation, https://docs.cortexhub.ai
@@ -159,29 +159,20 @@ The MCP gateway URL is fixed — `https://api.cortexhub.ai/v1/mcp-http`. There i
159
159
 
160
160
  - Route per-end-user OAuth tokens (when the toolkit needs them)
161
161
  - Attribute every tool call to that user in the audit log
162
- - Evaluate per-user budget caps and rate limits
163
162
 
164
163
  Calling `create()` with the same `user_id` twice is a no-op — the session is fully local and cheap to construct.
165
164
 
166
- ## What this SDK doesn't do
165
+ ## What runs where
167
166
 
168
- The cortexhub MCP gateway is the source of truth for governance. The SDK has no:
169
-
170
- - Decorators (no `@cx.tool` — the gateway discovers tools from your registered toolkits)
171
- - Local Policy evaluation
172
- - Local PII / secret / prompt-injection scanning
173
- - Local span recording / OTLP export
174
-
175
- All of that runs server-side at the gateway when the agent calls a tool through the URL above. The SDK is a thin wrapper around two strings (URL + headers).
176
-
177
- ## Migrating from cortexhub 0.5.x
178
-
179
- The v1 SDK is a complete rewrite. The decorator surface (`@cx.tool`, `cx.session`, `cx.run`, `cx.llm_call`, `cx.enforce`, …) is gone. If you used 0.5.x:
167
+ | Concern | Where it runs |
168
+ |---|---|
169
+ | Authentication, session construction | This SDK (local, fully offline) |
170
+ | Tool discovery, tool execution | cortexhub MCP gateway → toolkits you've attached |
171
+ | Per-end-user OAuth resolution | cortexhub MCP gateway |
172
+ | Per-tool policies + HITL approvals | cortexhub MCP gateway |
173
+ | Audit log of every tool call | cortexhub MCP gateway |
180
174
 
181
- 1. Remove `cortexhub.init()` calls.
182
- 2. Remove `@cx.tool` decorators — your tools come from cortexhub toolkits configured in the dashboard.
183
- 3. Replace the function-call orchestration with an MCP-aware framework (Claude Agent SDK, OpenAI Agents, Vercel AI SDK, LangGraph, …).
184
- 4. Use the snippets above to wire the MCP gateway into the framework.
175
+ The SDK itself is a thin wrapper around two strings (URL + headers). Everything else is server-side.
185
176
 
186
177
  ## License
187
178
 
@@ -136,29 +136,20 @@ The MCP gateway URL is fixed — `https://api.cortexhub.ai/v1/mcp-http`. There i
136
136
 
137
137
  - Route per-end-user OAuth tokens (when the toolkit needs them)
138
138
  - Attribute every tool call to that user in the audit log
139
- - Evaluate per-user budget caps and rate limits
140
139
 
141
140
  Calling `create()` with the same `user_id` twice is a no-op — the session is fully local and cheap to construct.
142
141
 
143
- ## What this SDK doesn't do
142
+ ## What runs where
144
143
 
145
- The cortexhub MCP gateway is the source of truth for governance. The SDK has no:
146
-
147
- - Decorators (no `@cx.tool` — the gateway discovers tools from your registered toolkits)
148
- - Local Policy evaluation
149
- - Local PII / secret / prompt-injection scanning
150
- - Local span recording / OTLP export
151
-
152
- All of that runs server-side at the gateway when the agent calls a tool through the URL above. The SDK is a thin wrapper around two strings (URL + headers).
153
-
154
- ## Migrating from cortexhub 0.5.x
155
-
156
- The v1 SDK is a complete rewrite. The decorator surface (`@cx.tool`, `cx.session`, `cx.run`, `cx.llm_call`, `cx.enforce`, …) is gone. If you used 0.5.x:
144
+ | Concern | Where it runs |
145
+ |---|---|
146
+ | Authentication, session construction | This SDK (local, fully offline) |
147
+ | Tool discovery, tool execution | cortexhub MCP gateway → toolkits you've attached |
148
+ | Per-end-user OAuth resolution | cortexhub MCP gateway |
149
+ | Per-tool policies + HITL approvals | cortexhub MCP gateway |
150
+ | Audit log of every tool call | cortexhub MCP gateway |
157
151
 
158
- 1. Remove `cortexhub.init()` calls.
159
- 2. Remove `@cx.tool` decorators — your tools come from cortexhub toolkits configured in the dashboard.
160
- 3. Replace the function-call orchestration with an MCP-aware framework (Claude Agent SDK, OpenAI Agents, Vercel AI SDK, LangGraph, …).
161
- 4. Use the snippets above to wire the MCP gateway into the framework.
152
+ The SDK itself is a thin wrapper around two strings (URL + headers). Everything else is server-side.
162
153
 
163
154
  ## License
164
155
 
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "cortexhub"
3
- version = "1.0.0"
3
+ version = "1.0.2"
4
4
  description = "MCP gateway client for cortexhub agents — authenticate, hand the MCP URL to your framework of choice, done."
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.10"
@@ -30,8 +30,7 @@ from .errors import (
30
30
  )
31
31
  from .session import Session, SessionMcp
32
32
 
33
- __version__ = "1.0.0"
34
-
33
+ __version__ = "1.0.1"
35
34
  __all__ = [
36
35
  "Cortexhub",
37
36
  "Session",
File without changes
File without changes