Skip to content

TapeAPI 1.1.0

Choose a tag to compare

@BruceLanLan BruceLanLan released this 29 Sep 16:54
· 15 commits to main since this release

中文

TapeAPI 1.1.0:在 1.0 基础上只做新增,按 1.0 文档写的代码无需任何修改。

新增

  • LiteLLM Proxy 一键签名(examples/litellm-sidecar/):一个 docker-compose 包,把签名旁路放在 LiteLLM Proxy 前面。用 LiteLLM 的 AI 中转站不用改代码,每个回答都会带上可核验的回执。旁路由你自己运行,TapeAPI 不托管。

修复

  • 中继:一帧的 Durable Object 写入落地之前,任何人都读不到它;写入失败时撤回这一帧,客户端的重试就是唯一的一份,不会再出现重复帧。
  • RPC:批量请求遇到连接重置这类“没有回答”的失败,只暂停批量 5 分钟或 20 次调用。以前是在客户端整个生命周期里都不再批量。
  • AI 回执:正确去掉 LiteLLM 以空 delta 形式发出的用量块。客户端没有要求用量时,就不会多收到一块。
  • 监控:修复中继异步投递检查。
  • 文档与网站的若干修正。

安装

npm install https://github.com/BruceLanLan/tapeapi/releases/download/v1.1.0/tapeapi-sdk-1.1.0.tgz

单独安装 server 时,先装同一版本的 SDK tgz。完整变更见 CHANGELOG。本项目未经第三方审计。

感谢 @Theairresearch 提出最初的想法。


English

TapeAPI 1.1.0 is additive over 1.0: code written against the 1.0 docs keeps working unchanged.

Added

  • One-command signing for LiteLLM Proxy (examples/litellm-sidecar/): a docker-compose package that puts the signing sidecar in front of LiteLLM Proxy. An AI relay running LiteLLM gets a verifiable receipt on every answer without code changes. You run the sidecar; TapeAPI does not host it.

Fixed

  • Relay: a frame is readable only after its Durable Object write lands. If the write fails, the frame is taken back out, so the client's retry is the only copy and no duplicate frames appear.
  • RPC: a batch failure that got no answer (such as a connection reset) now pauses batching to that node for 5 minutes or 20 calls, not for the client's lifetime.
  • AI receipts: LiteLLM's usage chunk with an empty delta is stripped correctly, so a client that did not ask for usage does not receive an extra chunk.
  • Monitor: fixed the relay async-delivery check.
  • Various fixes to the docs and website.

Install

npm install https://github.com/BruceLanLan/tapeapi/releases/download/v1.1.0/tapeapi-sdk-1.1.0.tgz

To install the server package on its own, install the SDK tgz from the same release first. The full list of changes is in the CHANGELOG. Nothing here has had a third-party audit.

Thanks to @Theairresearch for the original idea.