TelemHQ Glossary
Plain-language definitions for the AI, cron, payload, token, API, and developer workflow terms used across TelemHQ. Inline definitions throughout the app link back here for source context.
Search all glossary terms.
Also seen as: artificial intelligence
Software that performs tasks normally associated with human judgment, language understanding, or pattern matching. In TelemHQ, AI usually means jobs that call a model, agent, or coding tool.
Source: Google Cloud Generative AI glossaryAlso seen as: LLMs, large language model, large language models
A large language model is a text-focused AI model trained on large amounts of data to understand, generate, summarize, translate, or reason over language.
Source: Google Cloud Generative AI glossaryAlso seen as: models
The AI system that processes input and returns output. For monitoring, the model name helps explain which tool or provider produced a run and how its token usage should be priced.
Source: Anthropic model docsAn AI provider whose APIs and models are commonly used for text generation, coding, reasoning, embeddings, and agent workflows.
Source: OpenAI token guideThe company behind Claude, a family of AI models used for chat, coding, analysis, and tool-using workflows.
Source: Anthropic model docsAnthropic’s family of AI models. TelemHQ can track Claude jobs by recording model names, token usage, latency, cost, and run metadata.
Source: Anthropic model docsA Claude-based coding tool. In TelemHQ, its usage can be tracked like other coding assistants when a run sends structured metadata after work completes.
Source: Anthropic model docsAn AI coding assistant workflow. TelemHQ can record Codex usage by branch, task, model, token counts, cost, and run result.
Source: OpenAI token guideGoogle’s family of multimodal AI models. TelemHQ treats Gemini runs like other model runs when they send comparable payload fields.
Source: Google Cloud LLM overviewA family of AI models often used through hosted APIs or local inference. TelemHQ can track Llama jobs when the run reports model and usage metadata.
Source: Meta Llama docsA family of open foundation models from Alibaba Cloud’s Qwen team, used for language, coding, and multimodal AI workflows.
Source: Qwen model siteAn AI model provider with an API that supports OpenAI-compatible and Anthropic-compatible usage patterns for model calls.
Source: DeepSeek API docsAlso seen as: Moonshot
An AI assistant and model platform from Moonshot AI, with model APIs that can be monitored when jobs report model, token, and run metadata.
Source: Kimi API PlatformAlso seen as: Z.ai, Zhipu
A family of large models from Z.ai, formerly known internationally through Zhipu AI, used for coding, agent, and general AI workflows.
Source: Z.aiAlso seen as: retrieval-augmented generation, RAG sync, RAG syncs
Retrieval-augmented generation improves model output by retrieving relevant information from a knowledge source and grounding the response in that context.
Source: Google Cloud Generative AI glossaryAlso seen as: evals, evaluation, evaluations, eval run, eval runs
A test or scoring run used to judge whether an AI system behaved well enough. TelemHQ can track eval score, pass rate, failures, and regressions.
Source: Google Cloud Generative AI glossaryAlso seen as: agents, AI agent, AI agents
An AI application that uses a model, instructions, state, and tools to work toward a goal. Agents are useful to monitor because they can run for a while and make multiple tool calls.
Source: Google Cloud Generative AI glossaryAlso seen as: workers
A background process that performs work outside the main request path, such as syncing data, generating reports, or running AI tasks.
Source: GitHub Actions CI docsAlso seen as: pipelines
A sequence of automated steps that moves data or work from one stage to another. AI pipelines often include retrieval, model calls, post-processing, and reporting.
Source: GitHub Actions CI docsAlso seen as: batches, batch job, batch jobs
A group of records or tasks processed together. Batch jobs are often monitored by counting processed items, failed items, duration, and cost.
Source: Anthropic API overviewA Unix-style scheduler for recurring commands. TelemHQ uses cron schedules to know when a tracker should receive its next ping.
Source: AWS EventBridge Scheduler docsAlso seen as: cron expressions
A compact schedule string made of time fields, such as minute, hour, day, month, and weekday. It describes when a recurring job should run.
Source: AWS EventBridge Scheduler docsAlso seen as: cron jobs
A scheduled task that runs automatically, often on a server. TelemHQ tracks cron jobs by receiving a ping after each run.
Source: AWS EventBridge Scheduler docsAlso seen as: scheduled jobs
A background task expected to run at predictable times. If it misses its expected window, TelemHQ can mark the tracker as failing.
Source: AWS EventBridge Scheduler docsAlso seen as: ad hoc jobs, ad hoc
A task that runs whenever needed instead of on a fixed schedule. TelemHQ records each run but does not fail the tracker just because no scheduled ping arrived.
Source: AWS EventBridge Scheduler docsAlso seen as: trackers
A monitored job, AI pipeline, worker, script, or automation in TelemHQ. Each tracker has its own ping URL and run history.
Source: TelemHQ docsAlso seen as: pings
A request sent to TelemHQ after a job runs. A ping can be a simple heartbeat or include JSON payload data about what happened.
Source: TelemHQ docsAlso seen as: heartbeats, heartbeat monitoring
A lightweight signal that proves a job checked in. TelemHQ extends heartbeats with payload data so the run can explain what happened.
Source: TelemHQ docsAlso seen as: grace periods
Extra time after a job is expected to run before TelemHQ marks it late or failing. It keeps normal scheduling jitter from creating false alarms.
Source: TelemHQ docsAlso seen as: status pages
A public page showing the health of selected trackers. Teams can use it to share whether monitored jobs are currently operational.
Source: TelemHQ docsAlso seen as: history
The stored record of previous job runs. TelemHQ uses run history to show payloads, failures, timing, token totals, and trends over time.
Source: TelemHQ docsAlso seen as: assertions, assertion rule, assertion rules
A rule that checks payload data after a run. Assertions can flag a job as unhealthy even if the process technically completed.
Source: TelemHQ docsAlso seen as: digests
A summary message that groups recent tracker activity, such as daily or weekly run totals, failures, and payload metrics.
Source: TelemHQ docsAlso seen as: payloads
The structured data sent with a request. In TelemHQ, payloads should contain safe operational metadata, not prompts, completions, secrets, customer data, or private paths.
Source: MDN API glossaryAlso seen as: JavaScript Object Notation
A common text format for structured data. TelemHQ accepts JSON payloads so jobs can report fields like status, tokens, duration, and cost.
Source: MDN glossaryData about a run rather than the private content of the run itself, such as model name, duration, branch, item counts, or token totals.
Source: MDN API glossaryAlso seen as: APIs, application programming interface
A software interface that lets programs interact through defined rules, URLs, methods, and data formats.
Source: MDN API glossaryThe web protocol used for requests and responses. TelemHQ ping URLs receive HTTP requests from jobs after they run.
Source: MDN glossaryAn HTTP method usually used to retrieve data. In TelemHQ docs, GET requests are used for pages and read-style endpoints.
Source: MDN HTTP docsAn HTTP method used to send data to a server. TelemHQ pings use POST when a job reports a run and optional payload.
Source: MDN HTTP docsAlso seen as: endpoints
A specific URL where an API receives requests. A TelemHQ tracking URL is the endpoint your job calls after it runs.
Source: MDN API glossaryAlso seen as: webhooks
An HTTP callback sent when an event happens. TelemHQ can use outgoing webhooks to notify another system about tracker events.
Source: MDN API glossaryA command-line tool commonly used to make HTTP requests. TelemHQ docs use curl examples to show how to send pings.
Source: curl projectAlso seen as: SDKs, software development kit
A software development kit is a package of tools or libraries for building with a platform or API.
Source: MDN API glossaryAlso seen as: token, token usage
The pieces of text an AI model processes. Token counts are often used to measure usage and calculate model cost.
Source: OpenAI token guideAlso seen as: prompt tokens
Tokens sent into a model as input. Tracking them helps teams understand how much context each run consumed.
Source: OpenAI token guideAlso seen as: completion tokens
Tokens produced by a model as output. They are part of total usage and are often priced separately from input tokens.
Source: OpenAI token guideInput tokens that a provider can reuse from previous context. Cached tokens may be reported separately because they can affect cost and performance.
Source: OpenAI token guideTokens used internally by some reasoning models while working toward an answer. They can count toward usage even when they are not shown as final output.
Source: OpenAI token guideHow long a request or job takes to respond. AI job latency helps teams spot slow model calls, overloaded workers, or expensive retries.
Source: MDN glossaryAlso seen as: spend
The money associated with a run, often estimated from token usage and provider pricing. TelemHQ can store cost fields when your job sends them.
Source: OpenAI token guideA distributed version control system used to track code changes. TelemHQ can store Git metadata like branch or issue identifiers with a run.
Source: Git glossaryAlso seen as: branches
A line of development in Git. Tracking branch names helps connect AI coding usage or job cost to a specific task or change.
Source: Git glossaryA code hosting and collaboration platform. Teams often use GitHub with CI workflows and pull requests.
Source: GitHub Actions CI docsA code hosting and DevOps platform. GitLab merge requests and CI/CD pipelines can display job or usage data from external systems.
Source: GitLab merge request docsAlso seen as: continuous integration
Continuous integration is the practice of frequently merging code into a shared repository and automatically building or testing it.
Source: GitHub Actions CI docsAlso seen as: merge requests, pull request, pull requests
A request to review and merge code changes. TelemHQ payloads can include branch or issue metadata so usage can be attached to review context.
Source: GitLab merge request docsAlso seen as: databases
A system for storing and querying structured data. TelemHQ uses database records to keep users, trackers, job runs, teams, and billing state.
Source: PostgreSQL overviewAlso seen as: PostgreSQL
An open source relational database. Applications use it to store structured rows and query them with SQL.
Source: PostgreSQL overviewAn in-memory data store often used for caching, queues, rate limits, and session storage.
Source: Redis docsAlso seen as: OAuth 2.0
An authorization framework that lets users grant an application limited access without sharing their password with that application.
Source: OAuth 2.0Also seen as: sessions
Server-side or cookie-backed state that remembers a signed-in user between requests.
Source: MDN glossaryAlso seen as: cookies
A small piece of data stored by the browser and sent with requests. Apps often use cookies to keep users signed in or remember preferences.
Source: MDN glossarySimple Mail Transfer Protocol, the internet protocol commonly used to send email between mail servers.
Source: RFC 5321An email delivery service and API. TelemHQ can use Resend as an email provider for notifications.
Source: Resend docsA plain-text writing format that uses lightweight punctuation for headings, links, lists, and code. TelemHQ blog drafts live in Markdown.
Source: Markdown projectAlso seen as: search engine optimization
Search engine optimization is the work of making pages clear, useful, and discoverable for people searching the web.
Source: Google Search Central SEO starter guideA newsletter and publishing platform. TelemHQ posts can be drafted in the repo and then published on Substack and the app blog.
Source: Substack Help CenterTry a model name, payload field, API term, or workflow word.