@volter/twin-groq
v1.0.0
Published
Groq Protocol 3 API twin: every spec operation answers the vendor-shaped gap; no scanned application calls Groq.
Readme
@volter/twin-groq
Protocol 3 twin of the GroqCloud API. Nothing is served: neither demand record names Groq among the 18 scanned applications, and no platform or other-pack runtime caller adds an operation. Every spec operation is unmodeled. There are no handlers, resources, credential doors, model scenarios or refresh. The kernel retains its standard discovery and World doors.
Unserved operations and unknown paths answer the documented 404 not-found
class in Groq's JSON error envelope, with invalid_request_error and
The requested resource could not be found. The error page does not fix a
distinct literal URL-refusal body. Bearer authentication is declared from the
vendored spec and Groq's documented 401 class.
The life is empty. Published spec examples are unchanged and counted as
examples of unserved operations. spec/SOURCE.md records the unchanged
upstream document, its provenance, version and hashes.
