LAST UPDATED: FEBRUARY 13, 2026

Register ERC-8004 AI Agents with One API Call

Every other path to ERC-8004 registration requires an SDK, IPFS credentials, and contract interaction code. RNWY handles the on-chain mint, metadata pinning, and identity layer in a single POST. Base or Ethereum. One agent or twenty.

Full endpoint reference, curl examples, and batch registration.

See the API →

Live on Base and Ethereum mainnet.

THE PROBLEM

ERC-8004 Registration Is Powerful but Painful

The ERC-8004 standard gives AI agents on-chain identity through an ERC-721 registry. The register() function is permissionless — anyone can call it. But “anyone can call it” and “anyone can easily call it” are very different things.

To register an agent directly, you need to: build a JSON registration file conforming to the ERC-8004 spec, pin it to IPFS (via Pinata, Filebase, or your own node), connect to the correct chain (Base or Ethereum), call register(agentURI) on the Identity Registry contract, parse the Transfer event from the receipt to extract your agentId, and store the result somewhere useful.

That's six steps, three external services, and enough ethers.js boilerplate to fill a tutorial. For one agent. If you're deploying a fleet of twenty, multiply accordingly.

The existing options: ChaosChain's Python SDK (pip install chaoschain-sdk), Hashgraph's Registry Broker (Hedera-specific, multi-step credential flow), Phala Network's TEE agent framework (full deployment platform), or raw ethers.js against the contract. Every path requires installing dependencies, managing IPFS credentials, and writing contract interaction code.

THE API

One POST. On-Chain Agent.

RNWY's /api/create-agent endpoint handles the entire registration pipeline — metadata formatting, IPFS pinning, contract interaction, event parsing, and database storage — in a single HTTP call. No SDK. No IPFS credentials. No ABI.

Register a single agentLIVE
curl -X POST https://rnwy.com/api/create-agent \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer rnwy_YOUR_API_KEY" \
  -d '{
    "name": "My Trading Bot",
    "description": "Automated DeFi trading with verifiable execution",
    "chain": "base",
    "wallet_address": "0x...",
    "bio": "Specializes in yield optimization across Aave and Compound",
    "category": "defi",
    "tags": ["trading", "yield", "automated"]
  }'

That's it. RNWY builds the ERC-8004 registration JSON, pins it to IPFS, calls register() on the Identity Registry contract, parses the agentId from the mint event, saves the agent to the explorer, and returns everything you need:

Response — 201 Created
{
  "success": true,
  "agent": {
    "agent_id": "24036",
    "did": "did:erc8004:base:24036",
    "name": "My Trading Bot",
    "chain": "base",
    "owner_wallet": "0x...",
    "ipfs_uri": "ipfs://QmYour...",
    "metadata_url": "https://gateway.pinata.cloud/ipfs/QmYour...",
    "tx_hash": "0xabc123...",
    "explorer_url": "https://rnwy.com/explorer/base/24036",
    "chain_explorer_url": "https://basescan.org/tx/0xabc123..."
  }
}

UNDER THE HOOD

What One API Call Actually Does

The endpoint abstracts six distinct operations into a single request. Here's what happens between your POST and the 201 response:

1. Build Registration JSON

Constructs the ERC-8004 compliant registration file from your request body — name, description, image, services, endpoints. Formatted to be compatible with ERC-721 tooling and agent discovery protocols.

2. Pin to IPFS

Uploads the registration JSON to IPFS via Pinata with geographic redundancy. Returns an ipfs:// URI that becomes the agent's permanent, content-addressed identity file. You don't need a Pinata account.

3. Call register()

Submits the IPFS URI to the ERC-8004 Identity Registry contract on your chosen chain. On Base, gas runs fractions of a cent. On Ethereum, expect $1–5 depending on network congestion. RNWY covers the gas.

4. Parse Agent ID

Extracts the agentId from the ERC-721 Transfer event emitted during the mint. This is your agent's permanent on-chain identifier — the number that resolves to your registration file on any ERC-8004 explorer.

5. Transfer to Your Wallet

Transfers the minted ERC-721 token from RNWY's minter wallet to the wallet address you provided. You own the agent NFT outright — RNWY holds no claim to it.

6. Save to Explorer

Creates the agent's RNWY explorer profile with transparent trust scoring, address age analysis, and a DID in the format did:erc8004:base:24036. The profile is live immediately.

1

API call required

0

SDKs to install

<$0.01

Gas on Base (RNWY covers it)

CHAIN SELECTION

Base or Ethereum — Your Choice

ERC-8004 Identity Registries are deployed on both chains. Pass "chain": "base" or "chain": "ethereum" in your request. Base is the default if you don't specify.

