Build a Request Path

After sending your first request through AISIX, you can use the same pattern for your own applications.

The path starts with the request format your application already sends. AISIX then checks the caller API key, resolves the requested model alias, and uses the configured provider credential to call the upstream model.

Once these pieces are in place, applications can keep calling one stable gateway API while AISIX handles the provider-side configuration behind it.

The request path looks as follows:

In self-hosted gateways, you create the resources locally through the admin API. In managed deployments, you create them in AISIX Cloud and the control plane projects them to the managed gateway.

By the end of this chapter, you will learn how to connect the caller-facing API shape, gateway resources, and provider upstream settings into one working traffic path.