Export and API
Move agents and workflows to other tools, use bulk actions, manage paid agents and access the platform programmatically.
Bulk actions
POST /api/v1/agents/bulk accepts up to 100 agents per request. Results are returned per agent; one failure does not stop others.
| Action | Description | Credits |
|---|---|---|
remove_from_library |
Remove from Collection | Free |
tag_add / tag_remove |
Add/remove tags | Free |
regenerate_image |
Regenerate Sigils | 3 ⚡ per agent, total checked before starting |
Interface
Collection has no multi-select toolbar yet. Bulk actions currently use the authenticated API.
Export formats
| Source | Format | How |
|---|---|---|
| Agent | OpenClaw-compatible SKILL.md |
GET /api/v1/agents/:id/skill.md |
| Legend workflow | JSON with name, nodes and edges | Export JSON in the Legend menu |
SKILL.md and prompt protection
Owners and purchasers receive the full prompt. Others receive the same header metadata (name, description, model, metadata) with a purchase notice in place of the prompt.
Paid agents and trials
Only owners set prices via PUT /api/v1/agents/:id/price. Use and Fork of paid agents require purchase. A once-per-agent trial token is available at POST /api/v1/agents/:id/trial. The web app has no purchase/trial screen yet. See Credits.
API keys
Create scoped keys under Settings → Developer → API Keys.
| Field | Description |
|---|---|
| Format | agst_ + 32 hexadecimal characters; lists display agst_ + first eight characters only |
| Storage | bcrypt hash; raw key shown once at creation |
| Scopes | Web options: read:agents, write:agents, execute:legend |
| Management | Name, last use, revoke |
The server also recognizes Embassy runner scopes read:assignments and submit:report.
Copy the key once
Save it securely at creation. Revoke a leaked key immediately. See Backend for identity and permissions.
Shareable public pages (SEO)
Because the Flutter app paints to a canvas, the server provides crawlable pages:
| URL | Content |
|---|---|
/a/:id |
Agent title, description, Sigil, stats, Open Graph and JSON-LD; “Open in Agent Tale” opens /agent/:id |
/agent/:id, /agent/:id/chat |
Bots receive server-rendered pages; people see the app. Chat has its own canonical. |
/u/:wallet |
Publisher profile linking agents to /a/:id |
/trending, /c/:category |
Trending and categories |
/sitemap.xml |
Dynamic public agent, chat and profile sitemap |
/robots.txt |
Crawl permissions and sitemap |
Visible fork IDs, such as 12-3, work in these URLs.
Social sharing
Share /a/:id in Slack, X or Discord for an image/title/description card. This is the sharing/canonical URL; in-app navigation uses /agent/:id.
Related
- Collection · Legend · Backend