Webbie Page Generator API

POST /api/webbie/page $0.02 per call USDC on Base · x402

Webbie page generator: site name, headline, tagline, hero images, content sections, nav, colors — returns a finished responsive standalone HTML page. Three templates (horizon, split, editorial); the seed deterministically picks template + fonts + accent, so reusing it across calls builds a consistent multi-page site. Nav loads from an editable nav.json at view-time. No AI — deterministic templating.

Parameters

Name	In		Description
`site_name`	body	required	Brand/site name (required)
`headline`	body		Hero headline
`page_name`	body		'home' = index.html (default), or e.g. 'about'
`seed`	body		Reuse the same seed on every call for one consistent site style
`template`	body		horizon, split, or editorial; omit to let the seed choose
`title`	body		Browser/SEO title
`caption`	body		Kicker above the headline
`tagline`	body		Supporting line + meta description
`hero_images`	body		First = hero, extras = gallery
`logo_url`	body		Nav logo image URL
`logo`	body		Auto-generate mark: {query, colors, shape}
`colors`	body		1-2 accents, hex or CSS names
`cta`	body		{text, href}
`content`	body		Sections: [{heading, body}]
`nav`	body		[{label, href}] — echoed as nav_json
`footer`	body		Footer text

Example request

curl -X POST "https://api.webbersites.com/api/webbie/page" \
  -H "Content-Type: application/json" \
  -d '{"site_name":"Northwind","headline":"Data for autonomous agents","seed":"nw-2026","template":"horizon","hero_image":"https://example.com/hero.jpg","colors":["#ff6b35"],"cta":{"text":"Get started","href":"docs.html"}}'
# first call returns 402 + payment requirements; an x402 client pays and retries automatically

Example response

{
    "seed": "nw-2026",
    "template": "horizon",
    "filename": "index.html",
    "html": "<!DOCTYPE html>…",
    "nav_json": {
        "links": []
    }
}

MCP tool: post_webbie_page — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.

How payment works

There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.