Reference

API reference

The whole corpus is public JSON under /v1 — no keys, no rate cards, open cross-origin access. Read the marketing grid, the stage and section grammar, the copy rules, the email grammar, the platform model and the worked case study; validate your own funnel-page outlines against the published schema and grammar.

Base URL: https://marketing.bowtiekreative.com · Machine description: OpenAPI 3.1 · Agent guide: /llms.txt

Endpoints

Method	Path	What it returns
`GET`	`/v1`	This index
`GET`	`/v1/health`	Liveness and corpus counts
`GET`	`/v1/openapi.json`	OpenAPI 3.1 description of this API
`GET`	`/v1/manifest`	Package manifest and inventory
`GET`	`/v1/grid`	The LAKA marketing grid — 8 variables × 4 change levels
`GET`	`/v1/stages`	The six funnel stages
`GET`	`/v1/stages/{id}`	One stage, e.g. homepage, with rules and required sections
`GET`	`/v1/sections`	The page-section grammar
`GET`	`/v1/sections/{id}`	One section type, e.g. hero, with its element contract
`GET`	`/v1/rules`	The copy rules — filter by category, severity or q
`GET`	`/v1/rules/{id}`	One copy rule, e.g. MG-CTA-001
`GET`	`/v1/emails`	The email nurture grammar and archetypes
`GET`	`/v1/platform`	The execution-platform domain model
`GET`	`/v1/example`	The HouseSmart worked case study, structured
`GET`	`/v1/example-outline`	A valid outline of the case-study homepage
`GET`	`/v1/schema`	The JSON Schema for a funnel-page outline
`GET`	`/v1/sources`	The source register and boundaries
`GET`	`/v1/docs`	The case-study documents
`GET`	`/v1/docs/{slug}`	One document, as markdown
`POST`	`/v1/validate`	Validate a funnel-page outline against the grammar

Filtering the rules

The rules list accepts category (seo, hero, cta, structure, voice, honesty, email), severity (must or should) and free-text q:

GET /v1/rules?category=cta&severity=must
GET /v1/rules/MG-CTA-001

Reading the grammar

Stages and sections cross-link: each stage lists its required sections, and each section lists the copy rules that apply to it:

GET /v1/stages/homepage
GET /v1/sections/hero

Validating an outline

POST a funnel-page outline to /v1/validate. It is checked against the published schema and then against the grammar itself — required sections for the declared stage, the hero contract, verb-first CTAs, the problem-before-mechanism ordering, and one primary destination per page. The response reports valid plus a list of errors with JSON paths, and grammar errors name the rule id they enforce.

A minimal outline fragment — see /v1/example-outline for a complete, valid outline

{
  "stage": "homepage",
  "title": "AI Smart Home Consultant for Builders and Homeowners",
  "description": "Plan an intelligent home before technology decisions become expensive.",
  "sections": [
    {
      "type": "hero",
      "eyebrow": "INDEPENDENT HOME INTELLIGENCE CONSULTING",
      "h1": "Plan the Intelligence Before You Build the House.",
      "subhead": "A smart home is not a collection of devices.",
      "primary_cta": {
        "label": "Assess My Project",
        "href": "/assessment"
      }
    }
  ]
}

curl -X POST https://marketing.bowtiekreative.com/v1/validate \
  -H 'content-type: application/json' \
  --data @my-outline.json

Caching & access

Read endpoints are cacheable and served with permissive cross-origin headers. There is no authentication and no usage charge — this is a free public reference.