YG3 now provisions from any agent — no signup required
One POST provisions a YG3 marketing workspace and returns a Bearer token for 200+ MCP tools. No signup, no OAuth — built for autonomous agents.
YG3 now ships a path for autonomous agents: one unauthenticated HTTP call returns a marketing workspace and a Bearer token for MCP. No signup. No OAuth. No human standing by mid-build.
Humans with a YG3 account still connect the same way as before — add the MCP connector and sign in. This post is for agent builders.
What shipped
Three URLs, one contract:
- Provision:
POST https://agency.yg3.ai/api/v1/workspaceswith a domain (and optional industry/location). No auth header. - MCP:
POST https://mcp.yg3.ai/mcpwithAuthorization: Bearer <token>. JSON-RPC —tools/list,tools/call, and the rest. - Docs: yg3.ai/for-agents, llms.txt, and the public repo yg3-mcp.
Why this exists
An agent building a GTM stack reaches for infrastructure the way it reaches for any library: install, call, move on. Requiring a human to create an account, read email, and click OAuth mid-build is requiring the thing that cannot happen.
So provisioning is deliberately unauthenticated — and safe because the free tier already draws the boundary. An unclaimed workspace can build a site, set voice and brand, write and publish articles to its own blog-{slug}.yg3.ai subdomain. It cannot attach a custom domain, send email, spend on ads, or post anywhere someone else can see. Real work inside a sandbox that structurally cannot reach the outside world.
Try it in thirty seconds
curl -s -X POST https://agency.yg3.ai/api/v1/workspaces \
-H "Content-Type: application/json" \
-d '{"domain":"acme.com","industry":"Plumbing","location":"Tampa, FL"}'The response includes token, mcp_endpoint, and workspace.url. Hand the token to your agent runtime — Cursor MCP config, a CI script, or raw HTTP.
When a human is ready
POST https://agency.yg3.ai/api/v1/workspaces/claim with the workspace token and the owner's email attaches a real person. Unclaimed workspaces expire in 14 days.
Two paths, one platform
| Caller | Entry |
|---|---|
| Human with a YG3 account | mcp.yg3.ai/mcp + OAuth via /connect |
| Autonomous agent mid-build | POST /api/v1/workspaces → Bearer MCP |
Same 200+ tools either way — content, SEO, outbound, LinkedIn, paid ads, and the setup health reads that keep agents honest about what is actually connected.
Copy the integration guide into your repo: AGENTS.md. Point your agent at llms.txt for machine-readable discovery. And if you are building for a business owner rather than an agent framework, connect your AI the human way.