Repository navigation
blog: python SDK announcement blog - #2987
Conversation
Signed-off-by: Ignasi Barrera <ignasi@tetrate.io>
✅ Deploy Preview for theagentrouter ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| image: /img/og/blog/python-sdk.png | ||
| description: >- | ||
| The Agent Router Python SDK keeps LiteLLM's API and sends every call through Agent Router, the | ||
| open-source AI gateway built on Envoy. Fallbacks, retries, rate limits and provider keys move out |
There was a problem hiding this comment.
| open-source AI gateway built on Envoy. Fallbacks, retries, rate limits and provider keys move out | |
| open-source AI gateway built on Envoy. Fallbacks, retries, request limits and provider keys move out |
Same wording in below line 47
| The exported configuration can be used to run a gateway with the | ||
| [Agent Router standalone mode](/docs/cli/aigwrun). |
There was a problem hiding this comment.
| The exported configuration can be used to run a gateway with the | |
| [Agent Router standalone mode](/docs/cli/aigwrun). | |
| The exported configuration can be used to run a gateway with the | |
| [Agent Router standalone mode](/docs/cli/aigwrun). It checks one shared client key: pick any value, | |
| set it as `AGENTROUTER_API_KEY` on the server, and give your clients the same value. |
Without this, the exported gateway refuses every request. export_config() turns on a client-key check by default, and the server reads the key from its own AGENTROUTER_API_KEY. The post shows the client side (line 175) but never the server side, and the aigw run page doesn't mention it either, so a reader who follows the post gets 403 on every call with no hint why. It's one shared key for everyone, which is fine for a small team.
| - **A much smaller footprint.** `theagentrouter-core` has exactly one runtime dependency: `httpx`. | ||
| There are no provider SDKs, and the model catalog ships with each release instead of being | ||
| downloaded on import. After this year's supply-chain incidents across the Python ecosystem, | ||
| including the compromised LiteLLM releases in March, a small dependency surface and keys that |
There was a problem hiding this comment.
| including the compromised LiteLLM releases in March, a small dependency surface and keys that | |
| including the [compromised LiteLLM releases in March](https://docs.litellm.ai/blog/security-update-march-2026), a small dependency surface and keys that |
|
|
||
| ## What's not there yet | ||
|
|
||
| The SDK is in alpha (`0.1.0a11`), and at the time of writing these are the known limitations: |
There was a problem hiding this comment.
| The SDK is in alpha (`0.1.0a11`), and at the time of writing these are the known limitations: | |
| The SDK is in alpha (`0.1.0a12`), and at the time of writing these are the known limitations: |
Created new version to fix issues
|
Thanks @arifsetiawan! Addressed the comments as part of #2989 |
**Description** Adds the release notes for version 1.2.1 and addresses small comment nitpicks left over from the Python SDK blog post review. **Related Issues/PRs (if applicable)** #2987 **Special notes for reviewers (if applicable)** N/A --------- Signed-off-by: Ignasi Barrera <ignasi@tetrate.io>
Description
Add a blog announcing the Python SDK
Related Issues/PRs (if applicable)
N/A
Special notes for reviewers (if applicable)
N/A