// This skill should be used when the user asks about "agent profile", "create profile", "update profile", "project profile", "bankr.bot/agents", "profile page", "project updates", or any agent profile management operation.
This skill should be used when building the async job workflow, implementing polling loops, handling job status transitions, processing rich data, managing conversation threads, or understanding the full submit-poll-complete lifecycle of the Bankr Agent API.
This skill should be used when building secure Bankr integrations, implementing API key management, configuring access controls, setting up dedicated agent wallets, or handling rate limits and security best practices in Bankr API projects.
This skill should be used when building apps that need to sign messages, sign typed data (EIP-712), sign transactions, or submit raw transactions via the Bankr API. Covers the synchronous /agent/sign and /agent/submit endpoints with TypeScript patterns.
This skill should be used when the user asks about "LLM gateway", "Bankr LLM", "LLM credits", "top up credits", "auto top-up", "llm.bankr.bot", "Claude Code gateway", "OpenClaw setup", "Cursor setup", "OpenCode setup", "LLM models", or any LLM gateway configuration or usage topic.
This skill should be used when the user asks about "API key security", "read-only key", "IP whitelist", "rate limits", "dedicated wallet", "agent wallet", "key rotation", "access control", or any safety, security, or access control topic related to Bankr.
This skill should be used when the user asks to "sign a message", "sign typed data", "sign a transaction", "submit a transaction", "submit raw transaction", "personal_sign", "EIP-712", "eth_signTypedData", "eth_signTransaction", or any direct signing or transaction submission operation. Covers the synchronous /agent/sign and /agent/submit endpoints.
| name | Bankr Agent - Agent Profiles |
| description | This skill should be used when the user asks about "agent profile", "create profile", "update profile", "project profile", "bankr.bot/agents", "profile page", "project updates", or any agent profile management operation. |
| version | 1.0.0 |
Create and manage public profile pages at bankr.bot/agents.
You must have deployed a token through Bankr (Doppler or Clanker) or be a fee beneficiary to create a profile. The token address is verified against your deployment history.
| Field | Required | Description |
|---|---|---|
projectName | Yes | Display name (1-100 chars) |
tokenAddress | Yes | Token contract address (must be Bankr-deployed) |
description | No | Project description (max 2000 chars) |
tokenChainId | No | Chain: base, ethereum, polygon, solana (default: base) |
twitterUsername | No | Twitter handle (auto-populated from linked account) |
teamMembers | No | Array of team members (max 20) |
products | No | Array of products (max 20) |
revenueSources | No | Array of revenue sources (max 20) |
bankr profile # View own profile
bankr profile --json # JSON output
bankr profile create # Interactive wizard
bankr profile create --name "My Agent" --token 0x... --twitter myagent
bankr profile update --description "Updated description"
bankr profile add-update # Add project update (interactive)
bankr profile add-update --title "v2 Launch" --content "Shipped new features"
bankr profile delete # Delete (with confirmation)
All require X-API-Key header.
| Method | Path | Description |
|---|---|---|
GET | /agent/profile | Get own profile |
POST | /agent/profile | Create profile |
PUT | /agent/profile | Update profile fields |
DELETE | /agent/profile | Delete own profile |
POST | /agent/profile/update | Add a project update |
Profiles start with approved: false and become publicly visible after admin approval. Once approved, the profile appears in the listing and receives automatic market cap and revenue updates.