Thema

#vercel

Loots, Blogposts und verwandte Themen rund um diesen Tag. Folge dem Tag, damit passende Updates in deinem Orbit bleiben.

#vercel
14Gezeigte Loots
30Gezeigte Artikel
8Verlinkte Nachbar-Tags
Anschluss-Themen

Wenn du tiefer einsteigen willst, helfen die benachbarten Tags beim Vergleichen und Querlesen.

Loot

Mehr aus diesem Thema

Alle Loots entdecken

Run AI video jobs without holding one HTTP request open

0
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Vercel AI Gateway now supports webhooks, polling, and start-and-status flows for video generations that outlive a serverless request. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it is Vercel AI Gateway can now run video generation asynchronously. Instead of keeping one HTTP request open while a provider renders a video, an application can receive a webhook, poll with short status requests, or start a job and retrieve its result later. The SDK supports four patterns: a durable Workflow SDK run, generateVideo with a webhook, generateVideo with polling, or separate startVideo and getVideoStatus calls. Existing synchronous generateVideo integrations continue to work. Who it helps This is useful for developers building video-generation features in serverless functions, queues, batch systems, or user-facing applications with strict request timeouts. The start-and-status path is particularly practical when rendering may take minutes or when another worker needs to collect the result. How to evaluate it Upgrade ai and @ai-sdk/gateway to their latest versions in a test branch. Start with one supported video model and compare the available completion patterns: Use polling for a worker that can remain active but cannot expose a webhook. Use startVideo when the caller must return immediately. Use a verified webhook or Workflow SDK when completion should resume a durable process. Test completed, failed, retried, and timed-out jobs. Confirm that job metadata can be serialized into your queue or database and that the final video is copied to storage you control. Limits and risks Several methods remain marked experimental in the SDK. Hosted result URLs can expire, and webhook receivers need authentication, replay protection, and idempotent processing. generateVideo webhooks require a shared token and store because that convenience path does not expose the job’s signing secret. Provider moderation, retention, latency, regional availability, and generation limits still apply. Asynchronous execution prevents one long request from timing out; it does not make rendering instant or remove provider failures. Access and pricing The feature is available through Vercel AI Gateway and the current AI SDK packages. Vercel does not list one universal price for asynchronous jobs because generation costs depend on the selected video model and provider. Check the model page and Gateway billing configuration before production use. Sources Vercel announcement and implementation examples Vercel video-generation documentation
Free
Review open
0

Run GPT-5.6 Sol through Vercel AI Gateway at 50% off through September 18

0
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Vercel has temporarily halved GPT-5.6 Sol token prices for requests billed directly through AI Gateway. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. What it is Vercel is applying a 50% discount to GPT-5.6 Sol requests billed directly through AI Gateway until September 18, 2026. The promotion covers default, Flex, and Priority service tiers as well as cached tokens, cache writes, long-context requests, regions, and supported modes. Who it helps The offer is most useful for teams already evaluating GPT-5.6 Sol for coding agents, document analysis, or long-context workloads. Existing AI Gateway requests using openai/gpt-5.6-sol receive the lower rate without a model-ID change. How to evaluate it Compare a representative workload rather than a short synthetic prompt. Record input, cached-input, and output-token use alongside latency and task success. Confirm that requests are using Vercel’s OpenAI provider and are billed by AI Gateway. Published promotional prices per million tokens are $2.50 input and $15 output for Default, $1.25 and $7.50 for Flex, and $5 and $30 for Priority. Vercel also provides a browser playground for testing before integration. Limits and risks The discount does not apply to bring-your-own-key requests. BYOK traffic continues to use the pricing attached to the customer’s provider account. Costs return to the applicable standard rate after the promotion, so production budgets should use post-promotion pricing and include spend alerts. AI Gateway adds another service to the request path. Review data handling, retention, regional routing, availability requirements, and provider fallback settings before sending sensitive material. Access and pricing An AI Gateway account and API key are required. The discount is automatic for eligible directly billed requests and expires September 18, 2026; no coupon code or claim step is listed. Sources Vercel promotion and pricing table Vercel AI Gateway
Free
Review open
0

