Agirails Agent Smart

A Claude Code skill for building AI agent payment infrastructure using the AGIRAILS protocol. Covers agent wallet creation, payment processing, settlement mechanics, and integration patterns for the emerging AI agent economy where autonomous agents earn, spend, and transact.

When to Use This Skill

Choose Agirails Agent Smart when:

• You're building AI agents that need to process payments
• You want to onboard agents onto the AGIRAILS payment network
• You need to implement agent wallet management and settlement
• You're building marketplace infrastructure where agents transact
• You want to understand agent-to-agent payment protocols

Consider alternatives when:

• You need human-facing payment integration (use Stripe/payment skill)
• You want general agent architecture (use an agent platform skill)
• You need cryptocurrency/blockchain payments (use a web3 skill)

Quick Start

Copy
# Install the skill
claude install agirails-agent-smart

# Onboard an agent to AGIRAILS
claude "Set up an AGIRAILS agent wallet for my code review agent that charges $0.10 per review"

# Implement agent payments
claude "Implement payment processing for my agent marketplace: agents bid on tasks, winner gets paid on completion"

# Design settlement flow
claude "Design the settlement flow for a multi-agent pipeline where 3 agents collaborate on a task and split payment"

Core Concepts

AGIRAILS Architecture

Component	Purpose	Description
Agent Wallet	Identity + balance	Each agent has a unique wallet for receiving/sending payments
Settlement Layer	Transaction processing	Handles payment clearing between agents
Task Registry	Work tracking	Records tasks, bids, completions
Reputation System	Trust scoring	Tracks agent reliability and quality

Agent Payment Flow

1. Task Posted → Client creates task with budget
2. Agent Bids → Agents submit bids with price + capabilities
3. Agent Selected → Client or system selects winning agent
4. Work Performed → Agent completes the task
5. Verification → Output verified against requirements
6. Settlement → Payment transferred to agent wallet
7. Reputation → Both parties' reputation updated

Payment Models

Model	Description	Use Case
Per-Task	Fixed price per completed task	Discrete, well-defined jobs
Per-Token	Price based on compute used	LLM-based agent work
Subscription	Recurring payment for ongoing service	Always-on monitoring agents
Revenue Share	Split earnings between collaborating agents	Multi-agent pipelines
Escrow	Funds held until task verified	High-value or untrusted transactions

Configuration

Parameter	Type	Default	Description
network	string	"testnet"	Network: testnet, mainnet
payment_model	string	"per_task"	Model: per_task, per_token, subscription, revenue_share
currency	string	"usd"	Settlement currency
escrow	boolean	true	Use escrow for payments
auto_settle	boolean	false	Auto-settle on task completion

Best Practices

1. Use escrow for all agent transactions — Agents are autonomous and might not deliver as promised. Escrow protects both parties: the client's funds are locked until the task is verified, and the agent is guaranteed payment upon completion.

2. Start on testnet — Always develop and test on the AGIRAILS testnet before handling real money. Agent payment flows have many edge cases (timeouts, partial completions, disputes) that need thorough testing.

3. Implement verification before settlement — Automated verification of agent output quality prevents paying for low-quality or incomplete work. Define clear acceptance criteria for each task type and verify programmatically where possible.

4. Track reputation rigorously — An agent's reputation score should reflect task completion rate, quality ratings, and response time. Use reputation to prioritize agents in task matching and determine escrow requirements.

5. Handle disputes gracefully — Build a dispute resolution flow: client flags an issue → evidence reviewed → mediation → resolution. Without dispute handling, the payment system loses trust from both agents and clients.

Common Issues

Settlement delays — Verification steps can delay settlement. Set clear SLAs for verification (e.g., auto-approve after 24 hours if no dispute raised) to ensure agents receive timely payment.

Agent wallet balance insufficient — Agents that need to pay for sub-tasks or tools may run out of funds. Implement balance checks before task acceptance and allow agents to set minimum balance thresholds.

Multi-agent payment splits are complex — When multiple agents collaborate, define the split before work begins. Use smart contracts or pre-agreed revenue sharing formulas to automate distribution and prevent post-completion disputes.