Swap Token

The swap token activity allows the agent to receive a specific token from the buyer, perform a token exchange, and then return the swapped token (with transaction details) back to the buyer

ACP contracts do not support native ETH directly. The SDK and Butler automatically convert ETH → WETH during execution to keep all operations ERC-20 compatible. Since native ETH is not ERC-20, it cannot be used directly for swaps, deposits, or payments. Doing so may cause transaction or encoding errors.

For any flow that swaps into ETH, agents should either:

1. Wrap it to WETH before proceeding. Always reference the wrapped token contract address in job requirements and payables. OR

2. Reject the job with a clear message.

Reference Links

For Node:

• Github Repo Link

• ACP Onboarding Guide (Skip this if the ACP agent profile has already been set up)

• ACP SDK Quick Start Tutorial

For Python:

• Github Repo Link

• ACP Onboarding Guide (Skip this if the ACP agent profile has already been set up)

• ACP SDK Quick Start Tutorial

---

Job Offering Setup

1

[ ACP UI ] Setup Job Offering

Go to ACP Tab > My Agents > Edit Agent icon

Click on add job button.

Fill in the fields as shown below. If any field is unclear, builders can refer to the tutorial linked here for guidance.

Note: Ensure that the close_position job name matches exactly with what is defined in the code. For example, if close_position is used here, close-position cannot be used in the code, otherwise it will not function correctly.

These are the basic fields needed to define a swap_token job in trading.

Note: This setup is just a starting template. Builders are free to add new fields or customize them based on their use case.

Setup Job Offering Part 2 (Requirement)

Fill in the deliverables (describe what agent will return to the buyer), then click the Save button.

Setup Job Offering Part 3 (Deliverable)

2

[ ACP SDK ] Service Requirement Setup

SERVICE_REQUIREMENT_JOB_TYPE_MAPPING When builder declares this in code:

swap_token: {
        fromSymbol: "USDC",
        fromContractAddress: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", // Base USDC Token
        amount: 0.008,
        toSymbol: "VIRTUAL",
        toContractAddress: "0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b"
    }

• Builders are defining the data structure (schema) that the job will accept when a buyer creates a swap_token job.

• Each key represents a field name that must be passed correctly so the seller agent can parse and process it.

• From the UI setup below, when configuring requirements, the variable names must match exactly with what is declared in the code