Skip to main content
Build AI agents on Abstract that can pay for APIs, accept payments from other agents, and operate through Abstract Global Wallet. Abstract’s agent stack has four main pieces:
  • x402 for pay-per-request HTTP payments
  • MPP for HTTP-native charge and session payments
  • AGW CLI and MCP for agent wallet access
  • llms.txt, llms-full.txt, SKILL.MD, and docs MCP for coding-agent context

​
What you can build

  • An agent that pays for premium APIs on demand
  • A paid API that charges other agents per request
  • A wallet-enabled operator that reads balances, previews transactions, and executes approved actions
  • A coding agent that understands Abstract docs and uses the right SDKs and network settings

​
Choose your path

Payments

Start with x402 or MPP if your agent needs to pay or get paid.

Wallet Access

Start with AGW CLI if your agent needs controlled wallet access.

Build Paths

Pick the shortest route based on the workflow you actually need.

Agent Resources

Use docs MCP, llms.txt, and SKILL.MD to give coding agents Abstract context.

​
How the pieces fit together

  1. Choose a payment model: x402 for simple 402-based pay-per-request flows, or MPP for HTTP-native charge and session payments.
  2. Choose a wallet path: AGW CLI if the agent should operate through Abstract Global Wallet with preview-first writes and policy-scoped permissions.
  3. Add docs-native context: point coding agents at the docs MCP endpoint or the machine-readable documentation files.

​
Payments for agents

x402

Accept and make HTTP payments on Abstract using the public facilitator.

MPP

Use charge payments for one-off requests or session payments for repeated micro-payments.

​
Wallet access for agents

AGW CLI Overview

Understand the command surface, delegated signer model, and MCP support.

Run AGW as MCP

Expose wallet, transaction, app, and Portal actions to MCP-capable hosts.

​
Resources for coding agents

Agent Resources

Start here for docs MCP, llms.txt, llms-full.txt, and SKILL.MD.

Contracts and Endpoints

Keep the key chain IDs, token addresses, facilitators, and agent endpoints in one place.