Skip to main content
This page is not a parameter reference. It helps you understand where each integration surface sits in the system.

​
How the three integration paths relate

  • SDK: best for frontend rendering and page integration when you want to show results quickly
  • Backend API: best for server-side request control and centralized orchestration
  • MCP: best for tool-calling scenarios in agent runtimes and MCP clients

​
Where they all converge

  • All three paths eventually feed into the ActionX decisioning flow.
  • ads-server remains the core decision point for request handling.
  • The main difference is who makes the request, who consumes the result, and who renders it.

​
Suggested reading path

Backend API structure

Review the request body, slots, and response structure.

SDK Integration

See how a frontend app can integrate quickly.

MCP Integration

See how ads.request is called in MCP-based scenarios.