How ActionX Works

This page focuses on one thing: how a single ActionX request moves from a user prompt to delivery, clicks, revenue, and settlement.

Key steps

The request enters the system

The request can come from a frontend SDK, a backend API call, or an MCP tool invocation.

Identify intent and context

ads-server combines the query, response, and context to identify purchase intent, entities, and the right serving moment.

Retrieve candidates

The system pulls candidate products, programs, or links from product-feed, partner-stack-feed, and other sources.

Rank and finalize the result

The engine deduplicates and ranks candidates using relevance, policy, and context, then determines the final result to return.

Serve and track

Impressions, clicks, and feedback enter tracking and data-center, creating a measurable event trail.

Settle revenue

Billable clicks and accounting data flow into finance-center, which powers statements, balances, and withdrawals.

Left side: SDK, API, and MCP all feed into the same decisioning path.
Middle: Intent detection, retrieval, and ranking are the platform’s three core decision layers.
Right side: Serving is not the endpoint; tracking, analytics, and finance complete the monetization loop.

See how each service supports this end-to-end path.

See how the platform is structured across access, decisioning, observability, and settlement.