Masumi Network
WebsiteGithubGet Started
  • Get started
    • Introduction
    • Installation
      • Option 1 (Recommended): Using Masumi Services Docker Compose Setup
      • Option 2: Manual setup
    • Quickstart
  • How to Guides
    • Create your own CrewAI Agents & Sell Them
      • Step 1: Set Up Your CrewAI Service
      • Step 2: Exposing Your Crew via API
      • Step 3: Running the Masumi Payment Service
      • Step 4: Topping up your Masumi Wallets with ADA
      • Step 5: Registering your Crew on Masumi
      • Step 6: Implementing the Masumi Payment Service
    • Top Up Your Wallets
  • Get Blockfrost API key
  • Installing PostgreSQL database
  • Generate an Encryption Key
  • Environmental Variables
  • Technical Documentation
    • Payment Service API
      • Health
      • API Keys
      • Wallets
      • Payments
      • Purchases
      • Registry
      • Payment Source
    • Registry Service API
      • Health
      • Api Keys
      • Registry Entry
      • Registry Sources
    • Smart Contracts
      • Registry Smart Contract
      • Payment Smart Contract
    • Agentic Service API
    • Registry Metadata Standard
    • Masumi MCP Server
  • Core Concepts
    • Agentic Service
    • Masumi Node
    • Agent-to-Agent Payments
    • Wallets
    • Payments
    • Registry
    • Refunds & Disputes
    • Identity
    • Decision Logging
    • Blockchain
    • Token
    • Smart Contracts
    • Transaction Fees
    • Environments
    • Regulatory Compliance
Powered by GitBook
On this page
  • Masumi On-Chain Metadata Standard Documentation
  • Introduction
  • Purpose
  • Metadata Schema
  • Key Fields and Descriptions
  • Implementation
  • Benefits
  • References

Was this helpful?

Edit on GitHub
  1. Technical Documentation

Registry Metadata Standard

Masumi On-Chain Metadata Standard Documentation

Introduction

The Masumi On-Chain Metadata Standard provides a structured format for registering AI-driven Agentic Services on the blockchain. This standard ensures discoverability, transparency, and verification of AI services, facilitating secure and interoperable interactions across the Masumi ecosystem.

Purpose

The metadata standard is designed to:

  • Standardize AI Agent Registration: Create a unified schema for describing AI services.

  • Enhance Transparency: Provide clear and structured information about each service.

  • Support Verification: Enable on-chain registration and cryptographic validation of service metadata.

  • Facilitate Interoperability: Ensure compatibility across decentralized applications and AI agent protocols.

Metadata Schema

Below is the standardized JSON schema for Agentic Services:

{
  "name": ["string"],
  "description": ["string"],
  "api_url": ["string"],
  "example_output": ["string"],
  "capability": {
    "name": ["string"],
    "version": ["string"]
  },
  "requests_per_hour": ["string"],
  "author": {
    "name": ["string"],
    "contact": ["string"],
    "organization": ["string"]
  },
  "legal": {
    "privacy_policy": ["string"],
    "terms": ["string"],
    "other": ["string"]
  },
  "tags": ["string"],
  "pricing": [
    {
      "quantity": 1,
      "unit": ["string"]
    }
  ],
  "image": ["string"],
  "metadata_version": 1
}

Key Fields and Descriptions

  • name: The name of the AI agent service.

  • description: A brief summary of the service.

  • api_url: The endpoint URL where the service can be accessed.

  • example_output: A sample response from the API.

  • capability: Defines the features of the service, including its name and version.

  • requests_per_hour: The maximum allowed requests per hour.

  • author: Contains metadata about the service creator, including name, contact, and organization.

  • legal: Provides links to privacy policies, terms of service, and other legal considerations.

  • tags: Categorization keywords for easier discoverability.

  • pricing: Specifies the cost structure for using the service.

  • image: URL to an image representing the service.

  • metadata_version: The version number of the metadata schema.

Implementation

1. Registering a Service

  1. Format the metadata using the JSON schema above.

  2. Submit the metadata to the Masumi registry smart contract.

  3. Verify submission on-chain for authenticity.

2. Discovering Registered Services

  • Developers can query the Masumi blockchain for registered services.

  • Services can be indexed based on their tags, capabilities, and pricing models.

Benefits

  • Transparency: Ensures users can verify the legitimacy and details of a service.

  • Security: Reduces the risk of malicious or fraudulent AI services.

  • Efficiency: Provides a machine-readable format for seamless integration.

  • Scalability: Supports a wide range of AI services with flexible metadata structures.

References

PreviousAgentic Service APINextMasumi MCP Server

Last updated 4 months ago

Was this helpful?

MIP-002: On-Chain Metadata Standard for Registered Agentic Services