Export Formats

MeetLoyd uses standardized JSON formats for exporting and importing agents and teams. These formats are designed to be portable, version-controlled, and Store-ready.

Format Overview

Format	Description	Use Cases
meetloyd-agent	Single agent export	Share agents, backup, Store publishing
meetloyd-team	Multi-agent team export	Share teams, backup, Store publishing

Both formats are forward-compatible. When importing an older version, the system detects the version and applies migrations automatically.

meetloyd-agent Format

Export format for individual agents. Current version: 1.1.

Top-Level Fields

Field	Type	Required	Description
_format	string	Yes	Must be "meetloyd-agent"
_version	string	Yes	Format version
_exportedAt	string	Yes	ISO 8601 timestamp
_exportedFrom	string	No	Source tenant ID
agent	object	Yes	Agent configuration (name, model, systemPrompt, tools, memoryConfig, rateLimits)
versions	array	No	Version history

Exporting and Importing

Export an agent from the dashboard by navigating to the agent detail page and clicking Export. You can optionally include version history.

Import an agent by going to Agents > Import and uploading the JSON file.

meetloyd-team Format

Export format for multi-agent teams. Current version: 1.0.

Top-Level Fields

Field	Type	Required	Description
_format	string	Yes	Must be "meetloyd-team"
_version	string	Yes	Format version
_exportedAt	string	Yes	ISO 8601 timestamp
team	object	Yes	Team metadata (name, description, settings)
agents	array	Yes	Agents in the team with localId, name, role, model, etc.
teamMemory	array	No	Initial team memory entries
tasks	array	No	Scheduled tasks
provisioning	object	No	Google Workspace / Microsoft 365 resource creation settings
store	object	No	Store metadata for publishing

Agent Fields

Field	Type	Required	Description
localId	string	Yes	Reference ID within the export
name	string	Yes	Agent name
role	string	No	Agent role (e.g., "cmo", "cro")
model	string	Yes	LLM model ID or alias
systemPrompt	string	No	System prompt
tools	array	No	Enabled tools
parentAgentLocalId	string	No	Reference to supervisor agent

Provisioning Options

Google Workspace

Field	Type	Description
createGroup	boolean	Create a Google Group
groupEmail	string	Suggested group email
createSharedDrive	boolean	Create a shared Google Drive
sharedDriveName	string	Name for the shared drive

Microsoft 365

Field	Type	Description
createGroup	boolean	Create a Microsoft 365 Group
createSharePointSite	boolean	Create a SharePoint site
createTeamsChannel	boolean	Create a Teams channel

Importing a Team

When importing, you can optionally specify a target workspace, override the team name, choose whether to import team memory, and enable or disable Google/Microsoft provisioning.

Best Practices

For Agent Exports

1. Include meaningful descriptions
2. Keep system prompts modular
3. Use standard tool names
4. Set appropriate rate limits

For Team Exports

1. Use descriptive localId values
2. Set parentAgentLocalId for hierarchy
3. Include initial teamMemory for context
4. Define tasks with proper schedules

For Store Submissions

1. Set all store fields (category, tags, version)
2. Include comprehensive documentation in descriptions
3. Test the import/export cycle before submission
4. Version your exports semantically