The endpoint compresses dental-category research and the local advanced-design notes into typed strategy, tokens, components, assets, prompt recipes, and QA gates another AI can fetch before it designs.
const sdk = await fetch("https://your-domain.com/api/design-sdk?view=manifest")
.then((response) => response.json());
const tokens = await fetch("https://your-domain.com/api/design-sdk?view=tokens")
.then((response) => response.json());Contract
The full payload is available, but generation agents should usually start with the manifest and then request tokens, recipes, prompts, or QA gates as separate context packs.
Assistant-oriented usage help and dental intent classification.
Reference placeholder image manifest for AI design rendering.
Small discovery response for agents.
Reusable design tokens and source metadata.
Generation workflows for pages, ads, and audits.
Machine-readable endpoint description.
Inputs
Accessible, local, affordable dental care with many entry points for routine, urgent, denture, implant, aligner, and financing needs.
Premium, specialist-led implant care centered on lasting confidence, customization, digital precision, and consultation conversion.
Use
Agents can combine these recipes with prompt templates and QA gates to generate landing pages, ad systems, and audits with fewer hidden assumptions.
Select brand mode: access uses affordability and location density; premium uses expertise, materials, and lifetime confidence. Build first viewport with explicit service, CTA, phone or center lookup, and one proof element.
Choose one objection to resolve per ad concept. Use concrete action language and avoid medical guarantees.
Check first viewport for actionable CTA and brand/service clarity. Check typography hierarchy and mobile fit.