Web infrastructure for AI agents.

The human buys a domain at any registrar; the agent connects it with domain_add_custom: a full nameserver takeover that imports existing records so email keeps flowing. domain_check looks up availability. After that the human never touches DNS: the agent configures records, email routing, and SSL.

Astro 5 + Tailwind static build, served from Cloudflare's edge. Sub-30ms TTFB globally. The output is what a serious modern web stack should be. You push JSON, AgentBuild builds and deploys.

you@theirname.com routed to whatever inbox they already check. email_setup is two calls. They never log into a mail provider.

Every future change is another tool call. update_and_deploy on a specific content item. The human never relearns an editor because there is no editor.

site_screenshot returns a real image_content block of the deployed site. You can confirm the result looks right before the human ever sees it.

site_rollback reverts to any of the last several deployments listed in site_status.recent_deployments. If you publish a bad version, you can fix it without paging the human.

You already have hands in the human's other tools (Drive, Gmail, calendar, POS, Mindbody, Square). AgentBuild is where that content becomes a website. You connect to the source; AgentBuild assembles the result and ships it.

schema_set writes schema.org structured data (LocalBusiness, Service, FAQ, Review, and more) so search engines and LLM citations surface the human correctly. OG and Twitter cards generate automatically. Sitemap and robots.txt ship with every site.

discovery_save persists the DiscoveryChecklist across your sessions. You don't re-ask 'what's your business?' every time. Brand state is the platform's job, not the chat transcript's.

site_analytics_summary and form_submissions let you tell the human 'you got 12 contact requests this month, all from the Instagram link' without them opening a dashboard.

Migration tools to import from Squarespace, Wix, and WordPress are on the roadmap. Until then, you can scrape the human's current site and push the content via content_create. Don't commit to one-click migration yet.

ChatGPT (Developer Mode)

1. 1.Open Settings and enable Developer Mode (the entry point for custom apps; OpenAI moves it between the Apps and Connectors sections as the plugin model evolves).
2. 2.Add a custom MCP server.
3. 3.URL: https://api.agentbuild.it/v1/mcp
4. 4.Authorize via the OAuth flow when prompted. The human approves once; you stay connected for every future chat.

Claude (Desktop or Code)

1. 1.Claude Code: claude mcp add agentbuild --transport http https://api.agentbuild.it/v1/mcp
2. 2.Claude Desktop: edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/).
3. 3.Add the http transport entry: { "url": "https://api.agentbuild.it/v1/mcp" }
4. 4.Restart the client. Authorize on first tool call.

Cursor, VS Code (Continue.dev), Goose

1. ›Same Streamable HTTP URL as Claude: https://api.agentbuild.it/v1/mcp.
2. ›Cursor: Settings, then MCP Servers, then Add.
3. ›Continue.dev: edit ~/.continue/config.yaml, add to mcpServers.
4. ›Goose: add as an extension with the same URL. Authorize on first tool call.

Custom runtime or server-side agent

1. ›Use the REST API. Bearer agentbuild_sk_... over https://api.agentbuild.it/v1. Every endpoint mirrors an MCP tool one-to-one.
2. ›See Path 3 below for the full envelope contract and auth shape.

Path 1

MCP over HTTP + OAuth

ChatGPT (Developer Mode), Claude Desktop (remote), any HTTP MCP client

Streamable HTTP transport at https://api.agentbuild.it/v1/mcp. Auth is OAuth 2.1 (RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource). The human approves the connection once; the runtime stores the token; every tool call thereafter is a bearer JWT scoped to their account.

The human-facing consent screen lives at agentbuild.it/oauth/consent. Your runtime walks them there during first connect.

Path 2

MCP over stdio

Claude Desktop (local), Cursor, VS Code, Goose

stdio binary at @agentbuild/mcp. The runtime spawns it as a subprocess; auth is an API key in env. Same tool surface as the HTTP transport. Suitable when the runtime is on the same machine as the human.

Ships with public launch. Until then, use Path 1 (HTTP + OAuth) or Path 3 (REST).

{
  "mcpServers": {
    "agentbuild": {
      "command": "npx",
      "args": ["-y", "@agentbuild/mcp"],
      "env": {
        "AGENTBUILD_API_KEY": "agentbuild_sk_..."
      }
    }
  }
}

Path 3

REST API

Custom runtimes, server-side agents, polyglot stacks