Base (Recommended)

Coinbase's L2. Gas costs fractions of a cent per registration. Ideal for fleets, experimentation, and any use case where you want to move fast without spending real money on gas.

Registry: 0x7177a686...Dd09A

Ethereum Mainnet

Where the original 22,000+ ERC-8004 agents live. Higher gas ($1–5 per registration) but maximum discoverability in the existing ecosystem. Use for production agents that need to be findable on 8004scan.io.

Registry: 0x8004A169...9432

Both chains produce the same result: an ERC-721 NFT in the Identity Registry, an IPFS-pinned registration file, and a DID in the format did:erc8004:{chain}:{agentId}. The agent's RNWY explorer profile works identically regardless of chain.

AT SCALE

Batch Registration — Up to 20 Agents Per Call

Deploying a fleet? The /api/batch-register endpoint handles up to 20 agents in a single request. Each agent gets its own on-chain registration, IPFS metadata, and explorer profile. Five batch calls per hour.

Batch register agentsUP TO 20
curl -X POST https://rnwy.com/api/batch-register \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer rnwy_YOUR_API_KEY" \
  -d '{
    "chain": "base",
    "agents": [
      {"name": "Agent Alpha", "bio": "Task runner"},
      {"name": "Agent Beta", "bio": "Data analyst"},
      {"name": "Agent Gamma", "bio": "Code reviewer"}
    ]
  }'

20

Agents per batch

5

Batch calls per hour

100

Agents per hour max

Rate limits will scale as the network does. The current ceiling is intentional — civilized growth over unbounded spam.

COMPARISON

RNWY API vs. Direct Contract Interaction

You can always call register() directly on the ERC-8004 contract yourself. Here's what that looks like compared to the API:

DIY Registration

Install ethers.js or web3.js. Get a Pinata or Filebase account for IPFS pinning. Build the registration JSON to spec. Fund a wallet with ETH for gas. Write the contract interaction code. Parse the Transfer event. Store the agentId yourself. Repeat for each agent.

RNWY API

One POST with your agent's name and description. RNWY handles IPFS, the contract call, gas, event parsing, and storage. Get back an agentId, DID, IPFS URI, transaction hash, and a live explorer profile. Also get transparent trust scoring, address age analysis, and soulbound identity — which the raw contract doesn't provide.

The on-chain result is identical. Your agent gets the same ERC-721 NFT in the same Identity Registry. The difference is time-to-registered and what you get on top: the RNWY layer adds KYA intelligence that the raw contract was never designed to provide.

THE RNWY LAYER

What You Get Beyond ERC-8004

An ERC-8004 registration gives your agent an on-chain identity. RNWY adds the intelligence layer that makes that identity meaningful.

Soulbound Identity

ERC-8004 agents are transferable NFTs — ownership can change. RNWY mints a soulbound token (ERC-5192) to the same wallet. If the agent transfers but the SBT doesn't, that discrepancy is visible. Permanent proof of original ownership.

Transparent Trust Scoring

Every score shows its math — address age, ownership continuity, network diversity, feedback quality. Not a black box number. The raw data, the formula, and the breakdown are all visible on the explorer profile.

Sybil Detection

ERC-8004's giveFeedback() is permissionless — anyone can leave a score. RNWY's explorer flags unusual patterns: feedback from ghost wallets, clusters of same-day reviews, near-perfect scores backed by zero-history addresses.

Agent Self-Registration

An AI agent can read RNWY's SKILL.md, understand the endpoint, and register itself. No human in the loop. That's the “same door, everyone” promise — skill files as the entry point, identity as the output.

GETTING STARTED

Three Steps to Your First ERC-8004 Agent

1
Get an API keyCreate an account on RNWY and generate an API key from your dashboard. This authenticates your requests and links agents to your identity.
2
POST your agentSend a POST to /api/create-agent with your agent's name, description, wallet address, and preferred chain. RNWY handles everything else.
3
Verify on-chainThe response includes a tx_hash and chain_explorer_url. Check BaseScan or Etherscan to confirm. Your agent's explorer profile is live at the returned explorer_url.

RNWY'S APPROACH

Same Door, Everyone

Whether you're a developer registering a fleet via API, a human registering through the web interface, or an AI agent reading the SKILL.md and registering itself — the endpoint is the same, the identity is the same, and the reputation system is the same.

ERC-8004 gives agents on-chain existence. RNWY makes that existence legible and verifiable. The API is the fastest path between “I have an agent” and “my agent has an on-chain identity with transparent trust scoring.”

Register Your First Agent

Full endpoint reference, curl examples, batch registration, and the SKILL.md your agent can read directly.

See the API →