get_nexus_overviewDiscover the platform, AdTech engineering heritage, revenue engines and AI-native operating model.
AI-native AdTech
Nexus includes a real Model Context Protocol layer, giving compatible AI clients a structured, governed way to understand products, inspect capabilities and assist with solution design.
POST /mcp
→ initialize
← capabilities: tools, resources, prompts
→ tools/list
← get_nexus_overview
← get_product_capabilities
← get_ad_format_guide
← get_operating_capabilities
← recommend_deployment
← get_security_modelA new interface to AdTech
The assistant and MCP server use the same curated Nexus product model. The website helps buyers understand the platform; MCP lets AI clients discover that knowledge through typed tools and resources instead of scraping pages.
get_nexus_overviewDiscover the platform, AdTech engineering heritage, revenue engines and AI-native operating model.
get_product_capabilitiesInspect typed capabilities for Search, feeds, OpenRTB, video or CPA.
get_ad_format_guideExplain what an ad looks like, where it appears, how it is bought, targeted, delivered and measured.
get_operating_capabilitiesResearch traffic quality, feed and bid policy, partner operations, direct campaigns, contextual monetization and custom engineering.
recommend_deploymentMap a business model and channel mix to a phased Nexus deployment.
get_security_modelUnderstand authentication, authorization and infrastructure boundaries.
How AI clients connect
The AI client connects to the Nexus Streamable HTTP endpoint and negotiates MCP capabilities.
It lists typed tools, reads the product catalog resource and can use the solution-discovery prompt.
The client combines verified Nexus context with the customer’s business question.
Public tools are read-only. Privileged operational tools can later be added behind scoped authentication and approval.
Open by design
AI-ready from day one