# Telnyx Compute: Functions — Documentation Index > Functions documentation within the Compute section of the Telnyx developer docs (https://developers.telnyx.com). > This file: https://developers.telnyx.com/docs/development/llms/compute-functions-llms-txt · Root index: https://developers.telnyx.com/llms.txt ## Overview - [Functions](https://developers.telnyx.com/docs/edge-compute/overview.md): Functions are the compute primitive of Telnyx Edge Compute: an HTTP server in a container, wired to KV, stateful actors, object storage, and the Telnyx API. ## Get Started - [Quickstart](https://developers.telnyx.com/docs/edge-compute/quickstart.md): Install the CLI, scaffold a function in the language of your choice, ship it, and curl the live URL — about five minutes. ## Best Practices - [Best Practices](https://developers.telnyx.com/docs/edge-compute/best-practices.md): Production patterns for Edge Compute functions: configuration, connection reuse, KV caching, state placement, error handling, and observability. ## Guides - [AI Assistants and Edge Compute](https://developers.telnyx.com/docs/edge-compute/guides/ai-assistant-backend.md): Use a Telnyx Edge Compute function as the backend for dynamic variables and webhook tool calls — no separate server required. ## Local Development - [Local Development](https://developers.telnyx.com/docs/edge-compute/development.md): Run and test Edge Compute functions locally with each language's native tooling. Standalone functions need no emulator, only your usual runtime and curl. ## Configuration - [Configuration](https://developers.telnyx.com/docs/edge-compute/configuration.md): Reference for the Edge Compute TOML manifest, func.toml or telnyx.toml, covering the identity block, environment variables, and every binding declaration. - [Environment Variables](https://developers.telnyx.com/docs/edge-compute/configuration/environment-variables.md): Configure Edge Compute functions with ordinary environment variables declared in func.toml or injected by the platform, from secrets, and from bindings. - [Secrets](https://developers.telnyx.com/docs/edge-compute/configuration/secrets.md): Organization-scoped values for sensitive data, managed with telnyx-edge secrets. Every function reads them as environment variables or via typed bindings. ## CI/CD - [CI/CD](https://developers.telnyx.com/docs/edge-compute/deploy.md): Deploy Edge Compute functions from CI: install telnyx-edge, authenticate with an API key, and ship, with GitHub Actions, GitLab, and CircleCI recipes. - [Routes & Domains](https://developers.telnyx.com/docs/edge-compute/configuration/routing.md): Every deployed Edge Compute function gets a public HTTPS URL at telnyxcompute.com. HTTP requests to that URL are the only way to invoke a function. - [Versions & Rollback](https://developers.telnyx.com/docs/edge-compute/configuration/versions.md): Every telnyx-edge ship produces an immutable revision. Use revisions list to see deploy history and rollback to instantly retarget traffic to a prior revision. ## Custom Domains - [Overview](https://developers.telnyx.com/docs/edge-compute/custom-domains.md): Serve Edge Compute functions from your own domain with customer-provided TLS certificates. - [Quick Start](https://developers.telnyx.com/docs/edge-compute/custom-domains/quick-start.md): Declare a custom domain in telnyx.toml, register it with the CLI, and route traffic from your own hostname to an Edge Compute function. - [API Reference](https://developers.telnyx.com/docs/edge-compute/custom-domains/api-reference.md): REST endpoints under /v2/compute/domains for creating, listing, verifying, and deleting custom domains bound to Edge Compute functions. ## Runtime APIs - [Overview](https://developers.telnyx.com/docs/edge-compute/runtime.md): What Edge Compute provides at runtime: the container execution environment, the per-language entrypoint contract, and bindings to platform resources. - [Execution Model](https://developers.telnyx.com/docs/edge-compute/runtime/execution-model.md): Functions run as Linux containers scaled with traffic: cold starts, warm reuse, scale to zero, request budget, HTTP-only trigger, no durable memory. - [HTTP Handler](https://developers.telnyx.com/docs/edge-compute/runtime/http-handler.md): The per-language entrypoint contract — which file the platform runs, the signature you implement, who owns the HTTP server, and who answers health probes. - [Overview](https://developers.telnyx.com/docs/edge-compute/runtime/bindings.md): Typed, pre-authenticated handles to platform resources, resolved by the runtime from a manifest declaration. - [Overview](https://developers.telnyx.com/docs/edge-compute/telnyx-api.md): Call the Telnyx API from Edge Compute through a pre-authenticated binding — no API keys in your code. - [Quick Start](https://developers.telnyx.com/docs/edge-compute/telnyx-api/quick-start.md): Declare, type, and ship a function that returns your Telnyx account balance through the binding. - [API Reference](https://developers.telnyx.com/docs/edge-compute/telnyx-api/api-reference.md): The Telnyx API binding is a pre-authenticated client handle — discover its resources and methods through generated types or the client method reference. - [Receiving Messages](https://developers.telnyx.com/docs/edge-compute/telnyx-api/receiving-messages.md): Handle inbound SMS on Edge Compute — your function is the messaging profile webhook, and replies go out on-net with no 10DLC campaign. - [Handling Calls](https://developers.telnyx.com/docs/edge-compute/telnyx-api/handling-calls.md): Answer inbound calls on Edge Compute via Call Control — your function is the Call Control app webhook; answer the call and play audio. - [Overview](https://developers.telnyx.com/docs/edge-compute/rate-limiting.md): Enforce per-key request budgets in bundled Edge Compute functions with a platform-managed rate limiter binding. - [Quick Start](https://developers.telnyx.com/docs/edge-compute/rate-limiting/quick-start.md): Add a rate limiter binding to an Edge Compute function, deploy it, and verify its behavior. - [API Reference](https://developers.telnyx.com/docs/edge-compute/rate-limiting/api-reference.md): Check a Telnyx Edge Compute rate limiter binding and interpret its result. ## Observability - [Overview](https://developers.telnyx.com/docs/edge-compute/observability.md): Observe Edge Compute functions with logs, metrics, deployment history, health checks, and CLI diagnostics. - [Logs](https://developers.telnyx.com/docs/edge-compute/observability/logs.md): Read runtime output and platform-generated invocation logs for Edge Compute functions. - [Log export](https://developers.telnyx.com/docs/edge-compute/observability/log-export.md): Push a function's runtime and invocation logs to an external OTLP endpoint as they happen. - [Metrics](https://developers.telnyx.com/docs/edge-compute/observability/metrics.md): View request, latency, CPU, and memory metrics for Edge Compute functions. - [Deployment history](https://developers.telnyx.com/docs/edge-compute/observability/deployment-history.md): Inspect the latest ship outcome and historical Edge Compute function deployments. - [Health checks](https://developers.telnyx.com/docs/edge-compute/observability/health-checks.md): Implement and externally probe an application-level health route for an Edge Compute function. - [API Reference](https://developers.telnyx.com/docs/edge-compute/observability/api-reference.md): REST endpoints under /v2/compute/funcs/{id} for fetching runtime logs, invocation records, and metrics for an Edge Compute function. ## CLI - [CLI Reference](https://developers.telnyx.com/docs/edge-compute/reference/cli.md): Every telnyx-edge CLI command in v0.5.3: install, authenticate, scaffold, deploy, and manage revisions, secrets, bindings, storage, and actor types. ## Platform - [Pricing](https://developers.telnyx.com/docs/edge-compute/platform/pricing.md): Telnyx Edge Compute functions bill on two meters — requests and CPU time — with a monthly free tier of 3.6M requests and 36M CPU-milliseconds. - [Limits](https://developers.telnyx.com/docs/edge-compute/platform/limits.md): Resource limits for Telnyx Edge Compute functions: request timeout, memory, body size, code size, deployment rate, and KV storage caps. ## API Reference (Functions) ### functions - [Get function logs](https://developers.telnyx.com/api-reference/functions/get-function-logs.md): Returns logs oldest first. `type=runtime` (default) returns function stdout/stderr. `type=invocations` returns one platform-generated record per HTTP request s… - [Get log export configuration](https://developers.telnyx.com/api-reference/functions/get-log-export-configuration.md): Returns the function's configured log export destination and which log types are exported. Headers are never returned. Returns 404 (error code 10005) when no d… - [Configure log export destination](https://developers.telnyx.com/api-reference/functions/configure-log-export-destination.md): Configures the external OTLP endpoint a function's runtime and/or invocation logs are pushed to as they happen. This operation is a **full replace, not a patch… - [Delete log export configuration](https://developers.telnyx.com/api-reference/functions/delete-log-export-configuration.md): Stops exporting a function's logs and removes its destination configuration. Idempotent: deleting when nothing is configured succeeds. - [Get function metric aggregates](https://developers.telnyx.com/api-reference/functions/get-function-metric-aggregates.md): Returns aggregate request, latency, CPU, memory, and resource-limit metrics for a function over the requested window. - [List function revisions](https://developers.telnyx.com/api-reference/functions/list-function-revisions.md): Lists a function's ship history newest first, including per-ship failure stage and reason when recorded. - [Inspect latest function ship](https://developers.telnyx.com/api-reference/functions/inspect-latest-function-ship.md): Returns the latest ship outcome. The stage is `none` on success, `pending` while building, or a failure stage such as `build`, `platform`, `pre_build`, `deploy…