Execution surfaces
One decision, many surfaces.
AgentKit keeps the commercial decision stable while adapting the presentation to each surface.
Execution surfaces are where approved plans become visible to the world. Each surface owns its own metadata, disclosure rules, media requirements, and upload method, but the core decision remains the same.
Configured surfaces
Website
Public destination pages, landing pages, and orientation layers.
Google Business Profile
Profile updates, posts, and local trust signals.
Founder-oriented distribution and commercial proof.
CRM / Email / Chat
Structured intake, routing, and follow-through.
How the connector layer works
- Each connector declares its capabilities instead of the engine hard-coding platform logic.
- Metadata requirements, disclosure rules, and media constraints are validated before execution.
- Failed destinations can be retried without re-running the whole campaign.
Why this matters
- New platforms can be added without changing the core engine.
- Provider-specific presentation never replaces canonical truth.
- Operators see one continuous workflow instead of repeated interruptions.
Surface requirements
Canonical URLs, metadata, media, and redirect strategy.
Caption contracts, hashtag rules, and disclosure language.
Structured intake and reliable routing to the right owner.
Fast triage without losing the commercial context.
Primary CTA
Execution should adapt to the surface, not the other way around.
AgentKit keeps the decision canonical and lets each platform declare its own contract.