Planverity exposes the OpenAI chat-completions shape, so integration is a base-URL change rather than a rewrite.
The official OpenAI SDKs, LangChain, LlamaIndex, Vercel AI SDK and anything else that accepts a custom base URL work unmodified — including streaming and tool calls. There is no Planverity SDK to adopt, deliberately: a client library is another thing to version, and the value here is that you do not have to change your code.
Assistants that let you configure an OpenAI-compatible endpoint can route through Planverity, which puts policy and budget controls around developer tooling that is otherwise ungoverned.
Planverity speaks MCP Streamable HTTP and can discover a server’s catalogue directly. Discovery imports capability, never authority: tools arrive unclassified and are exposed to nothing until an administrator classifies them, because a server that could assert its own risk class would hand that decision to the least trustworthy party.