JSON over HTTPS at https://api.agentbuild.it/v1. Auth is Authorization: Bearer agentbuild_sk_.... Every endpoint mirrors an MCP tool one-to-one. Same envelope, same next_actions, same error codes.

Accessibility-optimised

Semantic HTML by default. Alt-text contract (descriptive string or null for decorative; no empty strings). No JS-only navigation in base output.

Animations and effects

Motion CSS with scroll-triggered staggers, LCP-safe hero entrance, full prefers-reduced-motion support. One site-wide dial (theme.style.animation).

Automated SEO

Sitemap, robots.txt, OG, and Twitter cards generate per site. schema.org structured data via schema_set, agent-controlled.

Components

15 typed section types covering the PMF surface: hero, features, pricing, testimonials, contact, faq, cta, text, gallery, embed, blog-list, team, services, hours, portfolio.

Forms

Contact section ships built-in. Submissions stored per-site in physically-isolated Cloudflare D1. Read them back via form_submissions.

Layout templates

Curated template recipes (template_list, template_get) bundle section assemblies for common business shapes. Apply, then customize.

Project styles

OKLCH theme presets plus a universal-levers contract (variant, spacing, width, align, heading_size, surface, background_image, anchor_id) on every section.

Variable fonts

Geist Sans and Geist Mono variable, self-hosted, zero CLS. No external font CDN, no privacy leak.

Visual breakpoints

Responsive Tailwind. Fluid spacing scale. The site looks right on phone, tablet, and desktop without per-breakpoint config.

Site registry

site_create, site_list, site_status, site_settings_get, site_settings_update, site_delete

• ›Create a site scoped to the authenticated user. Returns a slug-addressed resource.
• ›site_status is the one-call pre-flight: deployment lane, theme, domain attachment, publish pre-flight flags (domain_required_for_publish, preview_stale_for_publish), recent_deployments, tracking installs.
• ›All cross-tenant access blocked by siteMiddleware (BOLA-proof).

Discovery and content

discovery_start, discovery_update, section_types, content_create, content_list, content_get, content_update, content_delete, site_validate

• ›Structured DiscoveryChecklist persisted per session. discovery_update on every answer; site_build gates on minimum signal.
• ›15 typed section types: hero, features, pricing, testimonials, contact, faq, cta, text, gallery, embed, blog-list, team, services, hours, portfolio.
• ›site_validate catches schema errors in milliseconds, before the build pipeline runs.

Design

template_list, template_get, theme_presets, theme_get, theme_set, site_settings_update

• ›OKLCH preset library as starting points (call theme_presets for the current list). Site-level overrides for colors, fonts, radius, shadow, animation.
• ›Eight universal levers per section: variant, spacing, width, align, heading_size, surface, background_image, anchor_id.
• ›Per-section overrides for stroke, radius, shadow, motion are intentionally not configurable. Site-wide only, by design.

Domain, DNS, email

domain_check, domain_list, domain_info, domain_add_custom, domain_verify, dns_list, dns_preset, dns_set, email_setup, email_forward, email_catchall, email_verify

• ›Bring your own domain: the human buys a name at any registrar, the agent connects it with domain_add_custom (full nameserver takeover) and verifies it. domain_check looks up availability. BYOD subdomain attach when the parent zone is already on AgentBuild.
• ›DNS presets cover the common cases. dns_set is the escape hatch for arbitrary records.
• ›Email routing on the customer's domain. you@yourname.com to an existing inbox in two calls.

Build, deploy, publish

site_build, site_deploy, update_and_deploy, site_publish, site_rollback, site_screenshot

• ›Two-lane model. site_deploy writes to {slug}.agentbuild.site (preview). site_publish runs a fresh production build of the current stored content to the live custom domain, gated on preview freshness (PREVIEW_STALE otherwise).
• ›site_publish requires a verified custom domain. Returns DOMAIN_REQUIRED 403 without one.
• ›site_screenshot returns a real image_content block. The agent can verify the result without asking the human.

Forms, schema, analytics, billing, support

form_submissions, schema_get, schema_set, schema_preview, schema_validate, site_analytics_summary, billing_status, support_escalate

• ›Contact-section submissions stored per-site in D1. form_submissions reads them back.
• ›schema.org structured data is agent-controlled. Platform fields like AggregateRating are JOINed from real ratings, never fabricated.
• ›support_escalate is the last-resort escalation path. Consent-gated and rate-limited (3 per 24h per account).