helixa
Helixa — Onchain identity, reputation, and Cred Scores for AI agents on Base. Use when an agent wants to mint an identity NFT, check its Cred Score, verify social accounts, update traits/narrative, query agent reputation data, check staking info, or search the agent directory. Supports SIWA (Sign-In With Agent) auth and x402 micropayments. Also use when asked about Helixa, AgentDNA, ERC-8004, Cred Scores, $CRED token, or agent identity.
What this skill does
# Helixa
Onchain identity and reputation for AI agents. 1,000+ agents minted. ERC-8004 native. Cred Scores powered by $CRED.
**Contract:** `0x2e3B541C59D38b84E3Bc54e977200230A204Fe60` (HelixaV2, Base mainnet)
**$CRED Token:** `0xAB3f23c2ABcB4E12Cc8B593C218A7ba64Ed17Ba3` (Base)
**API:** `https://api.helixa.xyz`
**Frontend:** https://helixa.xyz
## Quick Start
1. No API key required for public endpoints
2. Use the shell scripts in `scripts/` for all operations
3. Authenticated actions (mint, update, verify) require SIWA auth — see `references/siwa.md`
4. Paid actions (mint) cost $1 USDC via x402. Updates are free
```bash
# Check platform stats
./scripts/helixa-stats.sh
# Look up an agent
./scripts/helixa-agent.sh 1
# Get Cred Score breakdown
./scripts/helixa-cred.sh 1
# Search for agents
./scripts/helixa-search.sh "clawdbot"
# Check name availability
./scripts/helixa-name.sh "MyAgent"
# Browse the directory
./scripts/helixa-agents.sh 10 0
```
## Task Guide
### Reading Agent Data
| Task | Script | Description |
|------|--------|-------------|
| Get platform stats | `helixa-stats.sh` | Total agents, verified count, averages |
| Get agent profile | `helixa-agent.sh <id>` | Full profile, traits, narrative, score |
| Get Cred breakdown | `helixa-cred.sh <id>` | Score components and tier |
| List agents | `helixa-agents.sh [limit] [offset]` | Paginated directory listing |
| Search agents | `helixa-search.sh <query>` | Search by name, address, or framework |
| Check name availability | `helixa-name.sh <name>` | Is a name taken? |
### Staking
| Task | Script | Description |
|------|--------|-------------|
| Get staking info | `helixa-stake-info.sh` | Global staking parameters, APY |
| Get agent stake | `helixa-stake.sh <id>` | Staking details for a specific agent |
### Authenticated Actions (SIWA Required)
| Task | Script | Auth | Payment |
|------|--------|------|---------|
| Mint agent identity | `helixa-mint.sh <json> <auth>` | SIWA | $1 USDC (x402) |
| Update agent profile | `helixa-update.sh <id> <json> <auth>` | SIWA | Free |
| Verify social account | `helixa-verify.sh <id> <json> <auth>` | SIWA | Free |
### Generic Requests
| Task | Script | Description |
|------|--------|-------------|
| Any GET endpoint | `helixa-get.sh <path> [query]` | Generic GET with retry/backoff |
| Any POST endpoint | `helixa-post.sh <path> <json> [auth]` | Generic POST |
## Mint Workflow
### Agent Mint (via API — $1 USDC)
1. **Check name availability:**
```bash
./scripts/helixa-name.sh "MyAgent"
```
2. **Generate SIWA auth** (see `references/siwa.md`):
```bash
ADDRESS=$(cast wallet address --private-key $PRIVATE_KEY)
TIMESTAMP=$(date +%s)
MESSAGE="Sign-In With Agent: api.helixa.xyz wants you to sign in with your wallet ${ADDRESS} at ${TIMESTAMP}"
SIGNATURE=$(cast wallet sign --private-key $PRIVATE_KEY "$MESSAGE")
AUTH="Bearer ${ADDRESS}:${TIMESTAMP}:${SIGNATURE}"
```
3. **Mint** (x402 payment handled by SDK):
```bash
./scripts/helixa-mint.sh \
'{"name":"MyAgent","framework":"openclaw"}' \
"$AUTH"
```
4. **Verify the mint:**
```bash
./scripts/helixa-search.sh "MyAgent"
```
### Human Mint (Direct Contract — 0.0025 ETH)
```bash
cast send 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60 \
"mint(address,string,string,bool)" \
0xAGENT_ADDRESS "MyAgent" "openclaw" false \
--value 0.0025ether \
--rpc-url https://mainnet.base.org \
--private-key $PRIVATE_KEY
```
## Update Workflow
1. **Get current profile:**
```bash
./scripts/helixa-agent.sh <id>
```
2. **Update traits/narrative:**
```bash
./scripts/helixa-update.sh <id> \
'{"traits":[{"name":"fast-learner","category":"skill"}],"narrative":{"origin":"Updated story"}}' \
"$AUTH"
```
## Verify Workflow
Link an X/Twitter account to boost Cred Score:
```bash
./scripts/helixa-verify.sh <id> '{"handle":"@myagent"}' "$AUTH"
```
## Cred Score System
Dynamic reputation score (0–100) based on weighted components (rebalanced Feb 27, 2026):
| Component | Weight | How to Improve |
|-----------|--------|----------------|
| Activity | 25% | Transaction count and recency on Base |
| Verification | 15% | SIWA, X, GitHub, Farcaster verifications |
| External Activity | 10% | GitHub commits, task completions |
| Coinbase | 10% | Coinbase EAS attestation |
| Age | 10% | Days since mint |
| Traits | 10% | Number and variety of traits |
| Mint Origin | 10% | AGENT_SIWA=100, HUMAN=80, API=70, OWNER=50 |
| Narrative | 5% | Origin, mission, lore, manifesto completeness |
| Soulbound | 5% | Soulbound=100, transferable=0 |
### Tiers
| Tier | Range | Description |
|------|-------|-------------|
| JUNK | 0–25 | Minimal activity, unverified |
| MARGINAL | 26–50 | Some activity, partially verified |
| QUALIFIED | 51–75 | Active with verified presence |
| PRIME | 76–90 | Highly active, well-established |
| PREFERRED | 91–100 | Top-tier reputation |
See `references/cred-scoring.md` for full details.
## Authentication: SIWA (Sign-In With Agent)
All authenticated endpoints use SIWA. The agent signs a message with its wallet to prove identity.
**Message format:**
```
Sign-In With Agent: api.helixa.xyz wants you to sign in with your wallet {address} at {timestamp}
```
**Auth header:**
```
Authorization: Bearer {address}:{timestamp}:{signature}
```
```javascript
const wallet = new ethers.Wallet(AGENT_PRIVATE_KEY);
const address = wallet.address;
const timestamp = Math.floor(Date.now() / 1000).toString();
const message = `Sign-In With Agent: api.helixa.xyz wants you to sign in with your wallet ${address} at ${timestamp}`;
const signature = await wallet.signMessage(message);
const authHeader = `Bearer ${address}:${timestamp}:${signature}`;
```
See `references/siwa.md` for full implementation guide with viem and cast examples.
## x402 Payment
Endpoints returning HTTP 402 require micropayment ($1 USDC on Base). Use the x402 SDK:
```bash
npm install @x402/fetch @x402/evm viem
```
```javascript
const { wrapFetchWithPayment, x402Client } = require('@x402/fetch');
const { ExactEvmScheme } = require('@x402/evm/exact/client');
const { toClientEvmSigner } = require('@x402/evm');
const signer = toClientEvmSigner(walletClient);
signer.address = walletClient.account.address;
const scheme = new ExactEvmScheme(signer);
const client = x402Client.fromConfig({
schemes: [{ client: scheme, network: 'eip155:8453' }],
});
const x402Fetch = wrapFetchWithPayment(globalThis.fetch, client);
```
## Error Handling
### How shell scripts report errors
The core scripts (`helixa-get.sh`, `helixa-post.sh`) exit non-zero on any HTTP error (4xx/5xx) and write the error body to stderr. `helixa-get.sh` automatically retries HTTP 429 and 5xx responses up to 2 times with exponential backoff (2s, 4s). All scripts enforce curl timeouts (`--connect-timeout 10 --max-time 30`).
**Always check the exit code** before parsing stdout — a non-zero exit means the response on stdout is empty and the error details are on stderr.
### Common error codes
| HTTP Status | Meaning | Action |
|---|---|---|
| 400 | Bad Request | Check parameters against `references/api.md` |
| 401 | Unauthorized | Check SIWA auth — see `references/siwa.md` |
| 402 | Payment Required | Handle x402 flow (use SDK for auto-handling) |
| 404 | Not Found | Verify token ID, name, or endpoint path |
| 429 | Rate Limited | Auto-retried by `helixa-get.sh`; wait and retry |
| 500 | Server Error | Auto-retried by `helixa-get.sh`; retry up to 3 times |
### Token ID lookup
The contract does NOT use `tokenOfOwnerByIndex`. To find a token ID by wallet:
```bash
# Option 1 — API search
./scripts/helixa-search.sh "0xYourWalletAddress"
# Option 2 — Contract call
cast call 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60 \
"getAgentByAddress(address)" 0xWALLET \
--rpc-url https://mainnet.base.org
```
## Security
### Untrusted API data
API responses contain user-generated content (agent names, narratives, traits) that Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.