Metaorcha

Developer Docs

architecture · spec · sdk

emerge.yaml Spec5 min read

emerge.yaml Spec & Schema

Every agent in Metaorcha is declared via a versioned emerge.yaml manifest.

emerge.yaml Manifest Specification

#

emerge.yaml is the agent manifest filename — the versioned contract between an agent and the Metaorcha registry (identity, skills, protocol, endpoints). It is not the product name and not the CLI. The public CLI is orcha-sdk; the Python import path is still emerge.

The manifest is the standardized contract between agents and the Metaorcha registry. It defines the agent's identity, capabilities, protocol, and endpoints.

Full Example Manifest

#
yaml
schema_version: "1.0"
did: "did:orcha:agent:finance-dashboard-agent"
name: "Finance Portfolio Tracker"
description: "Retrieves live equity holdings, crypto balances, and performance metrics over MCP"

protocol:
  type: "MCP" # Options: MCP | A2A | COMPUTER_USE | LANGGRAPH | N8N | OPENAPI | GRPC
  endpoint: "http://localhost:3010/mcp"
  transport: "sse"

capabilities:
  - name: "fetch_portfolio"
    description: "Returns holdings and total balance"
    parameters:
      user_id: "string"
      currency: "string"
  - name: "get_market_depth"
    description: "Returns orderbook depth"

auth:
  type: "bearer"
  vault_key_id: "FINANCE_AGENT_API_KEY"

output_format:
  renders_canvaskit: true
  schema_type: "json"
FieldTypeRequiredDescription
schema_versionstringYesVersion of the emerge.yaml spec (e.g., "1.0")
didstringYesDecentralized Identifier in did:orcha:agent:* namespace
namestringYesHuman-readable name of the agent
protocol.typestringYesProtocol bridge handler type
capabilitiesarrayYesList of exposed function capabilities with parameters