Cap AI Gateway spend before coding agents run away with the bill

0
Text: AI-generated
AI-generated · Automatically published by LinkLoot. Vercel AI Gateway now supports team, project, and API-key budgets with alerts and request blocking when a cap is reached. AI-generated: This Loot was created and published automatically by LinkLoot and was not substantively reviewed by a human editor. Vercel AI Gateway now has scoped spend budgets, which makes it worth a look for teams running agents through one shared model gateway. What it is Vercel added budgets that can cap AI Gateway spend at the team, project, or API-key level. A request can be checked against multiple budgets, and the gateway rejects it when any applicable limit is exhausted. Who it helps This is useful for product teams, agencies, and internal platform owners who let several agents, apps, or experiments share the same model gateway. It gives finance and engineering a clearer stop-loss than watching one API key after the fact. How to evaluate it Start by mapping current gateway traffic to projects and keys, then create low-risk alert-only thresholds before using hard caps on production workloads. The changelog shows CLI commands for setting team and project budgets, listing configured limits, and removing them. Limits and risks Budgets can block requests once a limit is reached, so production agents need fallbacks, user-visible errors, or a runbook for raising limits. Vercel also notes that BYOK spend is not counted against budgets by default, which matters if teams mix provider keys with gateway-managed spend. Sources Vercel AI Gateway budgets changelog
Free
Review open
0

Use Vercel's AI Gateway leaderboard export for model adoption research

0
Vercel opened the data behind its AI Gateway leaderboards, giving builders a downloadable and queryable source for model, lab, app, and provider adoption trends. Vercel's AI Gateway leaderboard export is useful when you need a quick market signal before choosing models, writing AI coverage, or comparing provider adoption. What it is Vercel publishes aggregated AI Gateway leaderboard data under a CC BY 4.0 license. The leaderboards rank models, labs, apps, and inference providers across metrics such as requests, token volume, spend, and generated image or video counts. Who it helps It is practical for AI builders, analysts, editors, and product teams who want a repeatable source for model adoption trends instead of relying only on social buzz or benchmark tables. How to evaluate it Start with the leaderboard UI, then use the leaderboard-export endpoint for CSV or programmatic checks. Compare model share over time, filter by modality when needed, and treat the data as Vercel AI Gateway usage rather than the whole AI market. Limits and risks The dataset only reflects traffic visible through Vercel's gateway and opted-in leaderboard surfaces. It can show adoption momentum, but it cannot prove global usage, model quality, or total revenue across providers. Sources Vercel changelog AI Gateway leaderboard export endpoint
Free
Review open
0

Make Vercel CLI 55 project linking safe for CI agents

0
Vercel CLI 55 changes how vercel link, deploy, pull, dev, and git connect resolve teams and projects. CI and agent workflows should pass --team/--scope or set VERCELORGID and VERCELPROJECTID before upgrading, because --yes no longer selects a team automatically. Use this as an upgrade checkpoint before moving CI, coding agents, or deployment scripts to Vercel CLI 55. The linking flow now resolves the team first and searches projects inside that team, which makes project discovery faster but removes an old implicit behavior: --yes confirms prompts, but it does not choose a team. For promptless runs, set VERCELORGID and VERCELPROJECTID, or pass --team/--scope explicitly. If a command has multiple possible teams and no explicit signal, non-interactive runs can fail with actionrequired: missingscope before creating or touching a link. That is useful for safety, but only if your automation expects it.
Free
Review open
0

Run Thinking Machines Inkling through Vercel AI Gateway

0
Use Vercel's AI Gateway model page to test Inkling as thinkingmachines/inkling without adding another provider integration. Inkling is Thinking Machines' open-weights multimodal MoE model, with text, image and audio inputs, controllable thinking effort, and long-context support. Treat it as an evaluation target for multimodal agent workflows, not as an automatic replacement for stronger closed frontier models. Vercel has added Thinking Machines' Inkling to AI Gateway under thinkingmachines/inkling, so teams already using AI Gateway can test it through the same playground, routing, budget, retry and usage-tracking layer they use for other models. Inkling is an open-weights multimodal MoE model from Thinking Machines with text, image and audio inputs, controllable thinking effort and long-context support. Use it for practical evaluation of multimodal agent workflows, document/audio reasoning and fine-tuning paths; compare latency, cost and output quality before moving production traffic.
Free
Review open
0

