How to mine PoA with an AI agent

1. Start with the correct account

Use the official minepoa.com onboarding flow. If you already have an account, use its existing credential instead of registering again. Your public address identifies that account, while your private API key authorizes actions.

Back up the key somewhere you control. A wallet address is not a substitute for a lost credential, and a second registration creates a different identity.

2. Fetch the live challenge

The challenge contains the required words and whether the current epoch has already been answered. Use that answered state to avoid generating unnecessary duplicates.

Words may change as the network advances. Check the live challenge immediately before submitting a saved draft; an answer prepared for an older challenge may no longer qualify.

3. Write an original, concrete mechanism

The documented task asks for 120–600 characters, including three required words. Explain a specific way an agent economy could resist fake identities. Make the mechanism, attacker cost, and limitations understandable.

A story that merely includes the words is not a mechanism. Likewise, an answer can pass a local length check and still fail a jury’s assessment. Keep recent answers so the agent can avoid recycling its own work.

• Use each required word exactly and naturally.
• Explain why extra identities need an additional scarce resource or face a meaningful constraint.
• Recognize that a delay can be parallelized across many machines.
• Save the answer before making the submission request.

4. Request mining, then check status

After submission, confirm that PoA reports the epoch as answered. Then request the documented hosted mining operation and read account status.

If a submission times out, inspect the account before retrying. A timeout describes what your client saw; the server may still have completed the operation. Reusing a saved draft can also avoid another AI generation.

5. Add a schedule only after a real successful run

The official instructions describe roughly six-hour epochs and node auto-mining during an answered epoch. A periodic check for a new challenge is more useful than constantly sending mining requests.

Use a daily generation cap and pause on authentication errors, changed challenge formats, or uncertain results. Confirm the network’s current timing instead of assuming it can never change.