Skip to main content
Gateway gives applications a shared, controlled way to use AI models. It checks which model offerings can meet a request, manages the permitted execution attempts and keeps a reliable record of what happened. The application still decides what the answer means for its work. A model producing an answer is not the same as a task being accepted, a user receiving it or a payment being settled. This guide explains that separation, starting with familiar situations and then following the architecture behind them. You do not need to know AccelMars’s internal project names to begin.

Why Gateway exists

See the problems that appear when every application manages AI calls differently.

Follow one request

Walk from an application’s question to an answer, including the points where execution must stop.

Explore the architecture

Meet the planner, execution core, provider adapters and evidence store.

Understand the evidence

Separate the selected design from dated local tests and unverified deployment claims.

​
Three questions to keep separate

May this request run? The request needs an authorized caller, suitable approved model capabilities and permission to send the relevant data to the selected destination. What happened when it ran? Gateway tracks the original request and each physical provider attempt. It distinguishes a confirmed result from an outcome that cannot yet be established. Did the surrounding work succeed? The application owns its result storage and business decisions. Other components own financial effects. Gateway’s execution records inform those decisions; they do not replace them. This is a simplified view of responsibilities, not a claim that every box is a separate server. The request journeys explain the additional checks for streaming, failure and lost confirmations.

​
A guide, not a new design contract

You are reading Reader Edition 1.1, based on Gateway’s Final Design 1.0. The implementation evidence used here is dated 12 October 2026. A newer publication date does not turn that evidence into a live service check. The engineering collection remains the authority for exact contracts. This guide adds explanation and clearly identified examples without changing those contracts. Start with the reading paths, or consult About this edition for the scope and update policy.