Gemini Enterprise Prebuilt Agents: Garden & Marketplace

You don't actually want to build an agent. You want the outcome the agent produces — invoices processed, code modernized, research summarized — and building one from scratch is just the toll you've been paying to get there. The interesting move Google made with Gemini Enterprise is putting a "don't build it, take one off the shelf" option right next to the build tools.

If you're new to the platform itself, start with what Gemini Enterprise is. This piece is about the part that should change how you plan: the prebuilt-agent supply. There are two distinct shelves, and knowing which one you're standing in front of matters more than any single agent on it.

The two shelves: Agent Garden vs. the Agent Marketplace

These get blurred together constantly, so pin the difference down first.

Agent Garden is the in-platform library Google ships. Think samples and templates for common patterns — a retrieval-augmented Q&A agent, task-shaped starters for things like document and invoice work — with the logic pre-wired and, importantly, source you can get at and customize. It's not a store. It's a jumpstart. You take a template, point it at your data and tools, change what you need, and deploy it as your agent.

The Agent Marketplace is the partner channel. This is where third parties — the usual enterprise names plus a wave of startups — list agents you procure and plug in. These surface inside the platform's agent gallery, so employees can discover a partner agent in the same place they'd find an internally built one. You're not forking source here. You're adopting someone else's product and wiring it in.

The mental model: Garden is a recipe, Marketplace is takeout. One you finish cooking yourself; the other arrives done, made by someone else's kitchen.

How marketplace agents actually attach

This is the detail people skip, and it's the one that matters for security review.

Partner agents typically connect over an agent-to-agent protocol rather than living entirely inside your environment. Practically, an admin adds the agent from the marketplace, reviews its details, supplies authentication, and registers it. From then on your agents (and your people) can call it — but some of what it does may run on the partner's side, not yours.

Governance is built around that reality. Administrators control gallery visibility — you can choose to show only agents you've already procured, or surface everything for discovery — and there's an access-request flow so users can ask for an agent and a human approves it. Adding and managing these requires real admin roles, not a self-serve toggle any employee can flip.

So before a partner agent is "available," someone with authority procured it, authenticated it, and decided who gets to see it. That's the right shape. Just don't assume it happened by default.

When to shop vs. when to build

Here's the part you came for.

Reach for a prebuilt agent when

• The job is generic to your industry, not your company. Invoice processing, code modernization, standard research workflows — if a thousand companies need the same thing, someone has already templated it. Building your own is reinventing a wheel that ships with the platform.
• You want to learn the platform fast. Even if you end up building custom, deploying a Garden sample teaches you the deploy/debug/preview loop with a known-good agent. Start there, then diverge.
• A partner already owns the integration. If a marketplace agent is built and maintained by the vendor whose system you're automating against, that maintenance burden staying on their side is a real, recurring win.

Build your own when

• The agent is your edge. If the workflow is specific to how your company operates — your data, your rules, your sequence — a generic template will fight you, and a partner agent will only ever be as good as its lowest-common-denominator design.
• The data is sensitive enough that you want every step on your side. A Garden template you deploy and own keeps the logic in your environment. That's a cleaner story for a security team than an external partner agent.
• You need to change the internals, not just the settings. Marketplace agents you configure; you don't rewrite them. The day you need behavior the vendor didn't expose is the day "shop" turns into "rebuild anyway."

The honest middle path most teams land on: start in the Garden, graduate to custom. Take a sample to learn the shape of a working agent, fork it, and grow your own from there. Reserve the Marketplace for the boundaries of your business — the systems you integrate with but don't want to own.

What's easy to get wrong

A few traps worth naming before you go shopping.

"Prebuilt" still needs grounding. A template Q&A agent is empty until it's pointed at your knowledge and tools. The agent is the easy 20%; connecting it to your data and getting the answers right is the other 80%. Shopping doesn't skip that part.

A marketplace agent is a vendor relationship. You're not buying a file, you're adopting an ongoing dependency someone else patches, prices, and can eventually deprecate. Treat the listing like any other third-party software decision, because it is one.

Don't let the gallery become a junk drawer. The visibility controls exist for a reason. An employee-facing gallery stuffed with dozens of half-vetted partner agents is worse than three good ones. Curate it like you'd curate an app store you're responsible for.

The take

Gemini Enterprise's real pitch isn't "we'll help you build agents." It's "you might not have to." The Agent Garden lets you start from working samples instead of a blank file, and the Agent Marketplace lets you rent capability you'd be foolish to build yourself.

Use both as defaults to avoid work — shop first, build only what's genuinely yours. The teams that win the next year won't be the ones who hand-coded the most agents. They'll be the ones who knew which agents were never worth coding at all.

Names and specifics on this platform are moving fast right now; if a label here doesn't match what you see in the console, the console is right — check the official docs.