# AON Quick Start

Source: https://docs.aon.pro/quickstart

> Derived from the same AON Docs release as the source page.

Run one bounded Offer Query, then choose the HTTP, SDK, or provisioned Hosted MCP path that fits your product. The current public contract remains the source of truth for every path.

Protocol v1.0 · Updated September 2, 2026

[Run the Public Test Sandbox](https://docs.aon.pro/quickstart/public-test-sandbox)

No application identity is required. The Sandbox returns a fixed, non-billable Query response.

Before live traffic

## Four terms you will see next

Learn these after the Sandbox, when you are ready to configure your own integration.

Application

Your live integration in Developer Portal. A serviceable Application owns the Live Key used by that integration.

Placement

Optional Query routing context for where an Offer appears. It is recommended for live configuration. Live Key issuance is independent of this routing context.

Live Key

An issued credential held by a serviceable Application and used to authenticate an enabled live route.

Offer

The structured result returned by an AON Query for your product to evaluate and display.

Query input

## `intent.content[].text`

Use one line containing 1 to 200 characters. The API does not promise to truncate or clean longer input for you.

## Developer implementation path

REST and SDK are the standard implementation paths after the Sandbox. Choose Hosted MCP only when access is already provisioned for the account.

For the conditional route, open [Hosted MCP Connection Setup](https://docs.aon.pro/mcp/quickstart) only when an issued API key can authenticate `/v1/mcp`.

Developer integration

## Choose one implementation route

Start with HTTP or an SDK. Hosted MCP connection details are available only when your issued API key can authenticate the endpoint.

HTTP

### Build with HTTP

Use the HTTP API when your service needs direct control over requests and responses.

[Read the first API call](https://docs.aon.pro/quickstart/first-api-call)

SDK

### Build with an SDK

Use a TypeScript or Python client library when it fits your application.

[Set up an SDK](https://docs.aon.pro/quickstart/sdk-setup)

Hosted MCP

### MCP connection setup

Use this conditional path only for accounts with provisioned access and an issued API key that can authenticate /v1/mcp; it is not part of the default Developer flow.

[Open Connection Setup](https://docs.aon.pro/mcp/quickstart)

Each guide covers the setup, credentials, and next step for a developer implementation path.

## Local checks are not live access

The public contract and local SDK mock verification validate integration shape. They do not by themselves provision credentials, account access, or production availability.

## Sandbox completion is not production completion

The Sandbox completes one bounded Query and contract check only. Continue with REST or an SDK for your own integration, or use the conditional MCP route only with an issued key that can authenticate its endpoint.

## Implementation requirements

Use Node.js 20+ or Python 3.11+ for the documented SDK baselines. Use the [API Reference](https://docs.aon.pro/api) and [SDK Reference](https://docs.aon.pro/sdk) for implementation details; access requirements live with the service and account setup for each path.

## Resources for AI coding agents

[Open `/agent.md` (raw Markdown)](https://docs.aon.pro/agent.md) when an AI coding agent needs the current Protocol, Schema, and Examples source links behind these guides.