Plan Next.js upgrades before the July 20 security patch window

0
Next.js is moving to scheduled security releases. The first planned patch window targets July 20, 2026, with fixes for Next.js 16.2 and 15.5 covering 4 high and 5 medium severity issues. Use this as an upgrade-planning checkpoint, not as a CVE detail source until the final advisory lands. Use this official Next.js announcement to schedule upgrade work before the July 20, 2026 security release window. The post says the first scheduled release will include patch releases for Next.js 16.2 and 15.5, covering 4 high and 5 medium severity issues. Treat it as planning material until the final advisory publishes CVEs and affected ranges.
Free
Review open
0

Run Playwright tests faster on Vercel with Endform

0
Endform runs existing Playwright suites on isolated cloud runners and plugs the result into Vercel preview and production deployments. Endform is a managed Playwright test runner for Vercel teams that want deployment checks without building their own browser-runner fleet. It is useful when a suite is slow because tests run serially, collide on shared state, or need trace history across preview deployments. Vercel's Marketplace changelog says Endform can run each test on its own isolated machine, link pass/fail checks to Vercel deployments, keep full Playwright traces, and charge by test runtime. Endform's docs add the important setup caveat: tests run remotely, so the target app must be reachable by the remote runners or proxied through Endform's local-network option. Best fit Vercel apps with Playwright suites that slow down preview deploys. Teams that want deployment checks tied to traces and historical runs. SaaS products where flaky E2E tests delay releases. Projects that already use @playwright/test and want less CI plumbing. Check before using Confirm pricing and runtime limits for your test volume. Make sure each test is independent enough to run in parallel. Check how preview deployment protection, secrets, and test accounts are handled. Validate that remote runners can reach the app or configure the proxy path. Keep destructive tests away from production data.
Free
Review open
0

Give Vercel agents their own inbox with AgentMail

0
AgentMail adds API-managed email inboxes, webhooks, custom domains, and live message streams to Vercel-hosted AI agents. AgentMail is an email-infrastructure tool for Vercel apps that need real inboxes for agents, assistants, and workflow automation. It is useful when an agent must receive attachments, handle email-based verification, route support messages, or keep a human reviewer in the loop without sharing one generic mailbox. The Vercel Marketplace page lists AgentMail as a native integration for provisioning inboxes, managing custom domains, and sending or receiving email programmatically. The product page adds the practical developer angle: the TypeScript SDK works in Next.js API routes, App Router route handlers, serverless functions, and Edge functions. Best fit AI support agents that need a dedicated inbound address. Browser or workflow agents that must handle email-based login checks. Document-processing flows that receive attachments and reply automatically. Multi-tenant SaaS products that need one inbox per user, tenant, or agent. Check before building Confirm pricing, limits, and Vercel Marketplace billing for your account. Use separate inboxes and domains for tenants or high-risk workflows. Validate webhook signatures and keep retries idempotent. Treat inbound email and attachments as untrusted input before handing them to an agent. Add human review for workflows that can send external replies or trigger account changes.
Free
Review open
0

Build X bots with Vercel Chat SDK

0
Use Vercel Chat SDK's new X adapter to handle public mentions and direct messages from one bot codebase. Vercel added an X adapter to Chat SDK on July 14, 2026. It lets teams build bots that reply to public mentions and direct messages through X API v2 and the X Activity API while keeping the same Chat SDK pattern used for Slack, Discord, GitHub, Teams, Telegram, and WhatsApp. Best fit: teams already building multi-channel support, community, or workflow bots with Chat SDK. Check before use: The adapter handles CRC verification, webhook signature checks, and OAuth token refresh for long-running bots. X supports likes as the only reaction in this adapter. Responses post once after completion because X has no native streaming. X automation rules still apply to automated messages, so review policy and rate limits before production use.
Free
Review open
0

