Meta tags:

Headings (most frequently used words):

-

Text of the page (most frequently used words):
and (66), the (58), mcp (52), gateway (46), api (30), your (29), zuplo (26), call (25), every (24), traffic (16), one (15), you (14), llm (13), agents (13), for (12), server (12), spend (11), rate (11), with (11), apis (9), policy (9), engine (8), https (8), calls (8), same (8), com (7), agent (7), customers (7), both (7), caps (7), limits (7), per (7), route (7), what (7), tool (7), requests (7), from (7), govern (6), just (6), oauth (6), teams (6), client (6), before (6), can (6), openai (6), unified (5), programmable (5), management (5), users (5), new (5), routing (5), docs (5), real (5), auth (5), servers (5), cost (5), origin (5), live (4), minutes (4), models (4), that (4), accuweather (4), blockdaemon (4), behind (4), ship (4), model (4), guardrails (4), not (4), directions (4), audit (4), run (4), budgets (4), team (4), tools (4), token (4), through (4), explore (4), costs (4), security (4), attributed (4), user (4), over (4), which (4), systems (4), policies (4), into (4), existing (4), control (3), end (3), type (3), credit (3), finsolutia (3), yext (3), applications (3), are (3), llms (3), bill (3), need (3), critical (3), scoped (3), access (3), via (3), keys (3), rest (3), openapi (3), portal (3), see (3), already (3), each (3), pkce (3), dynamic (3), limiting (3), schema (3), prompt (3), injection (3), billing (3), spec (3), month (3), results (3), across (3), case (3), study (3), front (3), plan (3), free (3), introduction (3), secure (2), observe (2), fully (2), apps (2), under (2), two (2), outbound (2), feature (2), any (2), inbound (2), consumer (2), identity (2), quotas (2), serve (2), written (2), once (2), enforced (2), capabilities (2), turn (2), vendor (2), key (2), providers (2), cap (2), use (2), features (2), issues (2), connect (2), authenticates (2), logged (2), stops (2), spikes (2), illustrated (2), lower (2), budget (2), runaway (2), bad (2), validation (2), defense (2), reject (2), reaches (2), answers (2), siem (2), infrastructure (2), build (2), 2025 (2), code (2), base (2), url (2), swap (2), side (2), app (2), keep (2), sdk (2), point (2), const (2), our (2), sales (2), get (2), operationid (2), summary (2), attack (2), surface (2), faster (2), revenue (2), cut (2), they (2), controls (2), request (2), logs (2), months (2), mission (2), scale (2), hours (2), own (2), authentication (2), between (2), sits (2), also (2), includes (2), have (2), off (2), apigee (2), alongside (2), start (2), included (2), 100k (2), card (2), title, description, managed, canonicalurl, sourceurl, pagetype, homepage, generatedat, 2026, accounted, meet, blog, introducing, uptime, sla, soc, lake, michigan, union, vndr, mews, zumiez, has, kinds, belong, product, adds, those, way, dependency, does, made, consumers, well, load, absorb, middle, four, surfaces, without, adding, audited, jwt, mcps, graphql, caching, products, gitops, authenticated, verified, idp, tokens, itself, claude, cursor, codex, chatgpt, shows, session, applied, scopes, metering, surge, sends, unmetered, roof, automatically, lands, saved, days, total, workload, drives, halts, ceiling, blow, governance, abuse, blocked, this, week, reached, failures, limit, exceeded, invalid, 800, visibility, understand, doing, attribution, turns, raw, where, denials, cluster, how, latency, trends, time, dashboards, export, everything, datadog, monetization, metered, billed, plans, usage, based, built, wired, stripe, facts, dcr, cimd, 300, edge, locations, 20s, deploys, extension, other, provider, apply, import, baseurl, org, apikey, process, env, zuplo_ai_key, response, await, chat, completions, create, gpt, messages, role, content, summarize, data, mark, operations, deploy, json, paths, orders, getorder, fetch, order, resource, tickets, post, createticket, open, support, ticket, value, measure, first, smaller, resolution, checklist, absorbs, hit, stop, overspend, hard, surprise, overage, shrink, bot, prove, happening, then, exported, meter, price, unit, resolve, level, tracing, pinpoints, slow, hop, problems, fixed, become, escalations, ciso, secret, masking, actually, ask, move, was, easy, taking, switch, saving, ryan, waites, senior, director, hardware, footprint, reduction, gives, flexibility, efficiently, ensures, compliance, reduces, operational, complexity, focus, building, daryl, benzel, staff, software, engineer, served, didn, touch, line, plug, play, were, very, surprising, couple, had, working, miguel, madeira, cto, founder, launch, regulated, frequently, asked, questions, puts, kind, business, runs, logging, instead, being, split, proxy, experiment, difference, handling, coming, capping, applying, going, out, rules, protect, invoke, brokers, credentials, upstream, compliant, authorization, registration, implementing, revision, replace, yes, don, cutover, moved, kong, azure, switched, works, most, publishing, consolidate, onto, their, schedule, developer, core, comes, required, enough, put, production, pay, anything, next, steps, tier, signup, book, demo, talk, expert,

