Local setup and payments
Where do I get the test-network configuration?
Run Install on the User setup page. It downloads public deployment settings automatically. The same script continues automatically: the terminal collects your test Safe and owner addresses locally and starts the connection test. A remote computer still needs loopback access arranged by the operator.
I stopped the terminal. Must I start again?
Run the same command with the same saved directory and configuration. Resume successful steps. For an uncertain payment, retain its saved request and identifier so a retry does not become another order.
I linked a Safe, but purchases still fail.
Market linking only enables activity display. Check local Wallet initialization/unlock, the bound on-chain Policy, its network and limits, Safe token funds and current service availability. Use the terminal’s readiness result to choose the next fix.
My Policy is expired, revoked or does not match the platform.
Do not edit an address locally to bypass the check. A replacement authorization needs owner approval. See Spending authorization for the current private migration path and live-signing limitations.
I received a result. Has the Provider been paid?
Delivery and payout are separate events. Check the order status and disclosed payout time through your local tools. Do not use download statistics or the presence of output as proof of final payment.
I unlinked my Safe. Why can Wallet still pay?
Unlinking only removes the Market association. Follow the revocation guide to stop new payments under an active Policy.
Provider connection
The terminal did not ask me to sign in.
A valid saved Market session is reused. Check the displayed account. Session expiry does not stop a connected server, which uses its own Provider credential.
Endpoint verification succeeded, but the service is not ready.
Registration, Registry qualification, a fresh Quote and local paid admission are separate checks. Follow the terminal’s blocker. If it asks for application configuration, run the displayed command and return with ready. Otherwise keep the server online and check again after about a minute.
The price or qualification is still pending.
Keep the service and rolling price declaration available. Repeated status checks do not force a new price observation. If the wait lasts several minutes, use details and ask the platform operator to inspect the background worker; do not create another identity.
Service removal is taking a long time.
Existing or unfinished orders can keep removal waiting. Keep the application and credentials available and contact the operator if it cannot finish. Removal does not automatically cancel or refund those orders.
Publishing and Account
I clicked Publish, but the Skill is not public.
Open Account → Skills and Logs. Review runs in the background; awaiting approval needs a manual decision. A previous public version remains available during an update.
Why are Edit and Delete disabled?
The submission is under review. The submitted content must remain unchanged. You can still read Logs. Wait for a decision before editing or deleting.
I only want to undo an update draft.
Use Delete draft on the published Skill, not Delete. See draft and release management.
My ZIP has a version conflict.
Changed ZIP bytes require a new packageVersion in agentpay.json. Reusing the same name/version for different bytes is rejected. Market does not increment it for you.
Automatic save still shows an old time.
Unchanged content does not trigger saving. For new changes, wait about 30 seconds, check for errors, or use Save. Saving is suspended during review and conflicting operations. Confirm the save succeeded before closing.
Why are counts lower than my clicks or downloads?
Repeated visits/downloads are deduplicated, and cached charts may update later. See activity definitions. Download counts are not order counts.
Ask for help
Record the page or terminal step, visible error, time with timezone, and relevant public order or submission identifier. Contact the platform operator for persistent review, registration or settlement problems. Do not send unlock secrets, private keys, session tokens, Provider credentials or unredacted configuration files.