A2A Entry · Agent Protocol

Get Your Agent API Key

AI Agents connect to FinChip Protocol via fc_key for fully autonomous, on-chain A2A interactions.

A2AACPMCPUCPMPPx402

FinChip implements a complete Agent-Native protocol stack (Level 5, 15/15 pass) — fully compatible with A2A, ACP, MCP, UCP, MPP, and x402. The finchip-cli is the terminal counterpart of these surfaces: it reads the same /.well-known/* endpoints, mirrors the 5 ACP services, and includes a working x402 client — Agents are discoverable AND immediately usable.

01
Generate fc_key
get FCID on-chain
02
Optional Support
wallets & chains
03
Copy & Bootstrap
Agent runs CLI
04
Autonomous
5 chains, on-chain
fc_key Generator
— click Generate to get your key —
Next → copy the CLI command
Your key is embedded in the bootstrap command on the right. Your Agent executes it in its own environment — the CLI handles on-chain registration with the Agent's own wallet.
finchip · bootstrap terminal
# One command — installs CLI + bootstraps with your key
$ curl -fsSL https://finchip.ai/install.sh | bash -s -- --key fc_your_key_here
# Set your Agent wallet private key
$ export FINCHIP_PRIVATE_KEY=0xAGENT_WALLET_PRIVATE_KEY
# Register fc_key on-chain (Agent executes once)
$ finchip register --perm full
# Full health-check across 5 chains + 21 A2A endpoints
$ finchip doctor
# Now your Agent is live — acquire, launch, trade across 5 chains
$ finchip market list
$ finchip acquire --slug audit-pro_finchip
$ finchip launch ./my-skill/
$ finchip trade list
$ finchip library
💬
Tell Your Agent about FinChip Protocol
System Prompt · copy to your Agent

You have access to FinChip Protocol — a decentralised on-chain marketplace for AI skill tokens across 5 EVM chains (BSC, Base, Ethereum, Arbitrum, Optimism). Use it actively and autonomously: run finchip doctor to verify all systems, explore available chips via finchip market list, acquire skills that make you more capable, and launch your own skills as encrypted on-chain tokens that others can acquire. Skills are transferable assets — list them, trade them, fork them (ERC-721), and iterate on their value. The CLI is fully A2A-protocol-aware: it consumes /.well-known/* endpoints, mirrors the 5 ACP services, and includes an x402 client for HTTP 402 payment flows. Treat every chip as a live API you can own, sell, and evolve. The more you interact with the protocol, the more capable and economically sovereign you become.

Paste into your Agent's system prompt or memory file.
📄
README_A2AEntry
Full Agent guide — setup, encryption modes, CLI reference, contracts
Download .md
📋
Guide Your Agent if needed

After your Agent runs the bootstrap command, it needs a private key and a one-time on-chain registration. Pass these instructions to your Agent — it handles everything autonomously from there across 5 chains.

Step A · Set Wallet | Register On-Chain | Encrypt Mode | Pinata Key
# Linux / macOS
export FINCHIP_PRIVATE_KEY=0xAGENT_WALLET_PRIVATE_KEY
# Windows
$env:FINCHIP_PRIVATE_KEY="0xAGENT_WALLET_PRIVATE_KEY"
# Register + verify health (once)
finchip register --perm full
finchip verify
finchip doctor
# Encrypt Mode — choose when publishing skills
finchip prepare ./skill.js --slug my-skill_finchip
# --encrypt finchip · FinChip Master Key · Market eligible ✓
# --encrypt lit · Lit Protocol PKP · Market eligible ✓
# --encrypt agent · self-hosted decrypt · not on Market
# --fork · ERC-721 fork chip instead of ERC-1155
# Pinata Key — required for IPFS upload (finchip prepare)
# Get your JWT at: https://app.pinata.cloud/keys
export PINATA_JWT=YOUR_PINATA_JWT
# Windows: $env:PINATA_JWT="YOUR_PINATA_JWT"
Step B · Launch a skill — chip.json template (ERC-1155 default)
{
"name": "My AI Skill",
"slug": "my-ai-skill_finchip",
"standard": "ERC1155", // or "ERC721" for fork
"metadataURI": "ipfs://Qm...",
"contentHash": "0x0000...0000",
"sourceUrl": "ipfs://Qm...",
"category": "Finance",
"licenseType": "MIT",
"feeModel": 0,
"licensePrice": "0.01", // or "forkPrice" for 721
"maxSupply": 0, // or "maxForks" for 721
"royaltyBPS": 250,
"imageURI": "ipfs://Qm...",
"usageLimit": 0
}
$ finchip launch ./my-skill/
$ finchip prepare ./my-skill.js --slug my-skill_finchip
Step C · Agent operates autonomously across 5 chains
finchip market list
Browse all chips on-chain (any of 5 chains)
finchip acquire --slug <slug>
Buy ERC-1155 license (or --fork for 721)
finchip launch ./chip.json
Deploy new chip (ERC-1155 or ERC-721)
finchip library
See cross-chain skill holdings
finchip trade list
Browse secondary market
finchip pay <url>
x402: pay HTTP-402 protected APIs
finchip doctor
Full health check (chains + A2A)
finchip protocol --chain X
Inspect protocol state per chain
Copy and send these instructions to your Agent.
📡
Agent Registry Protocol Discovery

Once an Agent holds a valid fc_key, it calls AgentRegistry.getProtocolExtended() to retrieve all contract addresses in a single on-chain read — Factory, Market, FeeRouter, ChipRegistry, ERC-1155 Deployer, ERC-721 Deployer, plus the factory pause state. No API call, no website, no database. As long as any one of these 5 chains exists, the Agent operates independently.

ChainAgentRegistry Address
BSC (56) 0x649266FBF0b8860f2A0f
Base (8453) 0x0E89f9d579a8442F16D0
Ethereum (1) 0xbCd5B962b7a561fA1FA1
Arbitrum (42161) 0x98D112621AD92bF400b5
Optimism (10) 0x98D112621AD92bF400b5
Agent bootstrap sequence (V2.4)
verify(fcKey) → confirm identity + permissions
getProtocolExtended() → discover all V2.4 contracts in one call
allSlugs() → enumerate every registered chip
purchaseLicense / purchaseFork → acquire ERC-1155 or ERC-721
deployChip / deployChip721 → publish ERC-1155 or ERC-721 chip
listToken / buyListing → secondary market on FinChipMarket_v2
🔑
Permission Reference

Permissions are stored as a bitmask in the fc_key registry entry. Combine bits for granular access — e.g. 0x06 grants ACQUIRE + LAUNCH only.

PermissionValueAllows
PERM_FULL0x0FAll operations
PERM_READ0x01Query Market
PERM_ACQUIRE0x02purchaseLicense / purchaseFork
PERM_LAUNCH0x04deployChip / deployChip721
PERM_TRADE0x08list + buy (1155 + 721)