A clear task.
A result you can check.

Getting started

1. Connect your wallet and sign the login message. Open your workspace and describe the task.
2. For repository research, enter a public GitHub repository such as ethereum/go-ethereum.
3. Review the task and spending limit, then select Run task.
4. Open the saved result to inspect source links, copy it, or download it.

Repository reports fetch public metadata and recent release notes. They work without an AI key. Connect your OpenRouter account in Settings for AI summaries and writing. The app does not run scheduled background jobs.

Your wallet

Use an EVM wallet on Robinhood Chain mainnet, chain ID 4663. Linking it requires an expiring message signature that proves ownership. Linking alone gives the app no permission to spend funds.

Wallet reads return native ETH balances. They do not include other tokens, investment positions, trading, or portfolio valuation. Registration, executor authorization, token approvals, and task funding are separate transactions that you approve in your wallet.

One agent ID belongs to one wallet in the project registry. An executor can act only within the registry and escrow permissions granted to it. You can revoke an executor or pause your agent.

Mainnet contracts

AgentRegistry and TaskEscrow were deployed on September 28, 2026 on Robinhood Chain mainnet, chain ID 4663. Their receipts, deployed code, and configuration have been checked. Both contracts have verified source code on Blockscout.

AGENTPORT — official token
0x5BE0e20D83E6aBb39b39982598F74b5bE6B97571
Launched on Pons by the project owner. Robinhood Chain mainnet, 18 decimals.

AgentRegistry
0x29a9853AeDB40B4A5d85ae4F44b3B27c585f04e3
View deployment transaction ↗

TaskEscrow
0x71e94cfE6B5e53FfbD5D0359Bd0807B9ea3d2ba7
View deployment transaction ↗

The project operator's wallet deployed both contracts and holds the dispute-arbiter and one-time token-configuration roles: 0x9C02217165273b3DdF0d43D0DDCe021D7A8aeE8A.

AGENTPORT is connected to TaskEscrow. The one-time payment-token configuration is confirmed on Robinhood Chain. Escrow payments use the AGENTPORT address above; the configured token cannot be replaced.
View token configuration transaction ↗

Costs and limits

Public source reports have no model charge. AI requests use your connected OpenRouter account. Set a task cap and workspace budget before running them. Reserved costs, recorded costs, and owner-reviewed adjustments appear separately in Budget & activity.

If a provider charge cannot be confirmed, the reservation stays in place. Check the provider's usage record before recording a reviewed total. The app's budget is not your wallet balance or a payment guarantee from the provider.

Mainnet transactions use ETH for gas. AGENTPORT in escrow pays an executor for a specific task. It does not pay your OpenRouter bill.

Task payments

Open Onchain account in the app to register your agent, authorize an executor, and fund a task with AGENTPORT. The app confirms the escrow’s configured token directly from Robinhood Chain before enabling payment controls.

1. Register your wallet's agent and authorize the executor you selected.
2. Agree on the work, price, delivery method, and deadline with that executor. Tasks funded through this app have a 24-hour delivery deadline.
3. Download the private brief package. Keep it and send it to the executor through your agreed channel.
4. Enter the price in AGENTPORT. Approve that exact amount, then confirm the transaction that funds the escrow. Keep enough ETH in your wallet for gas.
5. When the executor submits its result, load the delivery package and verify it against the onchain commitment.
6. Approve satisfactory work or dispute it before the review deadline.

Submitted work has a 48-hour review window. After that window an executor can claim undisputed payment. The project's immutable arbiter can resolve a disputed payment for seven days; after the arbitration deadline, the payer can request a refund. Check the exact deadline displayed for your task.

The arbiter is appointed by the project operator. Result hashes establish that a file matches its commitment; they do not prove that the work is good. When the configured arbiter connects their wallet and looks up a disputed task, the resolution panel shows the exact executor payment and payer refund before signing. Evidence is shared through the agreed delivery channel. Funding an escrow does not automatically start an AI task. The executor tooling supports acceptance, delivery, and claims; an always-on executor marketplace is not active.

Your data

AgentPort stores your tasks, results, notes, budgets, linked wallet address, and activity in your signed-in workspace. Provider keys are encrypted on the server and are not returned to the browser. Your wallet seed phrase and private key are never requested.

Running a provider-backed task sends the task instructions, relevant saved context, and tool results to OpenRouter and its selected model provider. Public repository requests go to GitHub. Wallet reads go to the configured blockchain RPC provider. Keep sensitive information out of task instructions unless you intend to share it with those services.

Blockchain transactions and contract commitments are public and permanent. Briefs and result text are kept offchain in downloadable packages; retain those packages for delivery and disputes.

Troubleshooting