# Aeeron ## Aeeron Aeeron is a Solana-native execution layer for agents that need to pay before they can act. Instead of treating payment as a separate checkout step, Aeeron makes it part of the API contract itself. An agent can request a priced action, receive an explicit payment requirement, satisfy that requirement through x402, and continue into execution without leaving the same control loop. ### What Aeeron enables Aeeron is designed for actions that already have a clear economic boundary but are still painful to automate in practice. That includes company formation, infrastructure provisioning, domain and storage purchases, and paid agent-to-agent service exchange. The important detail is not the category of action. The important detail is that the action has a price, a provider, and a meaningful execution result that an agent needs to track after payment clears. ### Why Aeeron is strong Aeeron is useful because it gives builders a single place to enforce the parts of agent execution that usually end up fragmented across internal tools, provider-specific billing code, approval systems, and ad hoc retry logic. Pricing, spend approval, payment proof, execution state, and provider output all live inside one request model. That makes autonomous execution more realistic because the agent does not need a different payment integration for every paid service it touches, and it makes supervised execution more realistic because every economic step is visible and auditable. The Solana-native part matters because machine-driven flows need settlement that is fast, explicit, and programmable. The x402 part matters because the payment requirement becomes a formal response, not an implicit assumption. Together, those choices make Aeeron a better fit for agent runtimes than traditional APIs that expect a human to handle the economic step somewhere outside the system. ### Good fit Aeeron fits agent systems that need to move beyond recommendation into execution. If an agent can stop at analysis, a normal API integration is usually enough. If the agent needs to spend money, provision external resources, purchase output from another service, or complete a business operation with a real financial consequence, Aeeron gives that workflow a cleaner and safer runtime boundary. ### Documentation map Read [Product overview](/aeeron-docs/product-overview.md) for the product framing, [Why Aeeron](/aeeron-docs/why-aeeron.md) for the strategic fit, and [Getting started](/aeeron-docs/getting-started.md) if you want the first end-to-end flow. For implementation details, continue with [How Aeeron works](/aeeron-docs/how-aeeron-works.md), [Authentication and x402](/aeeron-docs/authentication-and-x402.md), [API conventions](/aeeron-docs/api-conventions.md), and [Integrate an agent](/aeeron-docs/integrate-an-agent.md). The executable API surface lives in [Payment-backed actions](/aeeron-docs/payment-backed-actions.md), [API endpoints](/aeeron-docs/api-endpoints.md), [Code examples](/aeeron-docs/code-examples.md), [Errors and idempotency](/aeeron-docs/errors-and-idempotency.md), and [Async jobs and webhooks](/aeeron-docs/async-jobs-and-webhooks.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/aeeron.md?ask= ``` 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.