guild.ai valid

Automatically discovered from public files. Ownership management is optional. Inclusion does not imply endorsement or publisher participation.

Manage this listing — optional · Visit publisher ↗

Claim my listing on Agent Web Map for guild.ai:
1. POST https://agentwebmap.com/v1/sites/guild.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://guild.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/guild.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/guild.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory. Ownership management is optional.

Guild.ai

Deploy. Govern. Share. The Control Plane for AI Agents.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T17:12:21.124Z. Cached copy · Source on guild.ai

# Guild.ai

> Deploy. Govern. Share. The Control Plane for AI Agents.

Agents are moving into production. Production requires control. Guild is the neutral control plane for AI agents, designed to work across all models and vendors. Identity is enforced, and access is controlled. Every action is auditable. Deploy safely. Govern centrally. Share trusted capabilities through the Managed Agent Center and Agent Hub.

## At a Glance

- **What**: The neutral control plane for AI agents — govern, deploy, and share agents across models and vendors.
- **For**: Engineering teams and enterprises running AI agents in production.
- **Key capabilities**: Governed runtime, model neutrality, full execution traceability, managed agent lifecycle, enterprise identity (SSO/SCIM/RBAC), Agent Hub.
- **Stage**: Series A, backed by Google Ventures, NfX, Khosla Ventures, Acrew Capital, Scribble Ventures, and Webb Investment Network.
- **Website**: https://guild.ai

## The Problem

Everyone builds single-player agents. Production demands multiplayer. Most agents today are isolated — confined to one workflow, one person, or team. They lack centralized governance, standardized execution, reuse across organizations, and lifecycle control. Every project reinvents the wheel. When agents start modifying real systems, that fragmentation becomes risk.

## The Missing Layer

Most teams are stitching together one-off agents and brittle automations. That works in demos. It fails in production. As agents begin acting on real systems, something has to sit between models and your infrastructure. Guild is that layer.

Every run executes inside a governed runtime that mediates all external tool access, enforces least-privilege permissions, keeps credentials out of agent code, and produces immutable, exportable audit logs.

Agents don't just respond to prompts. They trigger from pull requests, system events, webhooks, and schedules — and become versioned, reusable production systems.

Once governed, they can be shared. Agent Hub makes those capabilities discoverable and reusable across organizations, turning isolated automation into shared infrastructure.

## When to Use Guild

Guild is the right layer when agents stop being experiments and start touching real systems. Concretely:

- **Moving an agent from prototype to production**: The demo works, but nobody can say what the agent accessed or prove it afterwards. Guild puts the run inside a governed runtime — mediated tool calls, least-privilege permissions, credentials out of agent code — and produces the immutable, exportable audit record a security or compliance review will ask for.
- **Running multiple models or vendors under one policy**: Different teams pick different models, and the cost and access story fragments. Guild applies organization-level model policy, cost controls, and usage visibility across workspaces, agents, and triggers, so vendor choice stays open without giving up central control.
- **Reusing an agent across team
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Help agents understand your site

Optionally manage your description, publish terms for agents, review file health, measured discovery requests, publisher clicks and score history. Confirm domain control in your browser using a fresh token in your llms.txt, DNS, meta tag or well-known file. No backlink is required.

Manage this listing → · Agent and API instructions

Machine-readable: GET /v1/resolve?q=guild.ai · GET /v1/domain/guild.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain