Components that talk to language models and vector stores: the provider clients, the chatbot and translator front ends, embeddings, and both sides of the Model Context Protocol. Eight documents in this section, each one available as a web page and as an A4 PDF.
Read links open the web version. PDF links open the same content laid out for A4, with a cover page and fixed page breaks.
| Anthropic ComponentHigh-level Anthropic Claude API client — Messages, streaming, tool use, vision and structured-output JSON schema. | Read PDF | |
| AI ChatBotHigh-level ChatBot component — wraps OpenAI, Anthropic, Gemini or local LLMs in a one-line conversational front-end. | Read PDF | |
| AI EmbeddingsEmbeddings generator and consumer for vector search — text-embedding-ada-002, text-embedding-3-large and compatible providers. | Read PDF | |
| MCP ClientModel Context Protocol (MCP) client — connect Delphi apps to any MCP server (resources, tools, prompts). | Read PDF | |
| MCP ServerModel Context Protocol (MCP) server — expose your Delphi resources, tools and prompts to any MCP client (Claude, ChatGPT, IDEs). | Read PDF | |
| OpenAI ComponentHigh-level OpenAI HTTP API client — chat completions, responses, embeddings, images, audio, files, fine-tuning, batches and assistants. | Read PDF | |
| Pinecone Vector DatabasePinecone client — upsert, query and delete vectors in a managed Pinecone serverless or pod-based index from Delphi. | Read PDF | |
| AI TranslatorHigh-level translator component — translate text between languages with OpenAI, Anthropic or Gemini providers. | Read PDF |
Eighty-six documents in all. The full index lists every one of them on a single page.
26 documents
Ready-made clients for third-party services. Mostly WebSocket market data and trading feeds, plus the messaging platforms and the two SignalR dialects.
12 documents
The WebSocket client and server themselves, in Delphi and in .NET, together with the resilience components that guard them and the scaling components that put several servers behind one address.
3 documents
Bridges that host an existing WebBroker or DataSnap application on an sgcWebSockets server, so one executable answers REST, WebSocket and HTTP/2 on the same port.
14 documents
The HTTP/2 client and server, gRPC, the OAuth2 and JWT components on both sides, WebAuthn, and the push and queue services reached over plain HTTP.
2 documents
MQTT clients preconfigured for the two managed IoT brokers, with the authentication each one insists on already wired up.
8 documents
The NAT traversal stack: STUN, TURN and ICE as client and server, the UDP transports underneath them, and the Delphi side of RTCPeerConnection.
12 documents
WebSocket subprotocols and message brokers: MQTT, both AMQP versions, STOMP against two brokers, WAMP, WebRTC signalling, and the five custom sgc subprotocols.
1 document
Server-side components that answer a browser or platform specification rather than call somebody else’s service.