Versatl — Marketplace Publisher Agreement

Effective Date: March 9, 2026

Last Updated: August 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)
Failed Review: One or more automated checks failed (feedback provided; you may revise and resubmit)
Pending Review: Passed automated checks, awaiting admin review
Published: Approved and visible on the marketplace
Rejected: Not approved by admin review (feedback provided; you may revise and resubmit)
Withdrawn: You withdrew an in-flight submission before review completed
Deprecated: Voluntarily marked as deprecated by you (an agent-level status; existing subscribers retain access per §9.1)

2.5 Automated Review Checks

Before admin review, each submitted agent version is evaluated by the Platform's automated checks, currently:

Schema Validation: Agent definition conforms to the AgentDefinition schema (which enforces limits including a per-attempt action ceiling and a per-task token budget ceiling)
Tool Verification: All declared tools exist in the platform registry
Prompt-Injection Screening: System prompt does not contain known injection patterns
LLM Prompt-Safety Review: An AI reviewer evaluates the system prompt for unsafe or deceptive instructions
Guardrail Compliance: Required content filters (including PII protection) are enabled
Approval Coverage: High-risk actions are covered by the approval settings the definition declares
Metadata Completeness: Name, description, and category are present

The check set may evolve per §8.3. A version that fails a gating check returns to you with feedback (status Failed Review) for revision and resubmission. Two qualifications: Approval Coverage (item 6) is advisory — it attaches feedback for the admin reviewer rather than failing the version, because at runtime the Platform independently requires customer approval for high-risk outbound actions regardless of your declared settings; and if the LLM Prompt-Safety Review (item 4) cannot be completed for operational reasons, the version proceeds to admin review flagged for closer manual scrutiny rather than failing automatically (an unsafe verdict still fails the version).

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.

2.8 Pinned Model and Substitution

