# Product overview

## Product overview

Aeeron turns paid actions into a clean agent API.\
It lets an agent price, pay, execute, and track work in one flow.

{% hint style="success" %}
**Core idea:** Aeeron makes the paid step part of the runtime.\
It does not leave money, approval, or provider state outside the system.
{% endhint %}

### At a glance

```
Intent → Quote → x402 payment requirement → Payment proof → Execution → Result
```

* **The agent** decides what to do.
* **Aeeron** prices and gates the action.
* **The provider** performs the real work.

### What Aeeron does

Aeeron exposes payable operations as agent-callable primitives.\
The request does not jump straight into provider execution.

It follows a fixed lifecycle:

{% stepper %}
{% step %}

### 1. Quote the action

The agent sends intent, input, and budget.
{% endstep %}

{% step %}

### 2. Gate the action

Aeeron returns price and payment requirements.
{% endstep %}

{% step %}

### 3. Execute the action

The provider call starts only after payment is valid.
{% endstep %}

{% step %}

### 4. Track the result

The agent gets a durable execution record.
{% endstep %}
{% endstepper %}

### Why it matters

The value is not only speed.\
The value is clear separation of concerns.

{% columns %}
{% column %}

#### The agent owns

* reasoning
* policy
* budget decisions
  {% endcolumn %}

{% column %}

#### Aeeron owns

* quoting
* payment gating
* execution tracking
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
**Main idea:** reasoning and spending stay connected, but not mixed.
{% endhint %}

### Core strengths

Aeeron is strongest when one integration must cover many paid workflows.

```
Reusable runtime value

Infrastructure      ██████████
Business actions    █████████
Agent services      ██████████
Auditability        ██████████
Retry safety        █████████
```

* **x402** keeps payment explicit.
* **Solana-native settlement** keeps the flow fast and programmable.
* **Execution records** keep the result traceable.

### Operating model

Aeeron works best when spending is treated as policy.

```
Budget set     ✓
Quote checked  ✓
Payment gated  ✓
Execution run  ✓
Result tracked ✓
```

That loop works for autonomous actions.\
It also works for reviewed actions.

### What agents can do through Aeeron

The first use cases are easy to understand:

* **Create a company**
* **Provision servers**
* **Buy another agent service**

The same model also fits:

* domain registration
* storage purchase
* compliance workflows

### Who Aeeron is for

Aeeron is for teams building agents that act in real systems.\
If a workflow depends on money, Aeeron gives that spend a formal runtime.

{% hint style="warning" %}
If payment happens outside the control loop, automation becomes harder to trust.
{% endhint %}

### Start here

* Read [How Aeeron works](/aeeron-docs/how-aeeron-works.md) for the system model.
* Read [Getting started](/aeeron-docs/getting-started.md) for the first live flow.
* Read [Why Aeeron](/aeeron-docs/why-aeeron.md) for the product case.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aeeron.gitbook.io/aeeron-docs/product-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.