Glossary
Key terms and concepts used throughout Futurity and this documentation.
A specialized AI assistant configured for specific tasks. Agents have custom instructions and focused capabilities. See Creating Agents.
API (Application Programming Interface)
Section titled “API (Application Programming Interface)”A way for software to communicate with Futurity programmatically. See API Overview.
Artifact
Section titled “Artifact”A document, report, or other content created by Corint. Artifacts can be saved to Vault, downloaded, or refined through conversation.
Authentication
Section titled “Authentication”The process of verifying identity when accessing Futurity. See Authentication.
A conversation thread with Corint. Each chat maintains its own context and history.
Corint
Section titled “Corint”Futurity’s AI-powered assistant. Short for “Core Intelligence.” Corint can execute workflows, create documents, and interact with tools.
Dashboard
Section titled “Dashboard”A customizable page with widgets displaying data and metrics. See Creating Dashboards.
Folder
Section titled “Folder”A container for organizing files in Vault. Folders can be nested and shared.
Integration
Section titled “Integration”A connection between Futurity and an external service. See Integrations Overview.
MCP (Model Context Protocol)
Section titled “MCP (Model Context Protocol)”A protocol for building AI tool integrations. Used to connect custom services to Corint. See Custom MCP Servers.
Middleware
Section titled “Middleware”Code that runs between receiving a request and processing it. Used in MCP servers for authentication, logging, etc.
A single step in a workflow. Nodes can be triggers, actions, or control flow elements.
A standard protocol for secure authorization. Used when connecting integrations that require your consent.
Organization
Section titled “Organization”A workspace containing members, content, and settings. You belong to an organization and share resources with your team.
Permission
Section titled “Permission”A specific action you’re allowed to perform, like “create workflows” or “manage users.”
Prompt
Section titled “Prompt”The text input given to Corint to describe what you want it to do.
RBAC (Role-Based Access Control)
Section titled “RBAC (Role-Based Access Control)”A system where permissions are assigned to roles, and roles are assigned to you. See Roles & Permissions.
Resource
Section titled “Resource”In MCP, a source of data that tools can access. Resources provide information to AI assistants.
A named set of permissions assigned to you. Examples: Admin, Member, Viewer.
Session
Section titled “Session”A period of authenticated interaction with Futurity. Sessions expire after inactivity.
SSO (Single Sign-On)
Section titled “SSO (Single Sign-On)”A system that lets you log in once and access multiple applications. Enterprise plans support SSO.
A credential used for API authentication. Access tokens are short-lived; refresh tokens can get new access tokens.
A capability Corint can use, like searching the web, reading files, or calling external APIs.
Trigger
Section titled “Trigger”What starts a workflow. Can be manual (button click), scheduled (cron), or event-based (webhook).
Futurity’s file storage system. Securely store and organize documents that Corint can access. See Vault Overview.
Webhook
Section titled “Webhook”An HTTP endpoint that receives data when events occur. Used to trigger workflows from external systems.
Widget
Section titled “Widget”A visual component on a dashboard displaying data, like charts, metrics, or tables.
Workflow
Section titled “Workflow”An automated sequence of steps that execute when triggered. See Workflows Overview.
A TypeScript-first schema validation library used in MCP servers for input validation.