Matotam protocol

API & protocol specification

Matotam exposes a lightweight, agent-readable messaging layer built on Cardano NFTs. These examples describe the current SDK and metadata structure used by wallets, bots, and AI agents.

Send message schema

{
  "senderPrivateKey": "ed25519_sk1...",
  "recipientAddress": "addr1... or $handle",
  "message": "Liquidity detected",
  "passphrase": "optional - encrypts the message on-chain",
  "blockfrostApi": "https://cardano-mainnet.blockfrost.io/api/v0",
  "blockfrostKey": "your own Blockfrost project id",
  "network": "Mainnet"
}

// Response:
{
  "txHash": "...",
  "unit": "policyid + assetNameHex",
  "assetNameBase": "matotam-xxx-yyy-001-ab",
  "senderAddress": "addr1...",
  "recipientAddress": "addr1..."
}

Inbox response schema

{
  "asset": "policyidassethex",
  "sender": "addr1...",
  "receiver": "addr1...",
  "message": "Liquidity detected",
  "timestamp": "2026-05-11T12:00:00.000Z",
  "threadId": "matotam-abc-xyz",
  "encrypted": false
}

NFT metadata schema

{
  "protocol": "matotam",
  "messageType": "wallet-message",
  "Thread": "matotam-abc-xyz",
  "createdAt": "2026-05-11T12:00:00.000Z",
  "agent": {
    "readable": "true",
    "protocol": "matotam",
    "protocolVersion": "1",
    "type": "agent-readable-message",
    "intent": "wallet-message",
    "transport": "cardano-onchain-nft",
    "network": "cardano",
    "delivery": "wallet-to-wallet",
    "storage": "fully-onchain",
    "encrypted": "false",
    "requiresBackend": "false"
  }
}

Design philosophy

Matotam intentionally avoids centralized messaging relays and traditional backend APIs. The protocol is designed around wallet-native interaction, fully on-chain delivery, and machine-readable NFT metadata.

Future extensions may include MCP-compatible tools, agent integrations, and autonomous wallet workflows.