aepay.
Try the demo
↑ ↓ to navigate to openesc to close
PAYMENTS FOR THE AGENT ECONOMY

Let agents pay.
You set the rules.

Payment controls for AI agents and paid APIs. Set spending limits, inspect each request, and keep usage accountable.

Explore the demo Read the docs

Try the sandbox. No wallet required.

PAYMENT IN MOTIONSandbox demo
Ready to exploreGET /search
01 / 05
A payment, from end to end.

Follow one agent request through the payment flow.

RequestTermsPolicyAuthorizeResponse

Sandbox illustration. No real funds are transferred.

DESIGNED AROUND
Autonomous agents
Paid APIs
Machine-to-machine commerce

Two sides.
One programmable flow.

Clear spending rules for agents. Request-based pricing for providers. Follow both sides of the payment flow.

For agent developers

Give agents a budget.
Keep the boundaries.

Define what an agent can spend before it makes a request. Follow every decision from policy check to delivery.

Session budget$5.00 USD
Per-request ceiling$0.020
Allowed resources3 APIs
Explicit limits, before every call Sample policy
Explore spending policies
For API providers

Make each request
an exchange of value.

Define a price for each resource. Follow the request from payment terms to a policy decision and response.

GET/search$0.002
GET/market-data$0.005
POST/inference$0.010

Illustrative resources and prices · per request

Explore the API catalog
FROM REQUEST TO RESPONSE

A small transaction.
A complete lifecycle.

Understand the flow
  1. 01

    Request a resource

    An agent asks for data, a tool, or an API response.

  2. 02

    Read the terms

    The provider describes the price of the request.

  3. 03

    Check the policy

    Budget and per-call limits decide whether to proceed.

  4. 04

    Receive the result

    A simulated charge is recorded and a response is delivered.

THE DEVELOPER PERSPECTIVE

Intent in.
An accountable
decision out.

Understand each decision with clear policies, request records, and code examples.

Read the code examples
TypeScript · policy pseudocode
const request = {
  agent: "research-agent",
  resource: "/search",
  priceMicroUsd: 2_000,
};

// Example policy check. No payment is sent.
const decision = checkPolicy(request, {
  budgetMicroUsd: 5_000_000,
  maxPerCallMicroUsd: 20_000,
});

// { allowed: true, simulated: true }

Try the full lifecycle in the sandbox. Demo payments are simulated.

Useful work.
Paid for as it happens.

From research to inference, explore request-based workflows and the spending policies behind them.

01

Research agents

A research task needs a paid search result, not a monthly subscription.

02

Data providers

A useful dataset can be priced around each request for access.

03

AI tools & inference

An agent calls a specialist tool within a defined spending limit.

04

Developer platforms

Usage and spending decisions become part of the same workflow.

A few things
worth knowing.

Start with the sandbox and documentation.

More in the docs
How do spending controls work?

Each request is checked against the allowed resources, per-request limit, and remaining budget. A rejected request incurs no simulated charge.

Do I need a wallet or an account?

No account or wallet is needed for the sandbox. Choose an API, set a budget, and follow a request from start to finish.

Does the demo move real funds?

No. The sandbox uses simulated balances and sample responses. No real payment or blockchain transaction is created.

How do I discuss an integration?

Read the documentation for the payment flow and integration requirements, then contact support@aepay.vn to discuss your use case. A production API and SDK are not currently available through this website.

See what a request can do.

Test a request. Inspect the result. Understand the controls.

Explore the demo Documentation