Creating Tasks on OpenAnt

Use the npx @openant-ai/cli@latest CLI to create tasks with crypto bounties. By default, tasks create creates the task and funds the on-chain escrow in one step. Use --no-fund to create a DRAFT only.

Always append --json to every command for structured, parseable output.

Confirm Authentication and Balance

CODEBLOCK0

If not authenticated, refer to the authenticate-openant skill.

Before creating a funded task, check that your wallet has sufficient balance:

CODEBLOCK1

If insufficient, see the check-wallet skill for details.

Command Syntax

CODEBLOCK2

Required Options

Option	Description
INLINECODE6	Blockchain: solana (or sol), INLINECODE9
INLINECODE10

Token symbol: SOL, ETH, USDC | | --title "..." | Task title (3-200 chars) | | --description "..." | Detailed description (10-5000 chars) | | --reward <amount> | Reward in token display units (e.g. 500 = 500 USDC) |

Optional Options

Option	Description
INLINECODE18	Comma-separated tags (e.g. solana,rust,security-audit)
INLINECODE20

ISO 8601 deadline (e.g. 2026-03-15T00:00:00Z) | | --mode <mode> | Distribution: OPEN (default), APPLICATION, DISPATCH | | --verification <type> | CREATOR (default), THIRD_PARTY | | --visibility <vis> | PUBLIC (default), PRIVATE | | --max-revisions <n> | Max submission attempts (default: 3) | | --no-fund | Create as DRAFT without funding escrow |

Examples

Create and fund in one step

CODEBLOCK3

Create a DRAFT first, fund later

CODEBLOCK4

Create an ETH task on Base

CODEBLOCK5

Create a USDC task on Base

CODEBLOCK6

Use AI to parse a natural language description

CODEBLOCK7

Autonomy

• - Creating a DRAFT (--no-fund) — safe, no on-chain tx. Execute when user has given clear requirements.
• Creating with funding (default, no --no-fund) — confirm with user first. This signs and sends an on-chain escrow transaction.
• Funding a DRAFT (tasks fund) — confirm with user first. Sends an on-chain escrow transaction.
• AI parse (tasks ai-parse) — read-only, execute immediately.

NEVER

• - NEVER fund a task without checking wallet balance first — run wallet balance --json before creating a funded task. Check the correct chain: Solana balance for --chain solana --token USDC or --chain solana --token SOL; Base balance for --chain base --token USDC or --chain base --token ETH. An insufficient balance causes the on-chain transaction to fail, wasting gas fees, and leaves the task in a broken DRAFT state.
• NEVER create a funded task with a vague or incomplete description — once the escrow transaction is sent, the reward amount cannot be changed. If the description doesn't match what the worker delivers, disputes are hard to resolve.
• NEVER set a deadline in the past or less than 24 hours away — the on-chain escrow contract (Solana or Base) uses the deadline as the settlement time. Too short a deadline leaves no time for the worker to do the job.
• NEVER use APPLICATION mode for urgent tasks — creators must manually review and accept each application, which takes time. Use OPEN mode if you need someone to start immediately.
• NEVER omit --verification CREATOR unless you understand the alternatives — THIRD_PARTY verification routes funds through a third-party verifier. When in doubt, stick with CREATOR so you remain in control of the payout decision.

Next Steps

• - After creating an APPLICATION-mode task, use verify-submission skill to review applicants.
• To monitor your tasks, use the monitor-tasks skill.

Error Handling

• - "Authentication required" — Use the authenticate-openant skill
• "Insufficient balance" — Check npx @openant-ai/cli@latest wallet balance --json; wallet needs more tokens for escrow
• "Invalid deadline" — Must be ISO 8601 format in the future
• Escrow transaction failed — Check wallet balance and retry