SDKs and HTTP · Shell
curl and plain HTTP
How do I use curl and plain HTTP with Onrup?
Post JSON to your deployment’s chat completions path with a bearer token. There is no SDK requirement anywhere in the product — every capability is reachable from a plain HTTP request.
The lowest common denominator: an HTTP request with a JSON body, from a shell or from any language.
Minimal working example
curl https://serve.onrup.com/<tenant>/<deployment>/v1/chat/completions \
-H "Authorization: Bearer $ONRUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "default",
"messages": [{"role": "user", "content": "Classify this message."}],
"temperature": 0
}'The thing that catches people out
Set temperature explicitly for anything structured. The default is not zero, and a classification endpoint left at the default will occasionally produce creative answers to a question with one right answer.
Worth knowing
- Add "stream": true and the response becomes a server-sent event stream.
- The control-plane API is a separate host from the serving endpoint, and uses the same bearer token.
- Errors return a stable envelope with a namespaced code, so a client can branch on the code rather than parse a message.
Other sdks and http
Start with the free tier
A magic link creates your account, your tenant and your first API key. No card until you ask for compute.