The Platform may substitute a functionally similar model when a selected model becomes unavailable, is deprecated by its provider, or otherwise cannot serve the request, as described in Terms of Service § 8.4. If reproducibility of model behavior is essential to your agent (for example, the system prompt depends on a specific model's idiosyncrasies, or downstream consumers require deterministic outputs from a known model), you may set require_pinned_model: true in the agent definition. In that case, requests that cannot be served by the pinned model will fail with a RetiredPinError rather than substitute. You remain responsible for publishing a successor version when a model on which a pinned agent depends is retired. Under the compute-based billing model described in Terms of Service § 5.6, a RetiredPinError that occurs before any provider call has been made incurs no compute charge; if provider calls have already been made before the error occurs, the customer is charged for the compute consumed and no automatic refund applies. Your per-task agent fee is completion-contingent: it is charged at task submission and automatically returned to the customer if the run terminally fails or is cancelled — including a failure caused by a RetiredPinError — with the corresponding publisher revenue reversed under § 4.9. Runs that complete (including with warnings) keep the fee. Note that, independently of your agent's settings, a subscriber may enable the account-level "No model substitution" setting (Terms of Service § 8.4); runs that would require substitution for such a subscriber are refused at admission or fail rather than substitute, with the same fee treatment as above.

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 — Profit Share

The Platform charges subscribers separately for the compute their runs consume: LLM token costs and any search or other third-party service costs are passed through to the subscriber at provider rates (LLM tokens may instead be paid by the subscriber directly to the provider under BYOM), plus Versatl's platform fee on that total provider cost at the rate published on the Platform's Pricing Page (versatl.ai/pricing) — see Terms of Service §5.1. Your agent's price is therefore not used to recover compute costs. It is profit, split between you and the Platform.

How it works for each billing period:

Gross Revenue = the fees actually collected from subscribers for your published entities during the period — per-task fees for direct runs, subscription-period fees for active subscriptions, and per-run fees for your published workflows — net of refunds and chargeback adjustments (§4.9).
Publisher Share = the Publisher Share percentage of Gross Revenue, rounded down to the nearest cent per entity per period. The current Publisher Share percentage is published on the Platform's Pricing Page (versatl.ai/pricing), which is incorporated into this Agreement by reference; the percentage in effect during a billing period applies to that period. Any reduction of the Publisher Share percentage will be communicated to publishers at least 30 days before taking effect and applies prospectively only; increases may take effect immediately.
Platform Share = the remainder of Gross Revenue

Runs invoked under an active subscription to your agent do not additionally incur your per-task fee; the subscription-period fee is the agent revenue for those runs. Direct and trigger-initiated runs outside a subscription each incur the per-task fee. Runs of your agent invoked as a delegated sub-task by another agent — including as a step of another creator's workflow — do not incur your per-task fee, and generate Gross Revenue only through the invoking user's active subscription to your agent, if any.

Illustrative example (assuming a 70% Publisher Share): During a period, your agent collects 100 direct-run fees at $0.25 each and four $5.00 monthly subscription fees. Gross Revenue = $25.00 + $20.00 = $45.00. Publisher share = $45.00 × 70% = $31.50. Platform share = $13.50. The subscribers separately paid the LLM token costs and platform fee for their own runs; those amounts are not deducted from your revenue.

4.2 Agent Pricing

You set your own pricing when publishing an agent, and may update it 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; agents with pricing_model: "subscription" specify a price_monthly_cents value charged at the start of each subscription period (a subscription-priced agent invoked as a one-off task outside a subscription charges its per-task price, where one is set).

4.3 Earnings Visibility

The Earnings dashboard shows, for each of your published agents and workflows: gross revenue, run counts, and your publisher share, plus totals for pending and paid amounts. Reversals (fee returns, refunds, and chargebacks) are netted against subsequent payouts as described in §4.6 and §4.9. The pending total is your overall balance awaiting payout, shown net of unapplied reversals; because each individual payout covers only earnings that have cleared the hold windows in §4.6 (with reversals netted at payout time and the minimum applied to the netted amount), a given payout may be smaller than the pending total displayed.

4.4 [Reserved]

4.5 Stripe Connect

To receive payouts — and before publishing any paid listing — you must connect a Stripe Connect Express account and complete its onboarding. The onboarding process is managed by Stripe and includes identity verification (KYC) as required by financial regulations. Free listings may be published without a connected account.

Once you have completed onboarding, the Stripe Express dashboard — accessible via the "Manage on Stripe" link on your Earnings page (/dashboard/create/earnings) — is the sole supported surface for managing your connected account. The link generates a one-time, signed Stripe Express login URL each time you click it; you use the Express dashboard to view payouts and balance, update bank account details, update tax information, and download tax forms (e.g., 1099-K, 1099-NEC). The Platform cannot modify your Stripe Connect account, and can view only summary status — your payout-eligibility status, your connected bank account's name and last four digits (or, where your payout method is a card, its type and last four digits), your payout schedule (interval and anchor), and your current account balance — which it displays on your Earnings page. Full account details, transaction history, and account management remain accessible only through the Stripe Express dashboard.

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 been paid 3 payout cycles OR been paid $500 USD in cumulative earnings (whichever comes first), every 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 at payout time against your total pending publisher earnings across all of your published entities: your publisher share of each reversed amount is deducted from the amount otherwise payable, and residual negative amounts carry forward until offset by later earnings. The minimum payout applies to the netted amount; if the netted amount falls below the minimum, no payout is made and both the earnings and the adjustments remain pending until a later cycle.

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

Sales tax. Where the Platform is registered to collect sales tax in the customer's jurisdiction, sales tax is calculated by the Platform using third-party tax-rate data, collected from the customer in addition to the top-up amount, and remitted by Mfini Inc. Sales tax is not part of Gross Revenue as defined in §4.1 and is not subject to revenue splitting between Mfini Inc. and you. Tax reporting and remittance are handled by the Platform; you have no sales-tax obligations arising from a customer's purchase of usage that funds your publisher revenue. Income tax on your publisher earnings remains your responsibility under §4.8.

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 entity: Breakdown of earnings per published agent and per published workflow

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 automatic fee return, discretionary refund, card chargeback, or other reversal — the publisher's share of revenue derived from that payment is also reversed. Under the compute-based billing model described in Terms of Service § 5.6, compute charges are never refunded on outcome; agent and workflow fees, however, are completion-contingent — when a run terminally fails or is cancelled, the fee is automatically returned to the customer and the corresponding publisher revenue is reversed under the same netting rules as the categories below.

Discretionary Platform refunds: The Platform may, at its sole discretion, refund a customer's charge for an agent run on a case-by-case basis (e.g., where a Platform-side incident materially prevented meaningful execution). When such a refund is issued, the corresponding publisher revenue is reversed on the same schedule as a chargeback: 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 adjustment against future earnings.
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. The current inventory of third-party integrations available to agents is maintained in the Connected Services Appendix at versatl.ai/legal/connected-services-appendix, which is incorporated by reference into this Agreement.

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

Accurate BYOM disclosure. Where your published agent's listing displays a Bring-Your-Own-Model (BYOM) coverage state (e.g., "Full BYOM coverage", "Partial BYOM coverage", "No BYOM coverage required", "Platform key only"), that disclosure must accurately reflect the runtime model selection your agent definition would produce for a subscriber who has no BYOM key configured. You may not publish an agent that displays a more favorable BYOM coverage state than is actually true at runtime — for example, you may not display "Full BYOM coverage" when the agent in fact silently falls back to the Platform-managed key for any of its tiers. Misrepresenting BYOM coverage is treated as a §6.1 content-standards violation and may result in delisting, revenue forfeiture under §4.10, or publisher termination under §9.

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, published at /legal/publisher-risk-remediation, 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:

Aim to 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 an individual agent from the marketplace at any time by deprecating it. Existing subscribers will retain access to their pinned version until they unsubscribe.

You may close your publisher account entirely from your publisher settings. Closing your publisher account is a deferred wind-down, not an immediate cutoff, because subscription fees are charged as whole upfront periods: each of your published agents is delisted (it stops appearing in the marketplace and will not accept new subscriptions) but keeps running for your existing subscribers through the end of the period they have already paid for. Once an agent's last active subscription reaches the end of its paid period, that subscription is cancelled, the agent reverts to a private agent in your own account (it is not deleted), and — once all of your agents have finished winding down — your final settlement is paid and your marketplace handle is removed. Until the wind-down completes you may cancel it from your publisher settings, which re-lists the agents that have not yet finished winding down and resumes their renewals; agents that have already completed their wind-down remain private (you may re-publish them through the normal review process), and subscriptions that have already ended remain cancelled. Published workflows are delisted immediately when you close your publisher account — per-run listings have no paid period to serve out — and cancelling the wind-down does not re-list them; you may restore and re-publish a workflow through the normal review process. Closing your publisher account does not delete your user account, nor does it cancel any pending clawback obligations under §4.9. (Deleting your user account requires closing your publisher account first.)

For subscriptions that are not in an active paid period when an agent winds down: a paused subscription is cancelled and the unused portion of its paid period is refunded to the subscriber; a past-due subscription (whose current period is unpaid) is cancelled without a refund.

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. Where we do so with notice, existing subscribers are served through their paid periods on the same wind-down basis as §9.1 unless the violation requires immediate removal.

9.3 Effect on Revenue

When your publisher account finishes winding down, your pending balance net of any pending adjustments (§4.9) is paid as a final settlement. Because the wind-down serves every subscription through the end of its paid period, revenue for those periods is included in the settlement — there is no pro-ration and no forfeiture of periods your subscribers paid for. The minimum payout threshold in §4.6 does not apply to a final settlement — it exists to avoid uneconomic recurring transfers, and a termination payout is one-time — so amounts below that threshold are paid rather than carried forward. Amounts under one dollar (US$1.00) are not transferred. If your connected Stripe account cannot receive transfers at that time (for example, identity verification is outstanding), we will ask you to complete verification so the settlement can be paid. 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

Address: 1401 Lavaca St, Ste 558, Austin, TX 78701