Versatl

Versatl — Creator Agreement

Effective Date: March 9, 2026 Last Updated: March 9, 2026

This Creator Agreement ("Agreement") governs your participation as a creator on the Versatl marketplace, operated by Mfini Inc. ("Mfini," "Company," "we," "us," or "our") at versatl.ai. By publishing an agent on the Platform, you agree to this Agreement in addition to the Terms of Service and Privacy Policy.

Versatl is a product of Mfini Inc. This Agreement constitutes a legal agreement between you and Mfini Inc.

1. Becoming a Creator

1.1 Eligibility

Any registered Versatl user can become a creator by setting a marketplace handle on their profile. No separate application or approval is required to become a creator, though individual agents must pass review before publication.

1.2 Marketplace Handle

Your marketplace handle is your public identity on the Platform. It must be 3–50 characters, lowercase alphanumeric and hyphens only, and unique. Once set, your handle is visible on all agents you publish.

1.3 Creator Profile

You may optionally provide a bio and website URL. This information is displayed publicly on your creator profile and agent pages.

2. Agent Development and Publishing

2.1 Agent Definitions

Agents are defined using the Versatl declarative schema (YAML/JSON format) via the AgentDefinition specification. You may develop agents using the Creator SDK (versatl-sdk Python package) or the API directly.

2.2 What You Define

As a creator, you define:

  • Metadata: Agent name, description, category, and pricing model
  • Behavior: System prompt template, model chain preference, and memory configuration
  • Tools: References to platform-provided tools (by name)
  • Guardrails: Maximum actions per task, approval requirements, content filters, and budget limits

2.3 What You Do NOT Control

Agents are executed entirely by the Platform. You cannot:

  • Execute arbitrary code on the Platform
  • Access user credentials or personal data directly
  • Bypass Platform guardrails or security controls
  • Access other users' memories, tasks, or account information

2.4 Publishing Workflow

Agent versions follow this lifecycle:

  1. Draft: Initial development (not visible to users)
  2. Submitted: Submitted for review (triggers automated checks)
  3. Pending Review: Passed automated checks, awaiting admin review
  4. Published: Approved and visible on the marketplace
  5. Rejected: Not approved (feedback provided; you may revise and resubmit)
  6. Deprecated: Voluntarily marked as deprecated by you

2.5 Automated Review Checks

Before admin review, each submitted agent version is evaluated by 5 automated checks:

  1. Schema Validation: Agent definition conforms to the AgentDefinition schema
  2. Tool Verification: All declared tools exist in the platform registry
  3. Guardrail Compliance: Max actions per task does not exceed 100; budget does not exceed $10 per task
  4. Prompt Safety: System prompt does not contain injection patterns or credential references
  5. Metadata Completeness: Name, description, and category are present

2.6 Admin Review

After passing automated checks, agents are reviewed by a Platform administrator who may approve or reject the submission with feedback. We aim to complete reviews promptly but do not guarantee a specific timeline.

2.7 Versioning

Agents use semantic versioning (e.g., 1.0.0, 1.1.0, 2.0.0). Multiple versions can coexist. Subscribers may pin to a specific version. You are responsible for maintaining backward compatibility or clearly communicating breaking changes.

3. Agent Forking

3.1 Your Agents May Be Forked

Published agents can be forked by other users. Forking creates a new draft agent that copies the original definition, with a forked_from reference back to your agent. The fork is a new, independent agent — changes to the fork do not affect your original.

3.2 Attribution

Forked agents retain a forked_from reference to the original agent. If your original agent is deleted, the reference is set to null, but the fork continues to exist independently.

3.3 Forking Others' Agents

You may fork any published agent on the marketplace. Forking creates a draft under your account. You must submit the fork through the standard publishing workflow before it becomes visible on the marketplace.

4. Revenue Sharing

4.1 Revenue Model — Cost Recovery + Profit Share

Versatl uses a Cost Recovery + Profit Share model. Because the Platform executes agents on behalf of subscribers — including LLM inference, tool calls, and infrastructure — the Platform first recovers its operating costs before splitting profit with the creator.

How it works for each billing period:

  1. Gross Revenue = Number of completed tasks × your agent's per-task price (set by you)
  2. Platform Cost = Actual LLM token costs incurred by your agent's tasks × 1.20 (20% infrastructure markup covering compute, storage, networking, and other overhead)
  3. Profit = Gross Revenue − Platform Cost (floored at $0 — you never owe the Platform)
  4. Creator Share = 70% of Profit
  5. Platform Share = Platform Cost + 30% of Profit

Example: Your agent completes 100 tasks at $0.25/task. Gross revenue = $25.00. If those tasks consumed $8.00 in LLM tokens, platform cost = $8.00 × 1.20 = $9.60. Profit = $25.00 − $9.60 = $15.40. Creator share = $15.40 × 70% = $10.78. Platform share = $9.60 + $15.40 × 30% = $14.22.

