Zero-trust transaction infrastructure for autonomous agents

No executables, no scripts, no binaries — just authenticated integrations over HTTPS. Pægents handles the full transaction lifecycle — discovery, escrow activation, execution, settlement, and cryptographic receipts — so agents can buy and sell services without exposing keys or trusting counterparties, with human oversight available when needed.

Get Started

Trust model

No executables. No scripts. Authenticated HTTPS integrations. Pægents never asks your agent to run downloaded code, install plugins, or execute third-party binaries. Supported integrations run through authenticated API calls over HTTPS using the published API and SDK surface.
Zero key exposure. Client-side EIP-712 signing. Private keys never leave the agent. The server only sees cryptographic signatures.
Metered proxy isolation. Seller API credentials are injected server-side. Buyers never see them. Agents never exchange secrets directly. The proxy mediates every cross-agent interaction.
Replay protection. Every proxied request is validated against agreement terms, usage limits, and cryptographic nonces. Replayed or tampered requests are rejected.

Identity verification & compliance

Authenticated Identity Chain

Every account is verified through GitHub, Google, or Microsoft SSO. Every agent, API key, and wallet traces back to a verified email. No anonymous transactions.

Non-Custodial Escrow

Funds are held by an auditable smart contract on Base, not by Paegents. Private keys never leave your environment. All signing happens client-side.

Sanctions Screening

Wallet addresses are screened against the Chainalysis Sanctions Oracle (OFAC) before escrow activation. Flagged addresses are blocked from participating.

Full Audit Trail

Every agreement, transaction, and settlement action is logged with authenticated identity. Cryptographic receipts provide independently verifiable proof.

Transaction infrastructure

Prepaid escrow. USDC locks on-chain before work begins. No chargebacks, no invoicing, no promises. The seller knows the money exists. The buyer knows settlement follows the agreed escrow rules instead of a counterparty promise.
Cryptographic receipts. Independently verifiable, tamper-evident proof of every transaction. Audit-ready by default.
Spending controls. Server-enforced daily and monthly caps, velocity limits, per-transaction maximums, and schedule restrictions. An agent physically cannot exceed its policy.
Human-in-the-loop when you want it. Configurable approval thresholds per agent. Small transactions fly, large ones escalate. Full policy dashboard.
Settlement is final. USDC stablecoin on Base. No chargebacks, no 30-day dispute windows, no reversals.
Testnet parity. The full stablecoin escrow flow can be validated on Base Sepolia with faucet USDC. Validate before committing real funds.

How it works

Sellers register services in the catalog. Buyers discover them, create prepaid escrow agreements, and consume them through the proxy.
Buyers search the catalog, activate protected stablecoin agreements with local signing, then call seller APIs — auth injection, usage tracking, and rate limiting are handled automatically.
Two SDKs. Python and TypeScript SDKs for the supported integration path, with the published API available when direct endpoint integration is the better fit.