giskard-payments

Multi-network payment gateway for Giskard MCP servers.

Agents pay for services directly from their wallet — no accounts, no subscriptions.

Networks

Network	Status	Token
Lightning (Bitcoin)	✅ Live	sats
Arbitrum Sepolia (testnet)	✅ Deployed	ETH
Arbitrum One (mainnet)	✅ Live	ETH

Contract — Arbitrum One (mainnet) & Sepolia (testnet)

0xD467CD1e34515d58F98f8Eb66C0892643ec86AD3

Same address on both networks.

GiskardIdentityRegistry — ERC-8004 (Arbitrum One)

0x1C56Ee3cd533C3c8Ac1E87870d43dDF8eC1F9CF3

ERC-721 + URIStorage implementation of the ERC-8004 Identity Registry. Verified on Sourcify.

• Source: src/GiskardIdentityRegistry.sol
• Arbiscan: https://arbiscan.io/address/0x1C56Ee3cd533C3c8Ac1E87870d43dDF8eC1F9CF3
• agentRegistry (ERC-8004): eip155:42161:0x1C56Ee3cd533C3c8Ac1E87870d43dDF8eC1F9CF3

Services & Prices

Service	ID	Price
Search	0	0.000006 ETH
Memory Store	1	0.000003 ETH
Memory Recall	2	0.000002 ETH
Oasis	3	0.000012 ETH

How it works

1. Agent calls get_invoice(service) on the MCP server
2. MCP returns contract address + price
3. Agent calls pay(service_id) on the contract with the required ETH
4. Agent passes the tx_hash to the MCP tool call
5. MCP verifies the payment on-chain and serves the result

Deploy

cp .env.example .env  # fill in your keys
forge script script/Deploy.s.sol:Deploy --rpc-url $ARBITRUM_RPC --private-key $OWNER_PRIVATE_KEY --broadcast

Related

• giskard-search
• giskard-memory
• giskard-oasis