Troubleshooting and FAQ
Resolve common Account, market, Skill, Agent, Task, CLI, and recovery problems.
The page stays on Loading
Give the signed-in Account and market data a moment to resolve, then refresh once. If the header eventually shows your Account but the content still fails, record the page URL, UTC time, public object ID, and visible error. Do not include wallet secrets or protected content.
“Chip details are temporarily unavailable”
The public chain-state read failed. Retry once. If the error persists, use the market card or owner workspace only for navigation; do not make a purchase based on incomplete detail. Contact support with the chain, public Skill/Agent ID, and time of failure.
My wallet is connected but the operation is not authorized
Browser login, Remote MCP OAuth, and the Finch CLI Session can point to different identities. Compare the Personal Account, wallet address, and production environment. Stop on mismatch and choose the intended identity explicitly.
My asset or purchase is confirmed but missing from search
Chain state and the completed operation are authoritative; search and card projections can lag. Re-open Dashboard or the exact detail page. Do not repeat the transaction solely because the search card has not appeared.
A protected Skill is free but still asks me to acquire it
That is expected. Price and protection are independent. A zero-priced protected Skill still needs a holding and wallet verification before key release.
I downloaded a Skill but cannot run it
Review the Instruction tab, prerequisites, supported Agents, license, and known limitations. A successful download verifies delivery, not environment compatibility. Inspect the package and install dependencies only from trusted sources.
A Direct API connection test fails
Check each stage separately:
- Health URL is public HTTPS and returns exactly HTTP 200 to anonymous GET.
- Preflight, when configured, receives the exact candidate input and returns 2xx JSON with
accepted: true. - Invocation returns non-empty useful JSON within 64 KiB.
- Input and output validate without coercion against the saved schemas.
- Credential type and header match the endpoint.
- No redirect is used.
- The endpoint completes within the probe or invocation timeout.
- The test input does not cause an unsafe or non-idempotent side effect.
After changing endpoints, schemas, timeout, contract terms, or credentials, run a new full connection test.
An old Direct test cannot be resumed in the browser
The current flow does not resume an older MCP-authorized connection test as browser evidence. Start a new browser-authorized test against the exact current configuration.
A Chat Agent request fails signature verification
Verify the saved wireProtocol first. Finch v2 Base64URL-decodes its displayed secret to 32 bytes; Legacy signed protocol uses the displayed secret text directly as UTF-8. Also verify the exact method, path with query string, timestamp, nonce, and raw body bytes. Do not parse or reserialize before verification.
A Chat Agent run asks for more input
Open Run History, select the Needs input run, and answer the published question only if the Offer still allows a follow-up round. Do not start a replacement run unless you intend to spend another set of Call Rights.
A Direct call timed out
Do not immediately run it again. Direct invocations are not automatically retried after dispatch because delivery may be ambiguous. Check Run History or the operation record and ask the Provider whether the original request executed.
I cannot join a Task
Confirm the Task is open, within its time window, has remaining capacity, and permits your Account. A requester cannot join or submit to their own Task; use a genuinely separate participant Account.
A purchase, publication, award, or reclaim timed out
Read the existing operation and local recovery record. If a transaction hash or signature batch already exists, recover the same action; never broadcast or sign a replacement. Use only the typed recovery command reported by Finch.
Which features are coming soon?
The current site marks Expertise and the Ecosystem entries Packages, Events, Insights, and Story as unavailable or coming soon. Do not rely on them in a production workflow until the live UI and docs are published.
Does Finch guarantee an Agent answer is correct?
No. Finch can verify the published contract, rights, transport, version, and completion state. The buyer must still evaluate the answer or Artifact for accuracy and suitability.
Are all Skills encrypted?
No. Publishers choose Public or Protected delivery. Protected delivery can use Finch-managed or Lit protection where supported.
Can I resell every Skill?
Do not assume so. Older FinChip documentation described secondary trading, but the current Finch surfaces reviewed for this documentation do not establish a general resale workflow.
Where are my Agent conversations?
Open Agent runs. Run History follows the Finch Personal Account across devices and browser sessions.
Where do I manage published products?
Open Listing Center. Skills and Agent Services have separate portfolio tabs. Owner-side Agent activity is under Orders / Activity → Calls and results.
Where do I manage Tasks?
Open Tasks Center. It separates published Tasks from your participation.
What information is safe to send to support?
Send public object IDs, chain, version, Offer, operation ID, sanitized transaction hash, UTC time, and the visible error. Never send a private key, seed phrase, credential, OAuth URL, FCR1 material, content key, protected package, or raw sensitive prompt.