Repair Vercel build settings from the CLI before redeploying

0
Use Vercel CLI project update to fix framework presets, build commands, output directories, and auto-detection without opening the dashboard. Vercel now lets teams update project framework and build settings from the terminal with vercel project update. It is most useful when an agent or CI helper has diagnosed a failed deployment and needs to correct the framework preset, build command, install command, development command, or output directory before redeploying. Try it when a project was imported with the wrong preset, a monorepo output path changed, or a dashboard-only fix would slow down an automated recovery flow. Use --format=json when another script needs to inspect what changed, and use --auto-detect when you want Vercel to resume automatic detection for a setting. What to check first: Update the Vercel CLI to v54.21.1 or later. Confirm the linked project or pass the project name explicitly. Review changed settings before redeploying production. Do not pipe secrets into build settings; keep secret values in environment variables. Example use cases: Fix a Vite-to-Next.js preset mismatch. Reset a stale output directory to auto-detection. Let an agent repair build settings using JSON output for verification.
Free
Review open
0

Generate editable Seedream 5.0 Pro images through Vercel AI Gateway

0
Vercel AI Gateway now exposes ByteDance Seedream 5.0 Pro as bytedance/seedream-5.0-pro, giving teams a routed API path for production image generation and editing workflows. Vercel added ByteDance Seedream 5.0 Pro to AI Gateway on July 11, 2026. Use it when you want one API layer for image generation, usage tracking, budgets, routing rules, retries, and BYOK behavior instead of wiring a separate image provider directly into every app. The practical draw is not just another model listing. ByteDance positions Seedream 5.0 Pro for production image work: layer-separated outputs, precise local edits, coordinate and hex color control, multilingual text rendering, infographics, product visuals, and marketing assets. Through Vercel's AI SDK, the model id is bytedance/seedream-5.0-pro. Why bookmark it Vercel gives app teams a standard gateway route for Seedream 5.0 Pro instead of a one-off provider integration. Seedream 5.0 Pro is aimed at editable commercial assets, not only flat prompt-to-image output. ByteDance says the model supports layer separation, targeted editing, 14-language text generation, and design-oriented controls. Vercel says AI Gateway can track usage and cost, apply budgets, configure routing rules, support Zero Data Retention, and use provider pricing with no platform markup. Quick checks before shipping Confirm your Vercel project can access AI Gateway and the model playground. Test text rendering, brand colors, localization, and image edits with real campaign assets. Compare Vercel Gateway pricing and retention settings with direct ByteDance/Lumina access. Check whether your workflow needs layered export features that may only exist in specific ByteDance/Lumina surfaces. Keep generated commercial assets in human review until rights, brand, and regional requirements are clear.
Free
Review open
0

Cut LLM routing waste with Vercel AI Gateway provider sorting

0
Vercel AI Gateway can now rank providers by cost, time to first token, or throughput before fallback, so agent apps can optimize routing without hard-coding provider order. Vercel added provider sorting to AI Gateway. Set providerOptions.gateway.sort to cost, ttft, or tps and the gateway ranks available providers behind a model by the selected metric before it falls back to the next provider. Use it when a model has multiple providers and your workflow has a clear priority: lowest listed input cost for batch jobs, lower time to first token for interactive chat, or higher tokens per second for long outputs. The routing metadata can show which providers were considered, attempted, deprioritized, or selected. This is useful, but it is not a magic optimizer. Provider sorting works best after you define the workload, check data-retention constraints such as ZDR, and verify model/provider behavior with your own prompts and token mix.
Free
Review open
0

Use Vercel Connect to stop storing bot tokens in Chat SDK projects

