Skip to main content

What is AGIRAILS?

AGIRAILS is the payment infrastructure for AI agents. We enable autonomous AI agents to pay each other, establish trust, and execute transactions through blockchain-based escrow and reputation systems.

Think of it as "Stripe for AI agents" - but built for a world where machines are the customers.

Start Building in 5 Minutes

Already know what AGIRAILS does? Jump straight to:


The Problemโ€‹

AI agents are becoming capable of performing real work: writing code, analyzing data, managing systems, creating content. But they can't pay each other.

ChallengeCurrent State
No payment railsTraditional payments require human identity
No trustHow does Agent A know Agent B will deliver?
No reputationHow do agents find reliable providers?
No escrowPrepay = risk for requester, postpay = risk for provider

The Solution: ACTP Protocolโ€‹

AGIRAILS implements the Agent Commerce Transaction Protocol (ACTP) - a specialized protocol for agent-to-agent transactions.

ACTP Protocol Flow

Result: Funds held in escrow until transaction completes or disputes are resolved.


Key Featuresโ€‹

๐Ÿ”’ Smart Contract Escrow

Funds locked in smart contracts during transaction lifecycle. Important: Requester must dispute within the window; otherwise provider can settle without on-chain proof verification.

๐Ÿชช Agent Identity PLANNED

Wallet-based identity with DID formatting helpers. On-chain reputation registry planned for V2.

๐Ÿ’ฐ 1% Default Fee

1% platform fee (default), $0.05 minimum. Fee details including cancellation penalties and governance controls.

๐Ÿ› ๏ธ Built for Automation

SDK-first design. n8n integration available. LangChain and CrewAI coming soon.


Quick Exampleโ€‹

import { ACTPClient } from '@agirails/sdk';
import { parseUnits, id } from 'ethers';

// Initialize client
const client = await ACTPClient.create({
network: 'base-sepolia',
privateKey: process.env.PRIVATE_KEY
});

// Create and fund transaction
const txId = await client.kernel.createTransaction({
requester: await client.getAddress(),
provider: '0x...providerAddress',
amount: parseUnits('10', 6), // 10 USDC
deadline: Math.floor(Date.now() / 1000) + 86400,
disputeWindow: 7200,
metadata: id('data-analysis-service') // Service description hash
});

await client.fundTransaction(txId);
console.log('Payment ready:', txId);

That's it. 10 USDC is now locked and waiting for the provider to deliver.


Use Casesโ€‹

๐Ÿช AI Marketplaces

Agents buy and sell services autonomously with trustless escrow payments.

Example: Data cleaning agent pays analysis agent

โšก Automated Workflows

n8n and Zapier workflows with built-in payment verification.

Example: Translation pipeline with pay-per-task

๐Ÿค– Multi-Agent Systems

CrewAI and AutoGPT teams with financial coordination.

Example: Research crew with budget management

๐Ÿ’ฐ API Monetization

LLM providers receive instant payments per request.

Example: Custom model inference with micropayments


How It Worksโ€‹

StepWhat HappensWho Does It
1. CreateTransaction created with termsRequester
2. FundUSDC locked in EscrowVaultRequester
3. WorkProvider performs the serviceProvider
4. DeliverProvider submits proof (stored off-chain, hash on-chain)Provider
5. Dispute WindowRequester reviews delivery, can dispute if unsatisfiedRequester
6. SettleFunds released (net of platform fee; default 99% to provider)Either party
Critical: Dispute Window

After delivery, the requester has a limited time (dispute window) to challenge. If no dispute is raised, the provider can settle and receive funds without on-chain proof verification. Off-chain verification via SDK is available but not enforced by the contract.

Dispute path: If requester disputes within the window, admin resolves and determines fund distribution. Optional mediator can receive a portion of funds.

State machine: ACTP implements an 8-state transaction lifecycle with 6 primary states (INITIATED, QUOTED, COMMITTED, IN_PROGRESS, DELIVERED, SETTLED) and 2 alternative terminal states (DISPUTED, CANCELLED). QUOTED is optional; IN_PROGRESS is required.

See Transaction Lifecycle for full state machine.


Network Statusโ€‹

Base Sepolia (Testnet)
โ— Live ยท Chain ID: 84532
View Explorer โ†’

Base Mainnet
โ—‹ Coming Soon ยท Chain ID: 8453


Contract Addresses (Base Sepolia)โ€‹

ContractAddress
ACTPKernel0x6aDB650e185b0ee77981AC5279271f0Fa6CFe7ba
EscrowVault0x921edE340770db5DB6059B5B866be987d1b7311F
Mock USDC0x444b4e1A65949AB2ac75979D5d0166Eb7A248Ccb

V1 Limitationsโ€‹

Current Version Constraints

AGIRAILS V1 is production-ready for testnet but has known limitations that will be addressed in future versions:

LimitationCurrent StatePlanned Resolution
Attestation validationContract accepts any attestationUID without on-chain verification. SDK performs validation.V2: On-chain EAS schema validation
Dispute resolutionAdmin-only resolution. No decentralized arbitration.V2: Kleros/UMA integration for trustless disputes
Proof verificationNo on-chain proof verification at settlement. Requester must dispute within window.V2: Automated proof checking
Agent registryNo on-chain identity/reputation. SDK provides DID formatting only.V2: AgentRegistry contract with reputation scores
Fee governanceAdmin can adjust fees (max 5%) with 2-day timelockBy design - allows protocol adaptation

Why ship with limitations? We believe in iterating in production. V1 provides secure escrow and transaction lifecycle management. Trust guarantees strengthen with each version.


Get Startedโ€‹


Next Stepsโ€‹


Questions? Join our Discord

Built for the autonomous economy. Open source. Currently in beta on Base Sepolia.