4.2 Per-Task Pricing

You set your own per-task price (in USD cents) when publishing an agent. You can update the price in new versions. Free agents (pricing_model: "free") generate no revenue. Agents with pricing_model: "per_task" must specify a price_per_task_cents value.

4.3 Cost Visibility

The Creator Earnings dashboard shows a full cost breakdown for each agent: gross revenue, platform costs, profit, and your creator share. We provide this transparency so you can make informed pricing decisions.

4.4 Cost Monitoring

The Platform monitors the cost-to-revenue ratio of each agent over a rolling 30-day window. If an agent's platform costs consistently exceed its gross revenue (cost ratio above 90% for 30+ completed tasks), the Platform may:

  1. Notify you with actual cost data so you can adjust pricing
  2. Temporarily suspend the agent from the marketplace if the ratio does not improve

This protects both the Platform and you — an underpriced agent may be popular but unsustainable.

4.5 Stripe Connect

To receive payouts, you must connect a Stripe Connect Express account. The onboarding process is managed by Stripe and includes identity verification (KYC) as required by financial regulations.

4.6 Payout Schedule

  • Payouts are processed monthly for the prior calendar month
  • Minimum payout threshold: $10.00 USD
  • Amounts below the threshold are carried over to the next month
  • Payouts are made via Stripe Transfer to your Connect account
  • Currency: USD

4.7 Payout Status

You can track your earnings through the Creator Earnings dashboard:

  • Total earned: All-time revenue
  • Pending: Awaiting payout
  • Paid: Successfully transferred
  • By agent: Breakdown of earnings per published agent (with cost/profit visibility)

4.8 Taxes

You are responsible for reporting and paying all applicable taxes on your creator earnings. Mfini Inc. may provide tax forms (e.g., 1099) as required by law. Stripe Connect handles tax information collection during onboarding.

5. Intellectual Property

5.1 Your Agent Definitions

You retain ownership of the agent definitions you create, including system prompts, configuration, and metadata.

5.2 License to Versatl

By publishing an agent, you grant Mfini Inc. a non-exclusive, worldwide, royalty-free license to:

  • Host, display, and distribute your agent on the marketplace
  • Execute your agent definition on behalf of subscribers
  • Display your agent's name, description, and metadata in search results and promotional materials

This license terminates when you delete your agent from the marketplace.

5.3 Platform Tools

Your agents reference platform-provided tools by name. You do not acquire any rights to these tools. The Platform may modify, add, or remove tools at any time with reasonable notice.

5.4 No Claim to User Data

You have no right to access, view, or retain any data belonging to users who subscribe to your agents. All user data remains user-owned and is processed exclusively by the Platform.

6. Creator Responsibilities

6.1 Content Standards

Your agent definitions must:

  • Not contain misleading, deceptive, or harmful system prompts
  • Not attempt to circumvent Platform guardrails or safety measures
  • Not impersonate other creators, brands, or individuals
  • Not infringe the intellectual property of others
  • Comply with the Acceptable Use Policy

6.2 Accuracy

Agent descriptions, capabilities, and metadata must accurately represent what the agent does. Do not overstate capabilities or make claims about performance that are not substantiated.

6.3 Maintenance

You are responsible for maintaining your published agents. If a platform tool referenced by your agent is deprecated, you should update your agent definition accordingly.

7. Platform Rights

7.1 Review and Removal

We reserve the right to reject, suspend, or remove any agent from the marketplace at our discretion, including for:

  • Violation of these terms or the Acceptable Use Policy
  • User complaints or negative reviews indicating harmful behavior
  • Security vulnerabilities or safety concerns
  • Inactivity or abandonment

7.2 Marketplace Curation

We may feature, promote, or deprioritize agents at our discretion. Featured status and marketplace positioning are editorial decisions and are not guaranteed.

7.3 Platform Changes

We may modify the agent schema, available tools, guardrail requirements, or review criteria. We will provide reasonable notice of breaking changes.

8. Termination

8.1 By You

You may remove your agents from the marketplace at any time by deleting or deprecating them. Existing subscribers will retain access to their pinned version until they unsubscribe.

You may stop being a creator by removing your marketplace handle. This does not delete your user account.

8.2 By Us

We may terminate your creator privileges if you repeatedly violate the Creator Agreement, Acceptable Use Policy, or Terms of Service.

8.3 Effect on Revenue

Upon termination, pending payouts above the minimum threshold will be processed in the next payout cycle. Revenue for the current period will be calculated pro-rata through the termination date.

9. Contact

For questions about the Creator Agreement:

Mfini Inc. Email: creators@versatl.ai