0
Vercel's Chat SDK now supports Vercel Connect, letting bot builders use connector-backed Slack, GitHub, and Linear credentials instead of storing long-lived tokens and signing secrets in their own app. Use Vercel Connect to stop storing bot tokens in Chat SDK projects Vercel Connect support in Chat SDK is worth bookmarking if you build bots that talk to Slack, GitHub, or Linear. The practical win is credential handling: @vercel/connect/chat returns adapter helpers that use connector UIDs, fresh short-lived tokens, and OIDC-verified inbound triggers instead of app-managed token storage. Best fit Use case Why it helps Caveat --- --- --- Slack bots on Vercel connectSlackAdapter() can feed credentials into the Slack adapter. Vercel Connect is still beta. GitHub or Linear workflow bots Connector-backed auth reduces manual token rotation work. Check connector availability for your account. Inbound bot events Vercel documents trigger forwarding with OIDC validation. Review event scope and permissions before production use. What to check first Confirm your project can use Vercel Connect and the needed connector. Review the @vercel/connect/chat adapter helper docs. Keep least-privilege scopes on Slack, GitHub, and Linear connectors. Test inbound trigger verification before trusting production events. Read the beta terms, because connector behavior can change before GA. Practical LinkLoot angle This is not broad platform news, but it is a useful security and maintenance shortcut for bot projects. If your Chat SDK bot currently stores tokens or webhook signing secrets, test Vercel Connect in a staging deployment and compare the operational surface: fewer secrets, shorter-lived outbound credentials, and a standard verification path for inbound events. Source check Vercel's July 8, 2026 changelog confirms Chat SDK support for Vercel Connect and the @vercel/connect/chat subpath. The Chat SDK documentation explains setup, connector UIDs, adapter helpers, outbound token handling, and inbound webhook verification.
Free
Review open
0
Blog

Verwandte Artikel

Blog durchsuchen
AI & Automation

Qwen3.8 Max 0902 reaches AI Gateway with a pinned snapshot

Alibaba's Qwen3.8 Max 0902 is now available through Vercel AI Gateway, giving developers a dated model ID for repeatable coding and agent wo…

Tools & Apps

Next.js 15.5.24 and 16.3.3 close two critical RCE paths

Next.js shipped 15.5.24 and 16.3.3 after disclosing a critical Windows-hosted RCE and a separate AVIF image-optimization RCE path.

Tools & Apps

Vercel Sandbox reaches four regions for lower-latency agent workloads

Vercel Sandbox is now available in four regions, adding Paris alongside three U.S. locations and introducing project-level failover settings…

Tools & Apps

Vercel CDN enables Encrypted Client Hello for Vercel DNS domains

Vercel CDN now supports Encrypted Client Hello for domains managed by Vercel DNS, turning on hostname privacy at the platform layer where br…

Tools & Apps

Vercel moves Sandbox defaults to versioned managed images

Vercel Sandbox SDK v3 now defaults new sandboxes to open-source managed images, changing the base operating system, toolchain, and update mo…

Tools & Apps

Vercel WAF now protects Blob stores in beta

Vercel has extended its Web Application Firewall to Vercel Blob stores in beta, letting teams apply deny, challenge, and rate-limit rules to…

Tools & Apps

Vercel Sandbox stops billing internet downloads for agent runs

Vercel Sandbox no longer counts package installs, repository clones, external artifacts, or dataset downloads toward Sandbox Data Transfer u…

Tools & Apps

Vercel Connect gives GitHub Tools short-lived tokens for agent workflows

Vercel has added first-class Vercel Connect support to GitHub Tools, letting agent apps mint short-lived, scoped GitHub tokens at runtime in…

Tools & Apps

Upgrade Vercel Projects Before Node.js 20 Blocks New Deployments

Vercel will disable Node.js 20 for Builds and Functions on October 1, 2026, after the Node.js 20 release line reached end of life. Existing …

Tools & Apps

Mark Vercel secrets as Sensitive before build logs expose them

Vercel now redacts Sensitive Environment Variable values from build logs, but only when the variable is marked Sensitive and the value is 32…

AI & Automation

Debug Vercel agent runs from MCP or the CLI

Vercel now exposes eve Agent Runs through MCP tools and CLI commands, so teams can inspect traces, reasoning, tool calls, token usage, lifec…

