Websites, apps and distribution

The journey in plain English

The brand’s developers put our conversation interface into an approved place on its website or app. It sends the brand identifier and permitted page context to our service. The service selects the approved persona, retrieves evidence and controls authorised tools; the interface carries text or voice back to the visitor. Provider credentials stay on the server. The present voice endpoint is deliberately local-only: installing a widget elsewhere requires a production service and access controls first.

Guinness can help a visitor plan a Storehouse afternoon or explore the story behind an exhibit, then hand off to existing booking. Pre can support a Nike shopping question, an athlete’s dream, or a Run Club conversation using explicitly permitted running context. Native apps need their own audio, permissions and lifecycle integration. We cannot insert ourselves into Nike’s app remotely.

MCP provides a common way for compatible software to use resources and tools. It does not supply an audience or ensure a host will reproduce our personality. OpenAI now documents a limited Sponsored Agent test, but our access, technical compatibility, partnerships and any platform revenue share remain unconfirmed. The public format is distinct from the original ChatGPT thread; our local Realtime voice demo is not that format. See published specifications and gaps. See the website and app integration plan for placements, responsibilities and implementation steps.

Persona, plugin, MCP and the brand’s systems

The persona is a versioned identity and evidence package, supported by an inference runtime. It can appear through an owned website/app adapter or a supported brand plugin. The plugin packages workflow instructions and tool connections; MCP exposes scoped capabilities on an integration server. Brand identity, run records and checkout still depend on the client’s authorised systems.

The GPT Agency creation plugin serves brand teams. A consumer-facing brand plugin serves people meeting Pre or Arthur. They are distinct products and permission boundaries. Neither a plugin nor MCP guarantees a host will reproduce the exact voice, retain memory or expose Sponsored Agent capabilities.

A Nike journey could invite membership, open the NRC app-store listing, connect authorised run data, explain a suitable product and hand off a prepared basket to Nike checkout. Membership creation, app installation, account access and Instagram follows require their respective provider’s support and the user’s own confirmation; a link is not proof of completion.

See Personality and agentic capabilities for the researched logistics, source notes and CEM/Gauntlet controls.