# Payment-backed actions

## Payment-backed actions

Aeeron turns paid external operations into agent-callable actions with explicit economic state. That is the central product shift. The agent does not stop at analysis and hand off the expensive part to a human. It can move from intent into action when the action has a price, a payment requirement, and a provider-backed result that can be tracked after execution begins.

### Common action types

#### Create companies

Company formation is a good example because it combines price sensitivity, provider orchestration, and long-running status. An agent may need to choose jurisdiction, entity type, registered agent options, or document delivery preferences. Aeeron gives that workflow a proper quote and execution model so the system can authorize the spend, launch the formation process, and track documents or status updates as they become available.

#### Pay for servers

Infrastructure spend is another natural fit because the economic event is often what turns planning into action. An agent may determine that it needs more compute, a GPU-capable instance, or a short-lived environment for a follow-on job. Aeeron lets the agent price that requirement, fund it through the same control loop, and receive a tracked execution instead of burying provider billing logic inside a custom tool.

#### Buy agent services

Paid agent services matter because they make multi-agent systems economically explicit. One agent can outsource research, synthesis, compliance work, or operational tasks to another service without losing budget discipline. Payment, delivery, and execution tracking remain attached to the same system record, which is what makes multi-agent coordination practical outside toy environments.

### Additional action classes

The same action model extends to domain registration, storage purchase, recurring server renewals, external research tasks, and compliance-oriented filing workflows. These categories look different on the surface, but they share the same execution pattern: a paid operation begins with a price decision and ends with a provider result that the agent needs to consume or act on later.

### Example action payload

```json
{
  "action": "agent-services.purchase",
  "input": {
    "serviceId": "svc_due-diligence-v2",
    "task": "Compare three GPU providers for cost and delivery speed.",
    "deliveryMode": "json"
  },
  "budget": {
    "amount": "45.00",
    "currency": "USDC"
  }
}
```

### Why this matters

Most agent systems stop at recommendation because recommendation is cheap and execution is operationally difficult. Aeeron pushes that boundary by giving the agent a runtime for the paid step itself. Once the pricing and payment requirement are formalized, the system can do more than say what should happen next. It can actually trigger the paid operation that makes the workflow real.

### Product strengths in these workflows

The strength of this model is not only breadth. One integration can cover many payable actions, but the deeper benefit is consistency. Payment is native to the execution path, third-party services become easier to compose, and the same reconciliation model can be reused across very different providers. Solana-based settlement helps keep the machine-driven path fast, but the larger win is that the economic and operational state stay visible together.

### Expanding beyond the first use cases

The Aeeron model applies to any workflow that has a clear price and a callable interface. That makes it broader than the initial examples. If a service can describe what it costs and what it returns, it can usually fit the same quote, payment, execution, and reconciliation lifecycle.

### Related pages

For the concrete API surface, read [API endpoints](/aeeron-docs/api-endpoints.md). For end-to-end request examples, continue with [Code examples](/aeeron-docs/code-examples.md).


---

# 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/payment-backed-actions.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.