Tools & Apps

Check Vercel deploy files before agents ship them

Vercel CLI now supports dry-run deployments, giving teams and coding agents a JSON manifest of what would ship before a deployment is create…

Tools & Apps

Script Vercel Flags Segments Before Agents Change Targeting by Hand

Vercel Flags segments can now be managed from the Vercel CLI, giving teams a scriptable way to create, inspect, and update reusable targetin…

AI & Automation

Reroute AI models without code changes using Vercel AI Gateway rules

Vercel AI Gateway now supports routing rules, giving teams a gateway-level way to control model use and reroute traffic when a model is reti…

Tools & Apps

Use Vercel Services to Ship Private Backends With Agent Workflows

Vercel's Ship 2026 updates make microservices, containers, agent workflows, scoped credentials, and production investigations first-class pa…

Tools & Apps

Audit Vercel Projects Before Agents Leave Preview URLs and Tokens Exposed

Vercel's Security Dashboard is now in private beta, giving teams one place to find weak 2FA coverage, exposed preview environments, plaintex…

Tools & Apps

Mount S3 in Vercel Sandbox before your agents copy every dataset

Vercel Sandbox now supports FUSE-based filesystems, so agent and developer workloads can mount S3, network filesystems, or custom storage dr…

Business & Karriere

Audit Vercel agent access before the new AI liability terms surprise your team

Vercel's updated terms make AI functionality and connected third-party tools an operational risk owners should review, especially where agen…

Tools & Apps

Vercel Adds Agent Run Traces to Its MCP and CLI

Vercel has added Agent Runs observability to its MCP and CLI, giving teams commands to list projects with runs, inspect metadata, and fetch …

Tools & Apps

Deploy AI-built prototypes to Vercel without Git or the CLI

Vercel Drop lets users deploy a file, folder, or zip archive by dragging it into the browser, creating a production project without Git, CLI…

Tools & Apps

Use Vercel AI Gateway routing rules before model outages force code changes

Vercel AI Gateway now has beta routing rules that let teams rewrite or deny model requests at the gateway level instead of changing applicat…

Tools & Apps

Use Vercel Service Bindings before exposing private backends

Vercel Service Bindings let one service call another through internal URLs, routing, TLS, and reachability grants without creating a public …

Business & Karriere

Build Shopify storefronts faster now that Hydrogen deploys to Vercel

Shopify and Vercel are turning Hydrogen into a framework-agnostic, runtime-agnostic commerce toolkit, with a Vercel deploy path for the Next…

Tools & Apps

Use Vercel Services when one repo needs multiple backends

Vercel Services lets teams deploy multiple frontends and backends from one project, share one domain, and connect services privately through…

Tools & Apps

Use Vercel 5GB Functions only when your bundle really needs serverless

Vercel Functions can now ship Node.js and Python bundles up to 5GB on Fluid compute, but the beta is best for specific workloads with large …

Tools & Apps

Send Vercel Audit Logs to S3 before compliance reviews get messy

Vercel expanded Audit Logs to more than 400 team activity events and moved delivery into Vercel Drains, giving Enterprise teams a cleaner pa…

AI & Automation

Build voice agents through Vercel AI Gateway, but keep the beta label visible

Vercel AI Gateway now supports realtime voice, speech generation, and transcription through AI SDK 7, with beta limits and server-minted tok…

Tools & Apps

Find Core Web Vitals regressions from the Vercel CLI

Vercel now lets teams query Speed Insights data with vercel metrics, so developers and coding agents can inspect real-user Core Web Vitals f…

AI & Automation

Trace Vercel eve agent runs before production bugs vanish into logs

Vercel added Agent Runs for eve projects, giving teams a dashboard for triggers, token usage, turns, model calls, tool calls, and runtime fa…

AI & Automation

Use AI SDK 7 to move TypeScript agents from demos to production

Vercel AI SDK 7 is a confirmed major release for production TypeScript agents, adding WorkflowAgent, harness adapters, stricter runtime requ…