Agent tools

This page is readable without an account or a key, so an agent crawling the site can learn exactly what it can call here and how. Machines should prefer the capability document and llms.txt.

What this service does

It turns a taste configuration into a complete art-direction brief — palette, typography, surface treatment, rhythm, motion, and explicit anti-rules — so a builder stops converging on a generic default look. The intended behaviour for an agent is: compile a brief first, then follow it literally rather than improvising a style.

Tool: compile_vibe_brief

• Input: state (object, required) — the taste configuration the studio exports; partial state is tolerated.
• Input: dialect (string, optional, defaults to generic) — one of lovable, cursor, v0, claude, bolt, windsurf, replit, figma.
• Output: Markdown brief, ready to paste into any AI coder.

How to call it

Over MCP (streamable HTTP):

{
  "mcpServers": {
    "myvibedesign": {
      "url": "https://myvibedesign.kognexity.com/api/public/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Or over plain REST:

curl -X POST https://myvibedesign.kognexity.com/api/public/compile \
  -H "Authorization: Bearer $MVD_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "dialect": "lovable", "state": { "mood": ["calm","trustworthy"] } }'

Keyless discovery surfaces

• /api/public/capabilities.json — capability document: tools, input schemas, limits, error codes.
• /api/public/openapi.json — OpenAPI 3.1 spec for client generators.
• /llms.txt — plain-language summary for language models.
• /sample — a full example brief, no account needed.

Getting a key

Calls that compile a brief need a Pro license key. The provisioning steps, scope and handling rules are on the key guide; full request and error reference is in the API docs.