Core Concepts and Terminology

Definitions for the terms used throughout Tangle’s docs.

• Blueprint Agent: An in-browser IDE where you describe a project and an AI agent builds it with you.
• Sandbox: An isolated computer for agent work.
• Runtime: The session and execution controls for agents running in sandboxes.
• Router: The model request path for supported providers and explicitly selected operator routes.
• Integrations: Connections between agents and supported tools, data, or external events.
• Intelligence: Observability for inspecting traces and comparing agent runs.
• Agent: An AI worker running inside a sandbox.
• Agent profile: A configuration that defines models, tools, budgets, and policies for an agent.
• Evaluation: A structured assessment of task results, cost, or policy compliance, built into layers and products.
• Simulation run: A multi-variant evaluation of an agent or workflow across many tasks.
• Blueprint: A reusable service template that defines interfaces, execution requirements, and expected outputs.
• Service instance: A live deployment of a Blueprint, launched on demand and run by operators.
• Job: A unit of work submitted to a service instance.
• Operator: A node that provides compute and runs service instances.
• Economic security provider: A participant who backs operators with assets and shares in protocol economics.
• Tangle protocol: The coordination layer that schedules work, routes payments, and enforces incentives.
• Payments: The flow of value tied to usage, distributed to operators and developers.
• Webhook gateway: An HTTP ingress path that converts external events into job executions.
• x402 gateway: An HTTP payment and execution path that verifies settlement via x402 and then triggers a job.