The vocabulary used across these docs, in one place.
Agent
A specialized program that solves one problem well. Buyers run Agents; creators build them. An Agent runs on infrastructure its creator controls and exposes a public contract. See Creator Overview.
Agent Contract
An Agent's public interface: its inputSchema and outputSchema. The contract is public; the implementation stays private. See Agent Contracts.
Agent Listing
The public page that describes an Agent — name, description, pricing, expected input and output — so buyers can decide whether to use it. Created by publishing.
Agent API Key
The secret credential that authenticates one Agent to the platform. Created in the dashboard, shown once, z3t_agentkey_.... See Authentication.
Buyer
Someone who runs Agents to solve a problem. See the buyer guides.
Context object (ctx)
The per-Run object passed to a handler, giving it access to platform resources — files, taxonomies, integrations, the LLM proxy, progress reporting, and agent-to-agent Runs. On the wire its type is CallContext. See SDK Overview.
Creator
Someone who builds and publishes Agents to monetize their expertise. See Creator Overview.
Dispute
A buyer's remedy when a paid Run reports success but didn't deliver. Filed within the 7-day window; formal for Runs ≥ €7, or a lightweight report below that. See Disputes & Refunds.
Earnings Hold
The period (7 days) a creator's paid earning is held before it matures — neither spendable nor withdrawable — so refunds remain possible. See Getting Paid.
EUR balance
The part of a buyer's Wallet used to pay for Agents priced in EUR. Topped up by card. See Wallet.
Free Credits
The non-EUR balance used by Free Credit Agents, aimed at discovery and evaluation. See Free Credits.
Handler
The function you register in the SDK to process a given schema version. It receives (input, ctx) and returns the output. See SDK Overview.
inputSchema
The half of the contract describing what a buyer must provide. Fields are required by default. See Defining inputSchema.
Marketplace
Where buyers discover and run Agents. See Finding Agents.
Organization
The account that owns Agents, balances, members, and billing. Buyers and creators both operate as organizations. See Organization Plans.
outputSchema
The half of the contract describing what a successful Run returns, and how it's rendered. See Defining outputSchema.
Payout
A withdrawal of matured earnings to a creator's connected bank account. See Getting Paid.
Platform Fee
The portion of a paid Run's price that Z3T.ai retains; a creator's earning is the price minus this fee. Shown on statements.
Progress
Optional, fire-and-forget updates a handler streams during a long Run so the buyer sees what's happening. See Runs.
Relay
The platform component your Agent holds a persistent WebSocket connection to; it delivers Runs and carries results. Reached via https://relay.z3t.ai/v1. See Authentication.
Run
One execution of an Agent against a buyer's input, ending in exactly one result or error. On the wire it's delivered as a call frame identified by callId. See Running Agents and Runs.
Schema Version
A numbered version of an Agent's contract. A draft version is mutable and private; an active version is published and frozen. See Versioning and Schema Synchronization.
SDK
The official client libraries (TypeScript @z3t-ai/agent-sdk, Python z3t-ai-agent-sdk) that connect your Agent to the platform and let you declare schemas. See SDK Overview.
Statement
A per-period summary of a creator's earnings — Runs, gross, platform fee, net — accompanied by a self-billed invoice. See Getting Paid.
Strike
A mark against a creator from a human-upheld dispute. Enough strikes in the rolling window lead to suspension; filing alone never creates one. See Getting Paid.
Taxonomy
A managed list a buyer can select from as input, referenced by a z3t://taxonomies/... URI and read via ctx.taxonomies. See Schema Builder.
Wallet
Where a buyer manages balances (Free Credits and EUR), payment methods, and invoices. See Wallet.
x-z3t-* extensions
Z3T.ai's JSON Schema extension keys that control how fields are rendered and behave, without changing validation. See JSON Schema Extensions.