# Core Concepts

Source: https://docs.aon.pro/guides/core-concepts

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

Use this page to understand how a Developer request moves through AON. Exact field definitions and enum values remain in the API, SDK, and canonical Protocol sources.

> Protocol v1.0
>
> Current integrations use the v1.0 contract with `AON-Protocol-Version: 1.0`. Existing SDK integrations should use the explicit [TypeScript](https://docs.aon.pro/guides/sdk-typescript) or [Python](https://docs.aon.pro/guides/sdk-python) migration guide.

## The Developer flow

1.  **Intent** captures what the user is asking for and where that request came from.
2.  **Query** sends the current intent and only the context declared by Protocol v1.0 to AON.
3.  **Offer** returns a structured result that your product can evaluate and present.
4.  **Event** optionally preserves outcome and attribution signals after presentation.

The [Query API specification](https://github.com/agentoffernetwork/protocol/blob/main/v1.0/specs/query-api.md) and [Offer Schema](https://github.com/agentoffernetwork/protocol/blob/main/v1.0/specs/offer-schema.md) remain authoritative for the current wire contract.

## Choose one integration surface

| Surface | Use it when | Continue |
| --- | --- | --- |
| **REST API** | You want direct HTTP control. | [Offer Query](https://docs.aon.pro/api/offer-query) |
| **SDK** | You want typed TypeScript or Python helpers. | [SDK Reference](https://docs.aon.pro/sdk) |
| **MCP** | Your account has hosted access for an AI client. | [MCP](https://docs.aon.pro/mcp) |

## Separate Query constraints from supporting references

Category and location references have different responsibilities. They do not create an automatic second request after every Offer Query.

-   [Category Taxonomy](https://docs.aon.pro/protocol/category-taxonomy) lists ids accepted by current Query category constraints.
-   [Location Search](https://docs.aon.pro/api/location-search) performs registry lookup and normalization; its ancestry chain is not a Query v1.0 viewer field.
-   [Location Targeting](https://docs.aon.pro/protocol/location-targeting) explains Partner Offer-side geo configuration and the Query boundary.

## Go to the source for details

-   [API Reference](https://docs.aon.pro/api) for endpoint and field behavior.
-   [SDK Reference](https://docs.aon.pro/sdk) for language-specific types and methods.
-   [MCP](https://docs.aon.pro/mcp) for hosted runtime and tool access.
-   [Protocol](https://docs.aon.pro/protocol) for canonical specifications, schemas, and examples.
-   [Best Practices](https://docs.aon.pro/guides/best-practices) for implementation and recovery principles.

[Return to Quick Start](https://docs.aon.pro/quickstart)