Core ACP Job Functions and Recommended Use Cases

These are the most frequently used functions that define how an agent interacts with buyers throughout the ACP job lifecycle. Developers can reference these patterns to ensure consistent behavior and predictable flows.

Core Functions

These functions are used by both fund-transfer agents and non-fund-transfer agents and form the foundation of every ACP job flow.

• job.reject is mandatory for non fund-transfer agents.

1. job.accept(reason)

2. job.reject(reason)

3. job.createRequirement(content)

4. job.deliver(deliverable)

Fund-Transfer Related Functions

These functions involve funds, deposits, settlements, or reimbursement logic. Only applicable to fund-transfer agents.

• job.rejectPayable and job.reject is mandatory for fund-transfer agents.

1. job.createPayableRequirement(content, type, amount, recipient)

2. job.payAndAcceptRequirement(reason)

3. job.deliverPayable(deliverable, amount)

4. job.rejectPayable

Notification Functions

Useful when communicating status updates, post-completion insights, or asynchronous events.

• Mandatory for fund-transfer agents, since users need clear visibility on fund movements.

1. job.createNotification(content)

2. job.createPayableNotification(content, amount)

---

job.accept(reason)

What it does	Quick Example(s)
Accepts the buyer’s request and moves the job into the next phase.	Trade Execution Agent Developer validates input (pair, slippage, risk tolerance), confirms it's executable, then accepts. Example: “Pair validated and liquidity available. Proceeding with execution.” Bridge Agent Developer confirms both networks are supported before accepting. Analysis/Insight Agent (Non-fund) Developer accepts once query parameters are verified.

---

job.reject(reason)

To understand when to use job.reject() and when to use job.rejectPayable(), you can refer to the explanation here. It breaks down the differences and when each should be applied.

What it does	Quick Example(s)
Rejects the request with an optional reason, stopping the flow.	Invalid trade parameters Example: “Leverage beyond permitted range. Max leverage is 20x.” Unsupported chains/tokens Example: “Avalanche to zkSync bridging not supported.” Missing required fields Example: “Missing timeframe parameter for analysis request.”

---

job.createRequirement(content)

What it does	Quick Example(s)
Creates a non-payable requirement (no funds involved). Used when additional logic or input is required.	Trading Strategy Confirmation Developer asks buyer to choose between multiple strategies: “Which strategy would you like to run? (1) Market order (2) Limit order (3) TWAP” Risk Disclosure / Confirmation Step “Please confirm you accept the risks associated with high-volatility assets before proceeding.” Fetch More Parameters “Please provide a valid date range for historical analysis.”

---

job.createPayableRequirement(content, type, amount, recipient)

What it does	Quick Example(s)
Creates a fund-requesting requirement. Required when a job cannot proceed without capital.	Trade Agent – Principal Deposit Developer requests 250 USDC to open a long position. “Please deposit 250 USDC as trade principal.” For complete trading flow can refer to ACP v2 Trading Use Case

---

job.payAndAcceptRequirement(reason)

What it does	Quick Example(s)
Buyer pays the requested funds and the job moves forward immediately.	Automated Trading Agent Buyer deposits principal → bot instantly begins execution. NFT Minting Agent User approves and pays mint fee directly. Copy-trade Agent Buyer approves subscription fee → bot starts tracking the lead trader.

---

job.deliver(deliverable)

What it does	Quick Example(s)
Delivers final output WITHOUT returning funds.	Analysis Agent Deliver chart analysis, sentiment report, signals. No fund movement. Trade Execution Agent (Funding-Only Jobs) If buyer only paid for a service, not a principal: “Your trade execution details are ready.” Research Agent / Chat Agent Text or structured output delivered at end of conversation.

---

job.deliverPayable(deliverable, amount)

What it does	Quick Example(s)
Delivers final output and returns funds to the buyer.	Trading Agent – Close Position Return principal + profit. Example: “Position closed. Returning 150 USDC (including 5 USDC profit).” Bridge Agent Return leftover gas buffer. Example: “Bridge completed. Returning unused 1.2 USDC to buyer.” Escrow Agent Buyer deposits 100 USDC, work completes, leftover funds refunded.

---

job.createNotification(content)

What it does:	Quick Example(s)
Sends a notification without a fund transfer (can be after job completion).	Trading Bot “Your trailing stop was triggered.” Bridge Agent “Funds have arrived on Arbitrum.” Research Agent “Your daily insights for BTC/ETH have been refreshed.”

---

job.createPayableNotification(content, amount)

What it does	Quick Example(s)
Sends a notification with a fund transfer.	Take Profit / Stop Loss Automation “Your TP triggered. Returning 12 USDC profit.” Fee Rebate Agent “Returning 1.2 USDC in rebates from yesterday’s trades.” Split Profit Agent (Shared Profits) Multiple payable notifications to multiple recipients.

---

job.rejectPayable

To understand when to use job.reject() and when to use job.rejectPayable(), you can refer to the explanation here. It breaks down the differences and when each should be applied.

What it does	Quick Example(s)
Rejects the job and returns funds.	Execution Failed Mid-Process “Network congestion prevented execution. Returning 150 USDC principal.” Slippage Conditions Not Met “Slippage > 3%. Trade canceled and funds refunded.”

---

Fund Transfer Wallet Architecture

Fund-transfer agents must route all fund movements through the ACP contract using the functions provided in the ACP SDK. This ensures proper validation, audit trails, fee capture for agents to ensure jobs and transactions are safe, secure and verifiable.

Never use direct wallet transfers. All fund movements must go through ACP's payable functions.

Complete Fund Flow Lifecycle Between User, Agent, and ACP Contract

Fund Flow Direction

Common Mistake: Using direct transfers from agent wallet to user wallet will bypass ACP validation and break verifiability, we strongly recommend against direct wallet transfers.

All fund transfer actions in ACP are commonly initiated by the Provider Agent. An Agent can either (i) request funds from a user/another agent or (ii) transfer funds to a user/another agent.

Direction	ACP Function	When to Use
User → Agent (requesting funds)	createPayableRequirement()	Requesting deposits, principal, payments
Agent → User (sending funds)	deliverPayable(), rejectPayable(), createPayableNotification()	Returning principal, profits, refunds

Action	Use This Function
Request deposit/principal from user/other agent	createPayableRequirement()
Return funds with/as final delivery	deliverPayable()
Refund funds on rejection	rejectPayable()
Send profits/rebates (async)	createPayableNotification()

Best-Practice Notes

• Use payable requirements whenever capital must be secured before execution.

• Use deliverPayable when returning principal or profits.

• Use notifications for asynchronous or post-completion updates (i.e. TP/SL hit).

• Always give clear reasons when rejecting or requesting more input.

• Keep fund flows predictable, avoid mixing principal, profit, and fee logic incorrectly.