RAG (Retrieval-Augmented Generation)
A setup where an AI tool first searches a private knowledge base (your own documents) and uses what it finds to answer. Helps reduce hallucinations and lets the AI use up-to-date internal information.
Example
A future 'Ask the AI Hub' chatbot would use RAG - it would search this site's content first, then answer using approved policy language.
Fine-tuning
Customizing an AI model by training it further on your own specific data. Different from simply 'using' a model - fine-tuning permanently teaches it new patterns. Most internal use cases don't need fine-tuning; clear prompting and RAG usually work just as well.
API
Application Programming Interface - a way for one piece of software to talk to another. AI APIs let developers connect models like Claude or GPT into other apps. If you're not a developer, the practical meaning is just 'how the AI plugs into something else.'
Multimodal AI
An AI tool that can handle multiple kinds of input - not just text, but also images, voice, or video. Claude reading a screenshot of an invoice, or Copilot generating a chart from a description, are multimodal moments.
AI Agent
An AI that can take a goal and execute multi-step tasks on its own - using tools, browsing the web, calling APIs, writing files - instead of just chatting. The difference between Claude answering 'how do I file this?' versus Claude actually filing it.
Example
An AI agent could be told 'pull the last 90 days of lease applications, flag any with credit-score anomalies, and email the underwriting lead.' It would chain those steps without further prompting.
Tool use
An AI's ability to call external software - a calculator, a database query, a web search, a file system - as part of producing its answer. Without tool use, the AI is limited to what's in its head; with tool use, it can reach into the real world.
Example
Claude with computer-use enabled can navigate a browser. ChatGPT with file analysis can read your uploaded spreadsheet. Both are examples of tool use.
Function calling
The technical mechanism that lets an AI request to run a specific function (with specific arguments) in the surrounding software. The AI doesn't run the code itself - it asks the host system to run it, gets back a result, and continues. Foundation of tool use and agents.
MCP (Model Context Protocol)
An open standard from Anthropic for connecting AI assistants to external systems - databases, files, business tools - without one-off integrations for each. Think of it as USB-C for AI: any MCP-compatible client (Claude, Cursor, etc.) can talk to any MCP-compatible server.
Example
If we ever build internal AI tools, MCP servers let us expose Advantage+ data (read-only) to Claude or other clients in a standardized, audited way.
Reasoning model
A newer class of AI model that 'thinks' before answering - it generates a hidden chain of internal reasoning, often weighs alternatives, then produces a more deliberate response. Slower and more expensive per question, but markedly better on math, logic, and multi-step problems.
Example
Claude's 'extended thinking' mode and OpenAI's 'o1' / 'o3' series are reasoning models. For 'summarize this email' you don't need one. For 'is this credit memo consistent with our policy?' you might.
Vector embedding
A way of turning text (or images, or audio) into a list of numbers that captures its meaning - so similar pieces of content end up with similar number-lists. Embeddings are how AI 'finds things that are about the same topic' without keyword matching.
Example
'Customer past-due' and 'Borrower delinquency' don't share keywords but their embeddings sit close together - a semantic search using embeddings would match them.
Semantic search
Searching by meaning rather than by exact keywords. Powered by vector embeddings. A semantic search for 'late payments' would surface documents about 'arrears' and 'delinquency' even if those exact words aren't in your query.
Chain-of-thought
A prompting technique (and now a built-in capability) where the AI is encouraged to show its reasoning step-by-step rather than jumping straight to an answer. Often dramatically improves accuracy on logic, math, and multi-step problems.
Example
Prompting 'think step-by-step before answering' often improves an LLM's output on credit-decision-style problems. Modern reasoning models do this automatically.
Few-shot prompting
Showing the AI 2–5 examples of the input/output pattern you want before asking it to do the real task. Hugely improves consistency for formatted outputs (emails, reports, classifications).
Example
Want consistent customer email tone? Paste 3 previous well-written emails as examples, then ask Claude to write the next one in the same style. That's few-shot.
Zero-shot prompting
Asking the AI to do something with no examples - just a clear description of the task. Works surprisingly well on modern models for many tasks, less reliable for tasks where the exact format matters.
Example
'Classify this email as urgent / normal / spam' with no examples is zero-shot. It works for big categories; for nuanced internal labels, few-shot wins.
Coding assistant
An AI tool aimed at software engineers - code completion, code generation, bug fixing, refactoring. Different categories: in-editor autocomplete (GitHub Copilot), terminal-based agents (Claude Code, Codex CLI), full IDEs designed around AI (Cursor). Each handles data + secrets differently.
Example
Not every Advantage+ employee will use one, but every developer here should know the options + their data-handling profile before pasting an internal config into a coding assistant.
Claude Code
Anthropic's terminal-based coding agent. Runs in a developer's command line, reads and writes files in a project, runs shell commands, and uses tool calling to complete software-engineering tasks end-to-end. Distinct from Claude.ai (the chat UI) - Claude Code is built for codebases, not conversation.
Example
An engineer might tell Claude Code: 'add a CSV export to the reports page.' It reads the codebase, writes new code, runs tests, and proposes a commit - all from the terminal.
Codex (OpenAI)
OpenAI's coding-agent platform. Available as a CLI tool, an IDE extension, and an autonomous web-based agent. Writes, modifies, and runs code from natural-language prompts. Powered by OpenAI's coding-tuned models.
Example
Used to draft PR-sized changes against a repo or to automate routine engineering work - same problem space as Claude Code, different vendor and slightly different ergonomics.
Cursor
A code editor (forked from VS Code) built around an AI that reads your codebase and edits files for you. You describe what you want; Cursor drives the editing across multiple files. Different from autocomplete plugins - in Cursor, the AI is the default way to write code.
Example
Engineers reach for Cursor over VS Code + Copilot when they want the AI to take the lead on multi-file refactors or new features.