Versatl — Marketplace Publisher Agreement

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

This Marketplace Publisher Agreement ("Agreement") governs your participation as a publisher 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.

Terminology used in this Agreement. A creator is any user who has built an AI entity (Skill, Agent, or Workflow) on the Platform — for personal use, internal sharing, or marketplace listing. A publisher is a creator who has additionally accepted this Agreement, set a marketplace handle, and listed at least one entity in the public marketplace. Becoming a creator does not require this Agreement; becoming a publisher does. This Agreement uses "you" to refer to a publisher.

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

1. Becoming a Publisher

1.1 Eligibility

Any registered Versatl user can become a publisher by accepting this Agreement and setting a marketplace handle on their profile. No separate application or approval is required to become a publisher, 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 Publisher Profile

You may optionally provide a bio and website URL. This information is displayed publicly on your publisher 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 publisher, 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:

Draft: Initial development (not visible to users)
Submitted: Submitted for review (triggers automated checks)
Pending Review: Passed automated checks, awaiting admin review
Published: Approved and visible on the marketplace
Rejected: Not approved (feedback provided; you may revise and resubmit)
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:

Schema Validation: Agent definition conforms to the AgentDefinition schema
Tool Verification: All declared tools exist in the platform registry
Guardrail Compliance: Max actions per task does not exceed 100; budget does not exceed $10 per task
Prompt Safety: System prompt does not contain injection patterns or credential references
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 publisher.

How it works for each billing period:

Gross Revenue = Number of completed tasks × your agent's per-task price (set by you)
Platform Cost = Actual LLM token costs incurred by your agent's tasks × 1.20 (20% infrastructure markup covering compute, storage, networking, and other overhead)
Profit = Gross Revenue − Platform Cost (floored at $0 — you never owe the Platform)
Publisher Share = 70% of Profit
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. Publisher 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 Earnings dashboard shows a full cost breakdown for each agent: gross revenue, platform costs, profit, and your publisher 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:

Notify you with actual cost data so you can adjust pricing
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 once per month, on the 1st calendar day of each month at 02:00 UTC, via Stripe Transfer to your connected Express account in USD. To absorb chargeback risk on the underlying customer charges, payouts are subject to the following holds:

Standard hold: 30 days after the end of the earnings period. April earnings are paid June 1.
New-publisher hold: until you have received 3 completed payout cycles OR accrued $500 USD in lifetime earnings (whichever comes first), your first payout requires the earnings period to have ended at least 90 days prior. This window allows us to absorb the elevated dispute risk associated with new accounts.
Minimum payout: $10.00 USD per payout. Amounts below this threshold roll forward to the next cycle.
Pending adjustments (refunds, chargebacks — see §4.9) are netted against your pending balance before each payout. If the net falls below the minimum, the remainder rolls forward.

We may delay any payout that is the subject of an active investigation, dispute, or compliance review.

4.7 Payout Status

You can track your earnings through the Earnings dashboard:

Total earned: All-time revenue
Pending: Awaiting payout (subject to hold periods and adjustments)
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 publisher earnings. Mfini Inc. may provide tax forms (e.g., 1099-K, 1099-NEC) as required by law. Stripe Connect handles tax information collection during onboarding.

4.9 Refunds, Chargebacks, and Clawbacks

Mfini Inc. is the merchant of record for all customer payments on the Platform. When a customer's payment is reversed — whether by refund, card chargeback, or other reversal — the publisher's share of revenue derived from that payment is also reversed. Specifically:

Failed-task refunds: When a task fails and the platform refunds the customer's balance, the corresponding publisher revenue is reversed. If the revenue has not yet been paid out, it is removed from your pending balance. If it has been paid out, it becomes a clawback.
Customer chargebacks: When a customer files a successful chargeback against a balance top-up, the funds withdrawn from Versatl's Stripe account are attributed (FIFO — first-in-first-out) to the tasks the customer paid for from those funds. Publisher revenue from those tasks is reversed under the same rules as §4.9.1.
Clawback mechanics: A reversed amount that has already been paid out becomes a debit against your pending balance (a "clawback adjustment"). Future earnings offset clawbacks before any new amount is paid out. Clawbacks may persist across payout cycles until offset.
Chargeback window: Card networks permit chargebacks up to 120 days after the original charge. The 30-day standard hold and the 90-day new-publisher hold are designed to absorb most of this risk, but residual clawbacks may occur for chargebacks filed beyond the hold window.
Termination with negative balance: If you terminate (or are terminated) with a net-negative pending balance after applying clawbacks, you remain liable for the negative amount. We may pursue collection through Stripe Connect, future earnings if you re-enroll, or other means available to us.
Disputed-charge holds: While a customer chargeback is being investigated, we may freeze the affected pending revenue until the dispute resolves. Won disputes release the freeze; lost disputes finalize the clawback.

4.10 Restricted Business Categories

You represent and warrant that no agent you list facilitates transactions, services, content, or operations falling within the Restricted Business Categories enumerated in the Acceptable Use Policy (§3 of the AUP), which mirrors and incorporates Stripe's restricted-business list. We may suspend, remove, or refuse to publish any agent we determine — at our sole discretion — to violate this representation. Pending revenue from any agent in violation may be withheld pending review and forfeited if violation is confirmed.

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. Publisher 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.

6.4 Cooperation with Risk and Compliance Inquiries

You agree to cooperate with Mfini Inc. and Stripe in connection with any payment-risk, chargeback, fraud, or compliance investigation involving your publisher account or any of your published agents. This includes promptly responding to information requests, providing documentation requested by Stripe (KYC updates, business proof, etc.), and assisting in dispute response when a customer charge that funded your earnings is being disputed.

The Platform's Risk and Remediation Guide (docs/legal/publisher-risk-remediation.md) describes the lifecycle of a payment risk event end-to-end and is incorporated by reference. Material updates to that guide will be communicated.

7. Publisher Support

7.1 Support Channel and SLA

For payout, revenue, chargeback, KYC, and Stripe Connect questions, the Platform support address is publisher-support@versatl.ai. We respond to publisher-support inquiries within five (5) business days. Inquiries about agent functionality, content moderation, or general platform usage should go to the channels listed in the Terms of Service.

7.2 Risk and Remediation Process

When a payment risk event affects you (chargeback received, KYC update required, payout flagged for review, etc.) we:

Notify you via email and an in-app notification, summarizing the event and any action required.
Reference the relevant section of the Risk and Remediation Guide, which walks through what to expect.
Hold any affected payout until the matter is resolved per §4.6 and §4.9.
Confirm resolution and either release the held payout, finalize a clawback, or — in cases of fraud or violations — terminate per §9.

7.3 Escalation

If you are dissatisfied with how a risk or payout matter was handled, you may escalate via the support address with the subject line "Escalation: [your handle]". Escalations are reviewed by Platform leadership within ten (10) business days.

8. Platform Rights

8.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

8.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.

8.3 Platform Changes

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

9. Termination

9.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 publisher by removing your marketplace handle. This does not delete your user account, nor does it cancel any pending clawback obligations under §4.9.

9.2 By Us

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

9.3 Effect on Revenue

Upon termination, pending payouts above the minimum threshold and net of any pending adjustments (§4.9) will be processed in the next payout cycle, subject to applicable hold periods. Revenue for the current period will be calculated pro-rata through the termination date. A net-negative pending balance survives termination and remains payable per §4.9.5.

10. Contact

For questions about the Marketplace Publisher Agreement:

Mfini Inc. Email: publisher-support@versatl.ai