Skip to main content

Glossary of Terms​

A​

API-first: An approach to software development that prioritizes the design and implementation of APIs before building the underlying application logic.​

Automated Orchestration: The automated arrangement, coordination, and management of complex computer systems, middleware, and services.​

Go to top

C​

Context: The information surrounding a user interaction, including user preferences, history, and environmental factors.​

Contract: A formal agreement that defines the expectations and responsibilities of different parties in a system, often used to ensure compliance and interoperability.​

Go to top

D​

Developer Experience (DevEx): Empowers developers to build better software, faster, minimizing technical debt proactively.​

Developer Happiness: We take DevEx seriously. It's about the overall satisfaction and productivity of developers, often enhanced by tools and practices that streamline workflows and reduce friction. HAPI MCP is designed to boost developer happiness by providing a structured, API-first approach.​

Go to top

G​

gRPC: A high-performance, open-source universal RPC framework that uses HTTP/2 for transport and Protocol Buffers (Protobuf) as the interface definition language.​

Go to top

H​

HAPI - Headless API Stack: A software architecture that separates the business logic in backend services from the client layer, enabling greater flexibility and scalability.​

HAPI Control Plane (HAPI CP): Provides a centralized management interface for MCP servers, enabling the dynamic management of tools and routing rules.​

HAPI MCP: The Headless API Stack for the Model Context Protocol (MCP), which simplifies AI integration by leveraging API specifications to generate MCP tools dynamically.​

HAPI Server: stands for Headless API, is a server that reads the API specs and dynamically serves an MCP contract, making your backend instantly usable by AI agents without rewriting code. Watch the demos and examples to see it in action.​

Go to top

I​

IDL (Interface Definition Language): A specification language used to define APIs and data structures in a way that is independent of programming languages.​

Go to top

L​

LLM (Large Language Model): A type of AI model trained on vast amounts of text data to understand and generate human-like text.​

Go to top

M​

MCP (Model Context Protocol): "A standardized way to connect AI models to different data sources and tools" (as per official specs). We see this as a contract that defines how interfaces should behave in AI-native systems, enabling more effective interactions between users and models.​

Memory: The ability of a system to retain information about past interactions, user preferences, and other relevant data to improve future interactions.​

Go to top

O​

OpenAPI: A specification for building APIs, allowing developers to define endpoints, request/response formats, and authentication methods.​

Orchestration: The automated arrangement, coordination, and management of complex computer systems, middleware, and services.​

Go to top

R​

RESTful: An architectural style for designing networked applications, relying on stateless communication and standard HTTP methods.​

Go to top

S​

Session: A temporary, unique interaction between a user and a system, often tied to a specific task or conversation.​

Swagger: A set of tools for designing, building, and documenting RESTful APIs, now part of the OpenAPI Initiative.​

Go to top

T​

Technical Debt: The implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.​

Go to top