Circle’s agentic-payment stack starts from a powerful premise: autonomous software needs financial infrastructure that works at machine speed.
Circle Gateway Nanopayments supports gas-free USDC payment authorisations as small as $0.000001 and uses batched settlement to avoid paying blockchain gas for every interaction. x402 gives a server a standard way to tell a client that payment is required and gives the client a way to return a signed payment payload. Arc provides an enterprise-grade blockchain environment for internet-native economic activity.
That stack is designed naturally for software agents and internet services.
TLAY’s work begins where HTTP ends.
A physical agent does not only request a digital resource. It measures energy, moves through space, consumes access, interacts over Bluetooth or another local protocol and operates under hardware constraints. Before it can use Circle’s financial infrastructure, someone must convert a physical event into a trustworthy, machine-readable and policy-compliant payment instruction. The September 17 drone-to-power nanapayments showcase demonstrates how the two stacks fit together.
Circle’s infrastructure solves machine-scale finance
Gateway Nanopayments separates payment authorisation from one-transaction-per-payment settlement.
A buyer funds a Gateway Wallet balance. When a seller requests payment, the buyer signs an off-chain EIP-3009 authorisation. The seller or facilitator submits that authorisation to Gateway for verification and settlement. Gateway can then settle net positions in bulk.
This model addresses three requirements of agentic commerce:
- Very small amounts — down to $0.000001 according to Circle’s product documentation.
- High frequency — an agent can sign many payment authorisations without a gas transaction each time.
- Programmable negotiation — x402 communicates price, network, asset and recipient in a machine-readable exchange.
Arc adds the on-chain environment in which settled value, contracts and other economic state can become publicly verifiable and composable.
Physical AI introduces a new edge
The internet payment flow normally begins when a client requests a URL. The physical flow may begin when:
- a drone touches a charging surface;
- a robot enters a work zone;
- a sensor receives a request for one verified reading;
- a vehicle connects to an energy endpoint;
- an edge-compute device accepts a short job.
The payment requirement cannot be created safely until the system knows what resource is being delivered and under what physical conditions. That creates an edge layer with responsibilities that conventional payment middleware does not cover:
- device discovery;
- hardware identity;
- resource metering;
- local session state;
- pricing inputs;
- buyer and seller policy;
- secure signing;
- offline or intermittent-network behaviour;
- proof retention;
- fail-safe service limits.
TLAY’s stack is designed around that edge.
A seven-layer combined architecture
The drone demonstration can be read as a seven-layer architecture.
Layer 1 — Physical resource
The Arkreen eCandle supplies energy. A meter turns the energy interval into a measurable event.
This layer answers: what was delivered?
Layer 2 — Physical-agent identity
The drone and eCandle each have an economic identity associated with device-held signing keys.
This layer answers: which machine requested or authorised the exchange?
Layer 3 — Local negotiation
The devices establish a BLE session. The seller publishes payment requirements in a structure that maps to the relevant x402 and Gateway fields: price, network, asset, recipient and time limits.
x402 itself is an HTTP payment-negotiation standard. TLAY does not redefine it as BLE. TLAY’s edge adapter translates a non-HTTP physical session into payment requirements and signed payloads that can enter an x402-compatible settlement path.
This layer answers: how does an offline-adjacent machine understand the commercial request?
Layer 4 — Device policy and authorisation
The drone checks the request against its local rules: approved token, recipient, session limit, maximum amount and validity.
If the request is acceptable, the device signs an EIP-3009 authorisation using its embedded key. This layer answers: is the machine allowed to pay, and can it prove the decision?
Layer 5 — Proof collection and batching
The eCandle verifies and stores each proof. It groups authorised slices according to time, count and risk policy.
This layer answers: how can thousands of physical micro-events be managed without treating every event as a separate blockchain transaction?
Layer 6 — Circle Gateway settlement
The facilitator or worker submits the compatible payment payload and requirements to Circle Gateway’s x402 settlement path. Gateway verifies and settles the authorisation according to its Nanopayments model.
This layer answers: how does the signed physical-agent instruction become a financially settled event?
Layer 7 — Arc execution and proof
When the seller moves cleared value on-chain, a separate seller-signed intent creates the Arc transaction.
This layer answers: when and where should the economic result become publicly verifiable and composable?
Why this is not “just an IoT integration”
Traditional IoT payment projects often attach a wallet to a device and call the result machine commerce.
That misses the central problem.
A physical machine-payment stack must preserve a reliable connection across three domains:
- Physical truth — a resource was measured.
- Authorisation truth — a particular device agreed to pay under defined policy.
- Financial truth — the instruction was settled and, when relevant, moved into on-chain state.
TLAY’s value is the translation layer across those domains.
The embedded protocol is not only a transport. It carries session, meter and policy context. The proof batch is not only an optimisation. It preserves the relationship between many physical events and the financial settlement rail. The Arc transaction is not a decorative final screen. It is a separate state with a specific meaning.
How the two stacks complement each other
| Machine-commerce requirement | Circle / Arc | TLAY |
|---|---|---|
| Stable programmable value | USDC | Maps physical price and units into USDC requirements |
| Agent-scale payment | Gateway Nanopayments | Creates constrained payment events at the device edge |
| Open payment negotiation | x402 and Gateway payment schemes | Bridges local physical protocols into compatible requirements and payloads |
| Buyer authorisation | EIP-3009 Gateway authorisation | Embedded key, local policy and physical-session binding |
| Efficient settlement | Gateway batching and facilitator APIs | Edge proof validation, aggregation and delivery |
| On-chain economic state | Arc | Seller intent, hardware-to-Arc trigger and proof UI |
| Application domain | Internet and agentic economy | Drones, robotics, energy, sensors, mobility and Physical AI |
The integration is strongest when neither side pretends to replace the other.
Circle and Arc do not need to become hardware-protocol vendors. TLAY does not need to recreate a global stablecoin and settlement network. The combination creates a credible path from a measured physical event to programmable financial infrastructure.
The strategic role for TLAY
For the Circle and Arc ecosystem, TLAY can serve three roles.
Reference implementation partner
TLAY can turn Circle’s agentic-payment primitives into open physical-device reference architectures: buyer, seller, meter, policy, facilitator and Arc proof.
Industry integration partner
Each physical vertical has different hardware and commercial constraints. TLAY can translate the reference stack into energy, robotics, mobility, sensor and edge-compute pilots.
Physical-agent developer platform
Over time, common components can become an SDK and management layer for provisioning identities, defining resources, enforcing policy, inspecting proofs and routing settlement. The September 17 showcase is evidence for the first role and an opening for the second and third.
Proposed next step: a reference stack for Arc
TLAY proposes a joint ecosystem initiative, subject to Circle/Arc approval:
Physical Agent Payment Reference Stack for Arc
The initial release would include:
- an embedded buyer SDK;
- an embedded seller and resource adapter;
- a physical payment-requirements schema;
- BLE and local-protocol reference transports;
- EIP-3009 secure-signing integration;
- Gateway/x402 facilitator adapter;
- batch and exposure policy;
- Arc settlement/mint proof dashboard;
- two-device Quickstart;
- reference pilots for energy, robotics and paid sensor data.
This initiative would give Arc builders a way to move from “an AI agent can pay an API” to “a physical agent can pay another machine for a measured resource.”
A shared roadmap for the physical agentic economy
Circle has built a financial stack for agents to hold value, discover services and transact programmatically. Arc is being built as an Economic OS for internet-native economic activity. TLAY’s thesis is that a meaningful part of that economy will leave the screen.
Agents will have batteries, sensors, motors and physical responsibilities. Their payments will begin with measured events, operate under local constraints and require infrastructure that can bridge edge devices with global financial rails.
The drone show makes that thesis visible. The combined Circle/Arc and TLAY stack makes it buildable.