From f7cfe9053934834960feddd092a7246e51b6beb3 Mon Sep 17 00:00:00 2001 From: Boyd Cohen Date: Sun, 9 Aug 2026 00:13:07 -0600 Subject: [PATCH] The deprecated SDK is still the spine of the integration guide, and a fourth offline variant MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two concepts, swept across the site rather than fixed per page. CONCEPT 1: the site instructs installation of a registry-deprecated package. Verified at the registries, not from our own copy: npm @observer-protocol/sdk carries a deprecation notice on the package itself ("Deprecated and unmaintained (last release 2026-04)"), and PyPI observer-protocol's newest release is 0.2.0, uploaded 2026-04-30. Four pages disclose this (sdk.html, quickstart.html, quickstart-tether.html, quickstart-ows.html). Four instruct it with no notice: - institutional/index.html listed "TypeScript + Python SDKs (npm + PyPI)" under ALREADY LIVE, in a capability inventory written for institutional counterparties. - docs.html's Python SDK card said "Full Python SDK" with no notice. I read this page end to end earlier today and missed it: it is the card ADJACENT to the one I edited. Editing a card is not reading its neighbour. - integrate/index.html is built on it end to end — Steps 1, 2, 3 and the closing CTA — under the headings "Integration time: under 1 hour" and "Ship chargeback prevention today". - ows/index.html:303 is the same, and is NOT fixed here: I have not read that page end to end and will not edit a page I have not covered. integrate/ gets a disclosure rather than a rewrite because there is no replacement package for its register/attest flows — policy-engine is verification-only. Saying so is more useful than pretending a swap exists. CONCEPT 2: a fourth vocabulary for the offline claim. "No runtime dependency on OP" — not "us", not "Observer". integrate/index.html asserted it twice while its own four-line example calls resolve_did() against the issuer DID, which for did:web:observerprotocol.org is a fetch from us. Adding the pattern immediately found TWO more instances, one of them on line 77 of the page I had just read end to end. The check caught what reading did not. blog/op-crossrail:84 was the second, and it is CORRECT as written — its subject is the conversion rate being attested in-credential rather than fetched from an oracle, not verification's dependence on us. Tagged for enumeration, wording untouched. A human scopes per instance; the enumeration only has to know. Base case re-run: untagging integrate:181 fails the check, restoring it passes. --- blog/op-crossrail/index.html | 2 +- docs.html | 4 ++-- institutional/index.html | 5 ++++- integrate/index.html | 15 ++++++++++++--- scripts/shared-copy.json | 7 +++++-- 5 files changed, 24 insertions(+), 9 deletions(-) diff --git a/blog/op-crossrail/index.html b/blog/op-crossrail/index.html index 51b37c6..dd99279 100644 --- a/blog/op-crossrail/index.html +++ b/blog/op-crossrail/index.html @@ -81,7 +81,7 @@

One credential, three rails, and a payment that never existed

OP Crossrail is a buyer-side enforcement layer for agent payments: one signed, portable mandate, enforced natively at each rail's own boundary, before the payment exists.

-

Here is the launch demo, committed as a transcript in the repo. A principal signs one delegation: $5.00 per rolling 24 hours, across every rail the agent operates on. Conversion rates are attested inside the credential itself, no oracle, no runtime dependency on us. Then the agent goes shopping.

+

Here is the launch demo, committed as a transcript in the repo. A principal signs one delegation: $5.00 per rolling 24 hours, across every rail the agent operates on. Conversion rates are attested inside the credential itself, no oracle, no runtime dependency on us. Then the agent goes shopping.

It buys an API call from a seller running Cloudflare's x402-proxy-template, unmodified, exactly as Cloudflare ships it: 402, sign, pay, 200. It runs a 5,940-sat L402 invoice through the engine's pre-payment hook, called in-process on a synthetic invoice: no LND node, and the engine ships no payment path. It moves 2 USDT on TRON through the policy engine running on the WDK's policy hook (Tether's PR #55). Two more x402 calls, and the budget sits at exactly $5.00, spent to the cent across three rails under one credential.

diff --git a/docs.html b/docs.html index 80db500..84328c1 100644 --- a/docs.html +++ b/docs.html @@ -225,10 +225,10 @@

Choose your path.

🐍
-
PIP INSTALL · v0.2.0
+
DEPRECATED · v0.2.0, April 2026
Python SDK
pip install observer-protocol
-
Full Python SDK: agent identity, delegation, x402 verification, magic link authorization, chargeback prevention, ERC-8004 integration. Type-hinted throughout.
+
Agent identity, delegation, x402 verification, magic link authorization, chargeback prevention, ERC-8004 integration. Deprecated and unmaintained since April 2026, and marked so on the registry. It still installs and anything pinned to it keeps working, but do not start here — see the SDK page for what replaces which part.
🏗️
diff --git a/institutional/index.html b/institutional/index.html index c923b9d..4912f62 100644 --- a/institutional/index.html +++ b/institutional/index.html @@ -310,7 +310,10 @@

ALREADY LIVE

  • AIP refusal and remediation grammar
  • Delegation scope enforced before signing
  • x402, Lightning, TRON settlement
    • -
  • TypeScript + Python SDKs (npm + PyPI)
    • +
  • @observer-protocol/policy-engine and the per-rail adapters on npm. The + older @observer-protocol/sdk and PyPI observer-protocol packages + are deprecated on the registry and unmaintained since April 2026 — they still install, + but do not start an integration on them.
    • diff --git a/integrate/index.html b/integrate/index.html index 8e33314..cfba537 100644 --- a/integrate/index.html +++ b/integrate/index.html @@ -74,7 +74,7 @@

    Add Chargeback Prevention to Your AI InfrastructureWhat you get

    -

    Observer Protocol adds one artifact to every agent transaction on your infrastructure: a cryptographically signed authorization proof that shows the purchase was within a valid delegation's scope. The authorization proof is independently verifiable by any third party. No runtime dependency on OP or your backend.

    +

    Observer Protocol adds one artifact to every agent transaction on your infrastructure: a cryptographically signed authorization proof that shows the purchase was within a valid delegation's scope. The authorization proof is independently verifiable by any third party: no API key, and no Observer Protocol API in the path. Verifying it fetches the issuer's DID document over ordinary HTTPS, or nothing at all if you supply that document yourself.