---
title: Eve Pricing and Limits
product: vercel
url: /docs/eve/pricing
canonical_url: "https://vercel.com/docs/eve/pricing"
last_updated: 2018-10-20
type: reference
prerequisites:
  - /docs/eve
related:
  - /docs/functions/usage-and-pricing
  - /docs/workflows/pricing
  - /docs/sandbox/pricing
  - /docs/ai-gateway/pricing
  - /docs/functions/limitations
summary: Understand how Eve usage maps to Vercel resources and inherited platform limits.
install_vercel_plugin: npx plugins add vercel/vercel-plugin
---

# Pricing and Limits

Eve usage is billed through the Vercel resources and third-party services your agent uses. An Eve
deployment can use Vercel Functions for compute, Vercel Workflow for durable sessions, Vercel
Sandbox for isolated command execution, and AI Gateway or model providers for model calls.

> **💡 Note:** Pricing depends on the features your agent uses, the Vercel plan for the project, and any model or
> third-party provider usage. Review the linked product pricing pages for current rates.

## Billable resources

| Resource | When Eve uses it | Learn more |
| -------- | ---------------- | ---------- |
| Vercel Functions | Serving the compiled agent routes, session requests, stream attachments, channel webhooks, and tool execution. | [Functions usage and pricing](/docs/functions/usage-and-pricing) |
| Vercel Workflow | Persisting session, turn, and subagent progress so runs can pause, resume, and survive redeploys. | [Workflow pricing and limits](/docs/workflows/pricing) |
| Vercel Sandbox | Running isolated filesystem and command execution when your agent uses the Vercel sandbox backend. | [Sandbox pricing and limits](/docs/sandbox/pricing) |
| AI Gateway | Resolving model strings such as `openai/gpt-5.4-mini` and routing model requests. | [AI Gateway pricing](/docs/ai-gateway/pricing) |
| Model providers | Processing input, cached, and output tokens for the models your agent calls. | [AI Gateway model list](/ai-gateway/models) |

## Common cost drivers

- **Session volume**: Each session and turn invokes agent routes and creates Workflow events.
- **Model usage**: Prompt length, tool results, reasoning, cached tokens, and output length affect
  model costs.
- **Tool calls**: External API calls can increase Function duration, Workflow event count, and
  third-party usage.
- **Streaming**: Stream writes are persisted by Workflow and count toward Workflow data written and
  retained.
- **Sandbox usage**: Command execution, provisioned resources, network transfer, snapshot storage,
  and sandbox creation can add Vercel Sandbox usage.

## Limits

Eve inherits limits from the platform products behind the agent:

- **Function limits**: Agent route runtime, memory, bundle size, request body size, concurrency, and
  regional behavior follow [Vercel Functions limits](/docs/functions/limitations).
- **Workflow limits**: Session durability, event creation, stream chunks, hook tokens, replay
  duration, payload size, and run storage follow [Workflow run limits](/docs/workflows/pricing#workflow-run-limits).
- **Sandbox limits**: Sandbox runtime, vCPU, memory, network, snapshot, and tag limits follow
  [Sandbox pricing and limits](/docs/sandbox/pricing).
- **Model limits**: Context windows, rate limits, output limits, and provider availability depend on
  the selected model and provider.
- **Channel limits**: Slack, HTTP clients, and other channel platforms can impose their own request,
  payload, retry, and rate limits.

## Estimate usage

To estimate production usage, start with one representative agent task and record:

1. How many turns the session takes.
2. How many model calls and tool calls each turn makes.
3. The input, cached, and output tokens per model call.
4. The amount of data streamed to the client.
5. Whether the task uses sandbox execution, snapshots, network access, or long-lived persistence.

Then map those measurements to the resources above. Agent Runs shows token counts, timing, tool
calls, and turn breakdowns, making it a practical starting point for real usage estimates.

## Cost controls

- Use smaller or cheaper models for low-risk turns, and reserve larger models for tasks that need
  them.
- Keep tool results and message history concise so the model receives only relevant context.
- Move repeatable instructions into skills so they load only when relevant.
- Use sandbox network policies and lifecycle hooks to limit unnecessary network and compute usage.
- Break very large or long-running jobs into smaller sessions or subagents when they approach
  Workflow replay or storage limits.
- Configure [Spend Management](/docs/spend-management) and project alerts for production agents.

## Next steps

- [Concepts](/docs/eve/concepts): learn how Eve's runtime pieces fit together.
- [Observability](/docs/eve/observability): inspect Agent Runs and optional OpenTelemetry spans.


---

[View full sitemap](/docs/sitemap)