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.
- {cortexhub-1.0.0 → cortexhub-1.0.2}/PKG-INFO +10 -19
- {cortexhub-1.0.0 → cortexhub-1.0.2}/README.md +9 -18
- {cortexhub-1.0.0 → cortexhub-1.0.2}/pyproject.toml +1 -1
- {cortexhub-1.0.0 → cortexhub-1.0.2}/src/cortexhub/__init__.py +1 -2
- {cortexhub-1.0.0 → cortexhub-1.0.2}/.gitignore +0 -0
- {cortexhub-1.0.0 → cortexhub-1.0.2}/LICENSE +0 -0
- {cortexhub-1.0.0 → cortexhub-1.0.2}/src/cortexhub/client.py +0 -0
- {cortexhub-1.0.0 → cortexhub-1.0.2}/src/cortexhub/errors.py +0 -0
- {cortexhub-1.0.0 → cortexhub-1.0.2}/src/cortexhub/session.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: cortexhub
|
|
3
|
-
Version: 1.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
|
|
165
|
+
## What runs where
|
|
167
166
|
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
-
|
|
173
|
-
-
|
|
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
|
-
|
|
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
|
|
142
|
+
## What runs where
|
|
144
143
|
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
-
|
|
150
|
-
-
|
|
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
|
-
|
|
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
|
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|