Text of the page (random words):
title the unified gateway for apis ai and mcp description secure govern and observe every api llm and mcp call on one programmable policy engine ai gateway mcp gateway mcp server and api management fully managed live in minutes canonicalurl https zuplo com sourceurl https zuplo com pagetype homepage generatedat 2026 10 08 secure govern and observe every api llm and mcp call zuplo is the unified gateway for apis and ai one programmable policy engine for the models your apps call and the agents that call you live in minutes spend under control every agent call accounted for meet the mcp gateway https zuplo com blog introducing zuplo mcp gateway live in minutes 99 99 uptime sla 1b end users soc 2 type ii customers accuweather blockdaemon lake michigan credit union finsolutia vndr mews yext zumiez your api has two new kinds of traffic your applications call models and ai agents call you both are api traffic and both belong behind one gateway outbound your product calls llms every ai feature you ship adds model calls to your traffic and to your bill those calls need routing spend caps and guardrails the same way any critical dependency does inbound ai agents call your api mcp made every agent an api consumer agents need identity scoped access quotas and docs real consumers to serve well not just load to absorb both directions one gateway in the middle auth rate limits spend caps and audit written once on one programmable policy engine and enforced on every api llm and mcp call in both directions one policy engine four capabilities zuplo is the unified gateway for apis ai and mcp auth rate limits spend caps and audit run on one programmable policy engine turn on the surfaces you need without adding a vendor agents scoped audited access for ai agents via mcp users api keys jwt oauth with per key rate limits apis mcps rest graphql mcp servers behind one gateway llms route providers with budgets caching guardrails products ai gateway ai gateway route llm traffic cap spend per team mcp gateway mcp gateway ship mcp to customers govern the mcp your teams use mcp server features mcp servers your openapi as mcp tools api management api management portal keys rate limits gitops every call is authenticated as a verified identity api keys your idp or oauth tokens the gateway issues itself see every agent every call every token claude cursor codex and chatgpt already connect through zuplo explore what one gateway shows you costs budgets security and every tool call attributed agent traffic every mcp tool call attributed to an agent each session authenticates with oauth 2 1 and pkce and each tool call is logged with the client the user behind it and the policy the gateway applied scopes rate limits metering cost control dynamic rate limiting stops origin cost spikes a traffic surge sends unmetered origin spend through the roof zuplo caps it automatically before the bill lands illustrated 42 9k saved over 14 days 41 lower total spend ai budgets every token attributed to a team under one budget see which workload drives llm cost zuplo caps spend per team and halts requests at the ceiling so a runaway agent can t blow the budget security governance bad traffic stops at the gateway auth schema validation rate limits and prompt injection defense reject abuse before it reaches your systems the same policies for every api model and mcp server illustrated 12 4k requests blocked this week 0 reached your origin auth failures 5 2k rate limit exceeded 4 1k invalid schema 2 3k prompt injection 800 visibility understand what every agent is doing per user and per client attribution turns raw mcp traffic into answers which agents call which tools where denials cluster and how latency trends explore it in real time dashboards or export everything to datadog or your siem monetization api traffic metered and billed plans quotas and usage based billing built into the gateway wired to stripe with no billing infrastructure to build facts mcp spec 2025 11 25 at ga oauth 2 1 pkce dcr cimd 1b end users via accuweather 300 edge locations 20s deploys both directions in code the models your apps call and the agents that call you a base url swap on one side an openapi extension on the other outbound your app calls llms keep the openai sdk and point it at your gateway provider routing spend caps and guardrails apply to every call ts keep your existing openai sdk just swap the base url import openai from openai const client new openai baseurl https your org zuplo app v1 apikey process env zuplo_ai_key your zuplo key not openai s const response await client chat completions create model gpt 4o messages role user content summarize our q1 sales data explore the ai gateway ai gateway inbound agents call your api mark openapi operations as mcp tools deploy and agents connect at mcp through the same policies as the rest of your api json paths orders id get operationid getorder summary fetch order by id x zuplo route mcp type resource tickets post operationid createticket summary open a support ticket x zuplo route mcp type tool explore mcp server features mcp servers same gateway same policies both directions value you can measure in the first month lower cost a smaller attack surface faster resolution and new revenue real results not a feature checklist cut runaway cost dynamic rate limiting absorbs traffic spikes before they hit your origin token budgets stop ai overspend with a hard cap not a surprise overage shrink the attack surface auth schema validation and bot controls reject bad traffic before it reaches your systems the same policies across every api model and mcp server prove what s happening every api llm and mcp call is logged and attributed to a consumer then exported to the siem you already run turn traffic into revenue meter price and bill apis and ai by request token or any unit that costs you with no billing infrastructure to build resolve issues faster request level tracing pinpoints the slow hop from client to origin so problems get fixed before they become escalations govern ai for the ciso scoped access audit logs secret masking and prompt injection defense the answers security teams actually ask for teams ship real results on zuplo the move to zuplo from our existing api management vendor was easy taking just over 2 months to switch mission critical systems and we re saving over 70 on costs ryan waites senior director blockdaemon case study customers blockdaemon 90 hardware footprint reduction at scale zuplo gives us the flexibility to scale efficiently ensures security and compliance and reduces operational complexity so we can focus on building new capabilities daryl benzel staff software engineer yext case study customers yext accuweather customers accuweather 1b end users served via zuplo apis we didn t touch a line of code it s just plug and play the results were very surprising in just a couple of hours we had a fully working mcp server miguel madeira cto co founder finsolutia case study customers finsolutia hours to launch an mcp server on regulated apis frequently asked questions what is a unified gateway a unified gateway puts every kind of traffic your business runs api requests from users llm calls from your own applications and mcp tool calls from ai agents behind one programmable policy engine authentication rate limiting spend caps and audit logging are written once and enforced on every api llm and mcp call instead of being split across an api gateway an llm proxy and an mcp experiment on the side what s the difference between an ai gateway and an api gateway an api gateway sits in front of the apis you serve handling authentication rate limits and routing for the requests coming in an ai gateway sits in front of the llm providers your applications call routing traffic across models capping spend per team and applying guardrails to the requests going out with zuplo both run on the same policy engine so the rules that protect your apis also govern your ai traffic what is an mcp gateway an mcp gateway is the control point between ai agents and mcp servers it authenticates agents with oauth controls which tools each user can see and invoke brokers credentials to upstream servers and logs every tool call zuplo s mcp gateway includes a spec compliant oauth authorization server dynamic client registration pkce implementing mcp spec revision 2025 11 25 so you can ship mcp to customers and govern the mcp your teams use from the same gateway can zuplo replace my existing gateway yes and you don t have to do it in one cutover teams have moved off apigee kong and azure api management blockdaemon switched mission critical systems off apigee in just over two months and cut gateway costs by 70 zuplo also works alongside the gateway you already run so most teams start with the new traffic routing llm calls through the ai gateway or publishing an mcp server in front of an existing api and consolidate the rest onto one policy engine route by route on their own schedule what s included in every zuplo plan the mcp gateway ai gateway and developer portal are included in every plan alongside the core api gateway the free plan comes with 100k requests and 1k mcp tool calls per month no credit card required enough to put a real api an llm route and an mcp server into production before you pay anything next steps one gateway for every api llm and mcp call live in minutes free tier includes 100k requests month no credit card no sales call start for free https portal zuplo com signup book a demo talk to an api expert docs ai gateway https zuplo com docs ai gateway introduction mcp gateway https zuplo com docs mcp gateway introduction mcp server https zuplo com docs mcp server introduction