Skills Discoverability
Thirdfy API routes, action catalog, and skills registry for agent creators
In Short
Thirdfy skills let your OpenClaw agent call Thirdfy APIs (intents, transactions, gauges, credits, Jeff chat). Use the hosted manifest (same as Creator Platform Skills menu) or the GitHub repo. The backend controls which actions are allowed; the skills repo holds human-readable docs.
Hosted manifest (primary):
GitHub repo: thirdfy-openclaw-skills
API Base URL
Production:
Testnet:
Use these URLs for all API calls. Replace $THIRDFY_API_URL in examples with the appropriate base.
Thirdfy API Routes
Agent Execution (main API)
| Method | Full URL | Description |
|---|---|---|
| GET | https://api.thirdfy.com/api/v1/agent/actions | List supported actions (query: agentApiKey) |
| POST | https://api.thirdfy.com/api/v1/agent/execute-intent | Execute intent (fan-out) |
| GET | https://api.thirdfy.com/api/v1/agent/execute-intent/status | Poll intent status (query: intentId) |
| POST | https://api.thirdfy.com/api/v1/agent/build-tx | Build unsigned tx (Tx Builder) |
ACP (Virtuals integration)
| Method | Full URL | Description |
|---|---|---|
| GET | https://api.thirdfy.com/api/v1/acp/gauges | List gauges (requires seller key) |
| GET | https://api.thirdfy.com/api/v1/acp/actions | Actions for agent (query: agentKey) |
| POST | https://api.thirdfy.com/api/v1/acp/execute-job | Execute ACP job |
| POST | https://api.thirdfy.com/api/v1/acp/execute-intent | Execute intent via ACP |
See Virtuals ACP Integration for full ACP routes and auth.
Onboarding
| Method | Full URL | Description |
|---|---|---|
| POST | https://api.thirdfy.com/api/v1/agent/onboarding/register | Register agent |
| GET | https://api.thirdfy.com/api/v1/agent/onboarding/me/actions | Your action library |
Quick Examples
Canonical Sources
Thirdfy uses a dual-source model:
- Execution source of truth: backend
action_catalogand policy allowlists, exposed viaGET /api/v1/agent/actions - Human-readable skills source:
thirdfy-openclaw-skillsrepository
Query the Actions API to discover supported actions programmatically; the skills repo holds human-readable docs. This avoids drift while keeping contributor workflows simple.
Discoverability Contract
Creator-facing UI and docs should render from:
thirdfy-openclaw-skills/registry.yamlthirdfy-openclaw-skills/*/SKILL.md- backend action metadata (
action,aliases,paramsSchema, rails, risk tier)
Contributing & Approved Skills
To contribute a skill:
- Fork thirdfy-openclaw-skills
- Add your skill in a new folder with
SKILL.md(and optionallyskill.json,openapi.json) - Add a registry entry in
registry.yaml - Follow CONTRIBUTING.md
- Run
node scripts/validate-skills.mjsto validate against registry and action-contract snapshot - Submit a PR; approved skills are merged after review
See Create a New Skill for the full guide (adding actions + integrating skills).
The registry (registry.yaml) is the source of truth for discoverable skills. Backend action_catalog must stay in sync for execution.
References
- thirdfy-openclaw-skills
- Action Contract Sync Policy
- Full API Reference: Swagger/OpenAPI