@volter/twin-perplexity
v1.0.0
Published
Perplexity Protocol 3 API twin: every spec operation answers the vendor-shaped gap; no scanned application calls Perplexity.
Readme
@volter/twin-perplexity
Protocol 3 twin of the Perplexity AI API. Nothing is served: neither demand record names Perplexity among the 18 scanned applications, and no platform or other-pack runtime caller adds an operation. Every spec operation is unmodeled, including the documented legacy chat-path correction. 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 unknown-resource
404 class in the vendor's JSON error.message envelope. The documentation
does not fix literal URL-refusal text, type or code; the gap says Not found
without inventing a code. Bearer authentication and the 401 class remain
declared from the vendor's documentation.
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 correction, provenance, version and hashes.
