Repository navigation
Conversation
The compat tests go through the SDKs, so they cannot show that the protocol alone is enough. These use a plain HTTP client, real listeners and JSON schemas, with only the chain faked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Routes were listed, but not their order, the payer header, the challenge body or top-up timing, which could only be found in SDK code. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rickstaa
temporarily deployed
to
docker-publish
November 5, 2026 13:29 — with
GitHub Actions
Inactive
rickstaa
temporarily deployed
to
docker-publish
November 5, 2026 13:30 — with
GitHub Actions
Inactive
rickstaa
temporarily deployed
to
docker-publish
November 5, 2026 13:30 — with
GitHub Actions
Inactive
rickstaa
temporarily deployed
to
docker-publish
November 5, 2026 13:31 — with
GitHub Actions
Inactive
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the client contract so integrators can reserve, pay and stream without the SDK, after the HTTP PUT transcoding discussion with Marco and Thulinma. It adds the client flow, proxy and O2R behavior, orchestrator response codes and tested nginx settings to the existing docs, JSON schemas for the session, challenge, signer and error messages, a first set of conformance tests that use a plain HTTP client, and a PR template that asks about protocol changes. Node behavior does not change.
This demo shows the media path on an unmodified orchestrator: ffmpeg PUTs the source and a GET returns the ABR ladder.
Two things to settle in review: the docs now state that session URLs are the only client credential, so should that stay or should they get a token check, and can clients rely on the signer's 10-second first payment, given that the Python SDK's 3-second interval is only its own choice? The 480 refresh path is documented, but only the pinned SDK test covers it.