> For the complete documentation index, see [llms.txt](/llms.txt).
> A full single-fetch corpus is available at [llms-full.txt](/llms-full.txt).
---
title: Serverless endpoints
description: Build, deploy, connect, and operate AGNT5 workflows on provider-managed HTTP runtimes without a persistent worker process.
last_verified: 2026-07-09
---

A **serverless endpoint** is an HTTPS deployment that serves an AGNT5 manifest and accepts signed invoke requests. AGNT5 routes workflow, function, tool, and agent runs to the endpoint while the provider owns the HTTP runtime, scaling, and deployment lifecycle.

AGNT5 owns the serverless protocol and durable execution contract. Your provider's CLI owns local emulation, authentication, deployment, and provider rollback.

## Start here

<LinkCardGroup compact>
  <LinkCard
    title="Deploy to Cloudflare Workers"
    href="/docs/integrations/cloudflare-workers"
    icon="cloud"
    description="Create a new Worker, validate it locally, deploy it, sync it with AGNT5, and run the workflow."
  />
  <LinkCard
    title="Operate serverless endpoints"
    href="/docs/run/operate-serverless-endpoints"
    icon="settings"
    description="Validate, sync, verify, activate, disable, rotate secrets, and roll back an endpoint."
  />
  <LinkCard
    title="Serverless CLI reference"
    href="/cli/serverless"
    icon="terminal"
    description="Look up every agnt5 serverless command, flag, alias, and side effect."
  />
</LinkCardGroup>

## Follow the deployment lifecycle

1. Add the AGNT5 protocol handler with **`agnt5 serverless init`**.
2. Develop locally with the provider CLI, such as **`wrangler dev`** or **`vercel dev`**.
3. Deploy with the provider CLI, such as **`wrangler deploy`** or **`vercel deploy`**.
4. Validate the deployed manifest with **`agnt5 serverless validate`**.
5. Import the immutable provider version with **`agnt5 serverless sync --activate=false`**.
6. Gate promotion with **`agnt5 serverless status --verify`**.
7. Activate the verified deployment and run its components through AGNT5.

The AGNT5 CLI does not wrap provider development or deployment commands. Provider bindings, preview environments, build behavior, and rollback remain visible in the provider-native tool.

## Understand the endpoint contract

Every serverless endpoint exposes two routes:

| Route | Purpose |
| --- | --- |
| `GET /.well-known/agnt5` | Returns the `workerless.v1` manifest and component declarations. |
| `POST /agnt5/invoke` | Receives signed AGNT5 invoke requests and returns a result or durable suspension. |

The endpoint and AGNT5 deployment share an HMAC signing secret. Set `AGNT5_SERVERLESS_SIGNING_SECRET` in the provider, then pass the same value to **`agnt5 serverless sync`** through `--signing-secret-env` or an existing AGNT5 secret reference.

## Choose a host

| Host | SDK entrypoint | Public guide |
| --- | --- | --- |
| Cloudflare Workers | `@agnt5/sdk/serverless` | [Deploy to Cloudflare Workers](/docs/integrations/cloudflare-workers.md) |
| Vercel or Next.js | `@agnt5/sdk/serverless` | Provider guide is next in the beta documentation sequence. |
| Generic Node.js | `@agnt5/sdk/serverless/node` | Provider guide is next in the beta documentation sequence. |
| FastAPI | `agnt5.serverless` | Provider guide is next in the beta documentation sequence. |
| Deno or Hono | `@agnt5/sdk/serverless` | Use the host adapter that preserves the original `Request`. |

Cloudflare Workers is the first public end-to-end beta path. The SDK also contains adapters and repository examples for the other hosts, but they do not yet have the same public, independently testable guide.

## Know the beta limits

Serverless endpoints support signed dispatch, immutable manifest sync, encrypted signing-secret references, component route ownership, durable step checkpoints, timeout suspension, retries, concurrency, throttling, rate limits, debounce, priority, singleton keys, and idempotency metadata.

Batch declarations are rejected during the serverless beta because aggregate batching enforcement is not available. Keep batch policies on persistent workers.

Serverless dispatch must be enabled for your AGNT5 workspace. If endpoint validation succeeds but sync reports that serverless execution is unavailable, contact your AGNT5 workspace operator.

## Next steps

- [Deploy to Cloudflare Workers](/docs/integrations/cloudflare-workers.md): complete the first public end-to-end serverless path.
- [Operate serverless endpoints](/docs/run/operate-serverless-endpoints.md): promote and recover immutable provider deployments safely.
- [Serverless CLI reference](/cli/serverless.md): inspect all serverless commands and flags.
- [Workflows](/docs/build/workflows.md): define durable components for your endpoint.