Protocol Engineering Layer

Technology & System Architecture

Apraxus combines a developer API, policy engine, payment execution layer, EVM infrastructure, and SDK to provide programmable infrastructure for autonomous software. Current implementation and future architecture are clearly separated below.

Current Implementation Surface

Repository-backed capabilities currently implemented for development and testnet use

SHIPPED

Developer InterfaceAPI v1 + TypeScript SDKIntent and sandbox workflows

Policy LayerPayment Policy EngineTransaction + daily limits

Execution LayerWallet-Signed APXSReceipt-confirmed testnet execution

EVM InfrastructureEVM + Uniswap v4APXS / WETH testnet infrastructure

Full Architectural Stack

Repository-backed implementation surface

Developer SDK & API v1

SHIPPED

TypeScript client for health, payment intents, quotes, execution intents, and sandbox simulation.

lib/sdk/*

Policy Engine

SHIPPED

Validates payment amount, per-transaction limits, daily limits, and destination address validity before execution.

lib/policy/engine.ts

Execution Lifecycle

SHIPPED

Tracks submitted, confirmed, reverted, and failed execution states with transaction receipts.

lib/execution/*

APXS Payment Engine

SHIPPED

Executes ERC-20 APXS transfers through a connected wallet and waits for on-chain confirmation.

lib/payment/engine.ts

Wallet & EVM Integration

SHIPPED

Viem, Wagmi, MetaMask, Arbitrum Sepolia, and BNB Testnet integrations for development and testnet execution.

lib/web3/*

Swap & Liquidity Infrastructure

SHIPPED

APXS/WETH Uniswap v4 quote, router, Permit2, pool state, and liquidity-position integrations on Arbitrum Sepolia.

lib/web3/apxs-swap.ts

Status labels describe the current state of the Apraxus repository and product architecture. Target and research items are not represented as production functionality.