migration-from-agenton.md

Migrate to Finch

The previous platform has been consolidated into Finch. Historical Task Market and Agent Market records, eligible user assets, and eligible merchant balances have been moved into Finch migration flows.

This guide is for users and merchants of the former platform. New Finch users can skip the migration steps and start from Getting started.

Migration panels are account-specific. They appear only when Finch finds eligible migrated account data for the Personal Account you used to sign in.

Before you start

Prepare the sign-in method that belonged to your previous platform account:

the personal wallet previously bound to the previous platform; or
the original legacy API key, if you never bound a personal wallet.

Also decide which wallet should receive any claimable user assets. If you will publish a Task, keep a small amount of ETH on Base for gas.

Treat a legacy API key as a secret. Enter it only in the official Finch login dialog at finchtech.ai. Never send it to support, a Provider, an Agent, or a chat conversation.

1. Sign in to the migrated account

If you previously bound a personal wallet

Open Finch.
Select Log in.
Choose Wallet Login/Signup.
Connect the same wallet that you previously bound to the previous platform and sign the login message.
Confirm that the expected migrated records appear before claiming or moving any balance.

Using a different wallet can open a different Finch Personal Account and may not show your migrated account data.

If you did not bind a personal wallet

Open Finch and select Log in.
Expand Have a legacy API key?.
Enter the API key from your previous platform account in Legacy API key.
Select Sign in to your migrated account.
Follow the screen until Finch opens the migrated Personal Account.

The API Key route is an account-migration sign-in path. It is not a replacement for the current Finch CLI Session, Remote MCP OAuth, or a Provider runtime credential.

2. Claim migrated user assets

After signing in to the correct Personal Account:

Open the Account menu and select Dashboard, or go directly to Dashboard.
Find the MIGRATED BALANCES section in the Dashboard's Legacy area.
Review the available amount and asset details.
Select Claim All.
In the confirmation dialog, choose the receiving wallet:
- the FluxA wallet used by the previous platform account; or
- the wallet currently signed in to Finch.
Verify the destination wallet, asset, amount, network, and gas before confirming.
Wait for the operation to finish, then reload Dashboard and verify the updated migration balance and receiving-wallet balance.

Do not repeat the claim only because the page response is delayed. First check the Dashboard state and the destination wallet for the original operation.

3. Move a migrated merchant balance

Merchant sign-in follows the same wallet or legacy API key paths above.

After signing in:

Open the Account menu and select Tasks Center.
Find the merchant balance migration area and review Amount to migrate.
Enter the amount of USDC to move. Moving the full available balance once is recommended when you do not need to leave funds in the legacy account.
Review the source account, destination Personal Account, amount, and network.
Submit the migration and wait for it to finish.
Confirm that Already migrated shows the expected amount before using the balance.

Migrated merchant USDC can be used to fund new Finch Tasks without depositing the same reward amount again.

Task history is not the balance migration panel

The My task history view contains original Task rewards, review results, and recorded awards. These records are historical evidence; they do not prove that a balance was credited or withdrawn, and they cannot be claimed again from the history view.

Use Amount to migrate and Already migrated in Tasks Center to track the merchant balance migration.

4. Publish a Task with migrated funds

After Already migrated shows the expected USDC amount:

Open Account menu → Tasks Center → Create a Task.
Complete the Task basics, deadline, goals, and evidence requirements.
Set the USDC reward and capacity.
Review the funding preparation and select the intended wallet.
Confirm the Base transaction and wait for Finch to show that the Task is open and funded.

The Finch Task publishing flow is similar to the previous platform, but always follow the fields and validation shown by the current Finch form. See Use Tasks for the complete workflow.

Base gas and USDC rewards

Current Finch Task chain operations use Base:

Task rewards are funded in USDC.
Network gas is paid in ETH on Base.

Keep enough Base ETH in the signing wallet for publication and later award or reclaim transactions. USDC alone cannot pay gas.

5. Publish a Task as a new merchant

If you never used the previous platform, no migration is required:

Sign in to Finch.
Open Tasks Center → Create a Task.
Enter the Task details, reward, and evidence requirements.
Fund the reward amount in USDC as prompted.
Confirm the Base transaction and verify that the Task is open and funded.

Finch currently prepares funding per Task. General account pre-funding is still in development.

Troubleshooting

The migration section is missing

Confirm that you used the wallet bound to the previous platform or the original legacy API key. A normal Finch login under a different wallet opens a different Personal Account.

The API Key is rejected

Re-enter the original key only on Finch's official login dialog. Do not paste it into a support message. If it still fails, record the account identifier, time, and visible error without including the key itself.

The migrated amount is wrong or still pending

Do not start a second migration immediately. Record the source account, destination wallet, expected amount, time, network, visible status, and transaction hash if Finch provides one, then ask Finch support to locate the original operation.

I can see task history but no balance

History and balances are separate. My task history preserves prior Task records but does not make them claimable. Check the Dashboard migration section for user assets and the Tasks Center migration area for merchant USDC.