Protocols and compatibility
The gateway preserves native formats for supported surfaces. Each model needs a mapping to a compatible upstream endpoint; the platform does not add absent model capabilities.
| Surface | Endpoint | Use |
|---|---|---|
| Catalog | GET /v1/models, GET /v1/models/{id} | Public names authorized for the key |
| Chat Completions | POST /v1/chat/completions | JSON/SSE conversations, compatible tools and structured output |
| Messages | POST /v1/messages | Anthropic protocol, compatible tool use and thinking |
| Messages token count | POST /v1/messages/count_tokens | Count sanitized text without inference charges |
| Responses | POST /v1/responses | Answers and supported Netter context continuations |
| Embeddings | POST /v1/embeddings | Single or batched text using named models |
| System One | POST /v1/systemone | Choice, Score and Noul structured decisions |
| Files | /v1/files | Private upload and own-file management |
| Audio | /v1/audio/* | Configured transcription, translation and synthesis |
Names and capabilities
Public names can include namespaces, such as vendor/model. Encode them correctly when used in URL paths. An alias is not the upstream ID: the client sends the alias and the server resolves provider, protocol and actual model.
switchyard routes supported conversational surfaces. Embeddings, audio and token counting use compatible named mappings. Do not use names from another provider's catalog unless Netter publishes them.
Tools and excluded features
Client-executed tools and compatible native formats are supported. Realtime, Batch, fine-tuning and provider-executed cloud tools are outside this gateway version.
If a client enables proprietary features automatically, configure allowed options and test the real workflow before rollout. A working text request does not establish image, tool or signed-reasoning compatibility.
Embeddings and System One
With PII enabled, embeddings require text rather than precomputed token IDs. Pseudonymization uses the tenant namespace; keep indexing and query processing consistent. Changing models may require reindexing.
System One receives state and structured questions under its contract and shares the platform's credit and authorization boundaries. Its mapping is separate from chat routes.
See the OpenAPI contract for schemas and Responses for application state.