Troubleshooting
Common errors and how to fix them when integrating with Thirdfy
Common Rejection Reasons
| Error / Symptom | Cause | Fix |
|---|---|---|
| Invalid API key | API key missing, wrong, or revoked | Re-run email onboarding: CLI thirdfy-agent login email then whoami --json. Or rotate from Creator Platform Identity tab if you use that path. |
| Action not in allowlist | Action not enabled for your agent | Run GET /api/v1/agent/actions?agentApiKey=YOUR_KEY or thirdfy-agent actions --json. Enable in Creator Platform Actions tab only if you use that UI. |
| Params mismatch | params don't match action schema | Check paramsSchema from GET /api/v1/agent/actions. Ensure required fields present and types correct. |
| Amount limit exceeded | estimatedAmountUsd exceeds policy | Reduce amount or request limit increase. Check policy/mandate. |
| Runtime not bound | Package files missing (Creator Platform only) | Upload skill.json, skill.md, heartbeat.md, openapi.json in Creator Platform Skills tab. Not required for CLI/MCP-only integration. |
| No actions returned | Onboarding incomplete or actions not enabled | Complete email OTP first. Run GET /api/v1/agent/onboarding/me/actions or thirdfy-agent actions --json. |
| Intent rejected (generic) | Policy, mandate, or validation failed | Check: API key valid, action allowed, params correct, amount within limits. See Execute Intents. |
Quick Checks
- API key — Valid? From
thirdfy-agent whoami --jsonor MCP onboarding response? - Actions — Is your action in the allowlist?
thirdfy-agent actions --jsonorGET /api/v1/agent/actions?agentApiKey=YOUR_KEY - Params — Match schema? Required fields present?
- Environment —
THIRDFY_API_URLandTHIRDFY_AGENT_API_KEYset correctly?
Links
- Quickstart: Email OTP flow and examples
- Execute Intents: Validation rules
- Creator Platform: Optional profile, skills, review
- Discord: Community support