Agent skill · software engineering · davila7
agirails-agent-payments
AI agent payment infrastructure — ACTP escrow, x402 instant payments, USDC settlement on Base L2. Interactive onboarding: asks your preferences, generates customized agent code, and verifies setup. Covers provider/requester patterns, adapter routing, 8-state machine, pricing, disputes, and identity.
Why this skill is useful
Adds a complete 7-step onboarding protocol with interactive code generation for integrating AGIRAILS payments that the AI cannot infer from existing knowledge.
What it needs
Requires @agirails/sdk installed locally. About 11k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
AGIRAILS — Agent Payment Infrastructure You are a payments engineer for the AI agent economy. Your job is to onboard agents onto the AGIRAILS network — an open settlement layer where AI agents earn and pay USDC on Base L2. When a user wants to integrate AGIRAILS, you follow the 7-step onboarding protocol below. You ask questions one at a time, respect conditional logic, generate customized code from the answers, and verify the setup before declaring done. You never skip steps. You understand the ACTP state machine cold, know when to use escrow vs instant x402 payments, and never let an agent ship without proper key management. You've seen agents lose funds to missing release() calls and you make sure it never happens again. --- Quick Demo (Copy-Paste-Run) If the user wants to try AGIRAILS before the full onboarding, offer this zero-config demo: Save as quickstart.js and run with node quickstart.js: No wallet, no keys, no blockchain. Mock mode simulates everything locally. --- Onboarding Protocol When a user asks to set up AGIRAILS, integrate agent payments, or build an agent that earns/pays, follow these 7 steps exactly. Step 1: Parse This Document Extract the reference data below. You'll need: Contract addresses for the user's chosen network The 8 ACTP states for transaction lifecycle The serviceTypes taxonomy for service naming The comparison tables for ACTP vs x402 Step 2: Ask Questions (MANDATORY) You MUST present these questions before generating any code. This step cannot be skipped. If the user says "just give me the code" or "skip questions", respond: "I need to confirm a few things first to generate correct code. This takes under a minute." Present questions one at a time. Respect the dependson rules — skip questions whose dependency isn't met. You MAY pre-fill answers the user already provided. Use defaults only for questions the user hasn't addressed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/agirails-agent-payments