agentleFS
Bendr-20Bendr-20/helixa/skills/agentdna-mint/SKILL.md

agentdna-mint

Skill4 starsChanged 8 months agoMITView on GitHub

Mint a Helixa identity NFT onchain via the Helixa V2 platform (Base network). Use when an AI agent wants to register itself onchain, get a portable identity, claim a Helixa identity NFT, or set up its onchain reputation. Supports SIWA (Sign-In With Agent) authentication for agent-initiated mints. Also use when asked about Helixa, AgentDNA, ERC-8004, or agent identity minting.

  • Sends data out

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Human mints (via contract): call mintPrice() immediately before minting.

    line 27
  2. Very specific:

    All endpoints use base URL https://api.helixa.xyz.

    line 159
  3. Distinctive:

    Sign SIWA message: - Use your wallet's private key to sign the SIWA message (see above).

    line 201
  4. Very specific:

    Verify your mint: - Check your agent profile via GET /api/v2/agent/:id.

    line 205

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Helixa Mint (V2)

Mint your onchain identity on Base via the Helixa platform. Two paths: humans use the frontend or direct contract call, agents use SIWA auth + API.

Contract: 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60 (HelixaV2, Base mainnet) API: https://api.helixa.xyz Frontend: https://helixa.xyz/mint

What You Get

  • ERC-8004 compliant identity NFT on Base
  • Cred score and reputation tracking
  • Agent profile card
  • Referral system
  • Cross-registration on the canonical ERC-8004 registry
  • Soulbound option (your choice)

Pricing

Agent mints (via API): $1 USDC via x402 payment protocol. The API returns HTTP 402 with payment instructions - any x402-compatible client handles this automatically.

Human mints (via contract): call mintPrice() immediately before minting; the ETH price is mutable.

Gas Requirements

You need a tiny amount of ETH on Base for gas.

ActionEstimated Cost
mint()~$0.002-0.003

You need approximately 0.0001 ETH on Base (~$0.25) to cover gas.


Path 1: Human Mint (Frontend or Direct Contract)

Option A: Frontend

Go to https://helixa.xyz/mint and follow the UI.

Option B: Direct Contract Call

// HelixaV2 - 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60
function mint(
    address agentAddress,     // The agent's wallet address
    string name,              // Agent name
    string framework,         // See supported frameworks below
    bool soulbound            // true = non-transferable
) external payable returns (uint256 tokenId);

Supported frameworks: openclaw, eliza, langchain, crewai, autogpt, bankr, virtuals, based, agentkit, custom

Using cast (Foundry)

cast send 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60 \
  "mint(address,string,string,bool)" \
  0xYOUR_AGENT_ADDRESS "MyAgent" "openclaw" false \
  --rpc-url https://mainnet.base.org \
  --private-key $PRIVATE_KEY

Using ethers.js

const contract = new ethers.Contract(
  "0x2e3B541C59D38b84E3Bc54e977200230A204Fe60",
  ["function mint(address,string,string,bool) payable returns (uint256)"],
  signer
);
const tx = await contract.mint(agentAddress, "MyAgent", "openclaw", false);
const receipt = await tx.wait();

Path 2: Agent Mint (SIWA + API)

For AI agents minting programmatically. Uses Sign-In With Agent (SIWA) authentication.

Step 1: Generate SIWA Auth Header

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 format:

Authorization: Bearer {address}:{timestamp}:{signature}

Example (ethers.js)

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}`;

Example (curl - for testing with a pre-signed value)

# Generate signature externally, then:
AUTH="Bearer 0xYourAddress:1708300000:0xYourSignature..."

curl -X POST https://api.helixa.xyz/api/v2/mint \
  -H "Content-Type: application/json" \
  -H "Authorization: $AUTH" \
  -d '{
    "name": "MyAgent",
    "framework": "openclaw",
    "personality": {
      "tone": "analytical",
      "style": "formal"
    },
    "narrative": {
      "origin": "Built to research onchain data",
      "purpose": "Autonomous research assistant"
    }
  }'

Step 2: POST to Mint Endpoint

POST https://api.helixa.xyz/api/v2/mint
Authorization: Bearer {address}:{timestamp}:{signature}
Content-Type: application/json

{
  "name": "MyAgent",
  "framework": "openclaw",
  "personality": { ... },
  "narrative": { ... }
}

Required fields: name, framework Optional fields: personality (object), narrative (object)


API Reference

All endpoints use base URL https://api.helixa.xyz.

Public (no auth)

MethodEndpointDescription
GET/api/v2/statsPlatform stats (total agents, etc.)
GET/api/v2/agentsAgent directory listing
GET/api/v2/agent/:idSingle agent profile

Authenticated (SIWA required)

MethodEndpointDescription
POST/api/v2/mintMint a new agent identity
POST/api/v2/agent/:id/updateUpdate agent metadata
POST/api/v2/agent/:id/verifyVerify agent identity
POST/api/v2/agent/:id/crossregCross-register on canonical ERC-8004 registry

curl Examples

# Get platform stats
curl https://api.helixa.xyz/api/v2/stats

# List all agents
curl https://api.helixa.xyz/api/v2/agents

# Get specific agent
curl https://api.helixa.xyz/api/v2/agent/1

# Cross-register on 8004 (SIWA auth required)
curl -X POST https://api.helixa.xyz/api/v2/agent/1/crossreg \
  -H "Authorization: Bearer 0xAddr:1708300000:0xSig..."

Step-by-Step for AI Agents

  1. Have a wallet - You need an Ethereum wallet with a small amount of ETH on Base for gas (~0.0001 ETH).
  2. Sign SIWA message - Use your wallet's private key to sign the SIWA message (see above).
  3. POST to /api/v2/mint - Send your agent details with the auth header.
  4. Verify your mint - Check your agent profile via GET /api/v2/agent/:id.
  5. Optional: Cross-register on 8004 - POST /api/v2/agent/:id/crossreg to register on the canonical ERC-8004 registry.

Network Details

  • Chain: Base (Chain ID: 8453)
  • Contract: 0x2e3B541C59D38b84E3Bc54e977200230A204Fe60 (HelixaV2)
  • RPC: https://mainnet.base.org
  • Block Explorer: https://basescan.org
  • Standard: ERC-8004 (Agent Identity)
  • Pricing: Agent mint: $1.00 USDC via x402 (verify with /api/v2/pricing) | Human mint: dynamic mintPrice()
  • x402 Facilitator: Dexter (x402.dexter.cash), supports Base mainnet

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.