Add systemone API for SI - #1236
Merged
SSharma-10 merged 2 commits intoSep 28, 2026
Merged
Conversation
SSharma-10
reviewed
Sep 28, 2026
SSharma-10
reviewed
Sep 28, 2026
SSharma-10
reviewed
Sep 28, 2026
This was referenced Sep 28, 2026
[bot] Add systemone API for SI: Re-Generated From digitalocean/openapi@5475e14
digitalocean/pydo#737
Open
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.
Summary
POST /v1/systemone, a serverless, pass-through evaluation endpoint for TypeSafe AI's Jev model, under the existing Serverless Inference taginference-proxy's live contract (internal/api/typesafe/openapi.yaml):state+model+ aquestionsmap ofnoul/choice/scoretypes in,answers+usageoutValidation
$refin the new files resolves/v1/systemoneis already present in production's edge/gateway allowlist, so this isn't documenting an unroutable endpointinference-proxy's current implementation that the request and response schemas match what the service actually accepts and returns