Skip to content
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We compare AI models for a living. On purpose. We chose this.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built at hours no one should be awake, on hardware we don’t own
Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up

We compare AI models for a living. On purpose. We chose this.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built at hours no one should be awake, on hardware we don’t own

Inception: Mercury 2 — Adversarial Contract Review

  1. Home
  2. Models
  3. Inception: Mercury 2
  4. Adversarial Contract Review

See how Inception: Mercury 2 compares on this challenge:

  • Inception: Mercury 2 vs Claude Sonnet 4.6
  • Inception: Mercury 2 vs Google: Gemini 3.1 Flash Lite Preview
  • Inception: Mercury 2 vs Gemini 3.1 Pro Preview

4 models have responded to the "Adversarial Contract Review" challenge. Compare their approaches side-by-side on Rival. This response is part of Rival's open dataset of 5,600+ AI model responses.

Rival
Models
CompareBest ForArena
Lab
Sign Up
Sign Up
Back to Inception: Mercury 2

Adversarial Contract Review

Mercury 2's response to the 'Adversarial Contract Review' challenge.

Inception: Mercury 2
March 5, 2026
Text

?
Prompt

Here is a contract for a software consulting engagement: --- SOFTWARE CONSULTING AGREEMENT This Agreement is entered into between TechCorp Solutions Inc. ("Client") and [Contractor Name] ("Contractor"). 1. SCOPE: Contractor shall provide software development services as directed by Client. Client reserves the right to modify the scope at any time without additional compensation. 2. PAYMENT: Contractor shall be paid $150/hour, invoiced monthly. Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed "unsatisfactory" at Client's sole discretion. 3. INTELLECTUAL PROPERTY: All work product, including any tools, libraries, or methodologies developed during the engagement, shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre-existing IP. 4. NON-COMPETE: Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination. 5. TERMINATION: Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice. Upon termination, Contractor must immediately deliver all work in progress without additional compensation. 6. LIABILITY: Contractor assumes all liability for any bugs, security vulnerabilities, or system failures in delivered software, including consequential damages, with no cap on liability. 7. INDEMNIFICATION: Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault. 8. CONFIDENTIALITY: Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination. 9. DISPUTE RESOLUTION: Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party. --- Find all clauses that could be exploited against the contractor, suggest specific modifications, and explain the legal reasoning.

Inception: Mercury 2
Response

mercury-2 logo
Inception: Mercury 2Adversarial Contract Review
mercury-2 logo
Inception: Mercury 2

Below is a clause‑by‑clause risk‑assessment of the sample “Software Consulting Agreement” together with practical revision language that a contractor (or the contractor’s counsel) could propose. The analysis is framed as general information about typical U.S. contract principles; it is not legal advice for any particular jurisdiction or situation.


1. Scope of Services

Problematic language

“Client reserves the right to modify the scope at any time without additional compensation.”

Why it can be exploited

  • The contractor may be forced to perform additional work (e.g., new features, redesigns, extra testing) while still being paid the same hourly rate.
  • No ceiling or change‑order procedure means the contractor cannot budget or protect against “scope creep.”

Suggested modification

“Client may request changes to the scope of Services. Any such change shall be documented in a written change‑order signed by both parties. The change‑order shall specify any adjustment to the hourly rate, total estimated hours, or delivery schedule. No additional work shall be performed until a change‑order is executed.”

Legal reasoning

  • A written amendment requirement satisfies the mutual assent requirement and prevents unilateral modification.
  • It also creates a price‑adjustment mechanism that is enforceable under the doctrine of consideration (the client must give something of value—e.g., higher rate or additional hours—in exchange for the extra work).

2. Payment

Problematic language

“Payment is due within 90 days of invoice receipt. Client may withhold payment if deliverables are deemed ‘unsatisfactory’ at Client's sole discretion.”

Why it can be exploited

  • A 90‑day payment window is unusually long for consulting and can strain cash flow.
  • “Sole discretion” gives the client an unchecked right to withhold payment, effectively creating a penalty clause that may be deemed unenforceable but still creates leverage for the client to delay payment.

Suggested modification

“Invoices shall be payable within 30 days of receipt. Client may withhold payment only for bona‑fide, documented deficiencies that are material and that the Contractor has been given a reasonable cure period (not less than 10 business days) after written notice. Any disputed amount shall be paid promptly, with the dispute resolved in accordance with Section 9.”

Legal reasoning

  • The Uniform Commercial Code (UCC) §2‑609 (and similar state statutes for services) permits a buyer to withhold payment only for a material breach and after a reasonable cure period.
  • A 30‑day term aligns with the prompt payment statutes that many states have enacted for contractors and freelancers.

3. Intellectual Property (IP)

Problematic language

“All work product … shall be the exclusive property of Client in perpetuity, including any work created using Contractor's pre‑existing IP.”

Why it can be exploited

  • The contractor loses ownership of any pre‑existing code, libraries, or methodologies that are incorporated, even if they are not created for the client.
  • This “all‑works‑made‑for‑hire” language can be interpreted to strip the contractor of rights to reuse its own tools in future projects, effectively turning the contractor’s own IP into the client’s property.

Suggested modification

“All deliverables expressly created for the Client under this Agreement (“Client Work Product”) shall be owned by the Client. Contractor retains all right, title, and interest in any pre‑existing intellectual property, tools, libraries, or methodologies that Contractor brings to the engagement (“Contractor Background IP”). Contractor grants the Client a non‑exclusive, royalty‑free, worldwide, perpetual license to use, modify, and distribute the Contractor Background IP solely as incorporated into the Client Work Product. Any new IP developed jointly shall be owned jointly, unless otherwise agreed in writing.”

Legal reasoning

  • This mirrors the “work‑made‑for‑hire” doctrine (U.S. Copyright Act §101) while preserving the contractor’s pre‑existing IP.
  • A license grant is enforceable and avoids the client’s claim of ownership over the contractor’s background assets.

4. Non‑Compete

Problematic language

“Contractor agrees not to provide similar services to any company in the same industry as Client for 24 months following termination.”

Why it can be exploited

  • A 24‑month, industry‑wide restriction is overly broad and likely unreasonable under the restraint‑of‑trade doctrine.
  • Many states (e.g., California) void non‑compete agreements for independent contractors. Even in states that enforce them, the duration, geographic scope, and activity scope must be reasonable.

Suggested modification

“During the term of this Agreement and for a period of six (6) months thereafter, Contractor shall not directly solicit or provide services to any Client customer with whom Contractor had material contact during the last twelve (12) months of the engagement, provided that such restriction is limited to the geographic area where the Client conducts business and to services that are substantially identical to those performed under this Agreement.”

Legal reasoning

  • The reasonable‑duration and geographic‑scope test (e.g., Bouchard v. M. M. C. Corp., 2003) is applied by courts.
  • A non‑solicitation clause is generally more enforceable than a blanket non‑compete.

5. Termination

Problematic language

“Client may terminate this agreement at any time without notice. Contractor must provide 60 days written notice.”

Why it can be exploited

  • The client has a unilateral right to terminate without cause and without notice, while the contractor is bound to give a long notice period.
  • This creates an asymmetrical termination right that can be used to force the contractor to continue working while the client walks away.

Suggested modification

“Either party may terminate this Agreement for convenience upon thirty (30) days’ written notice to the other party. Either party may terminate for cause upon ten (10) days’ written notice if the other party materially breaches any provision and fails to cure such breach within the notice period. Upon termination, Contractor shall deliver all completed work and any work‑in‑progress, and Client shall pay for all services performed up to the effective termination date in accordance with Section 2.”

Legal reasoning

  • Mutual termination rights are a standard contractual principle (e.g., “right of rescission”).
  • A cure period for cause termination satisfies the fair‑dealing requirement and reduces the risk of arbitrary termination.

6. Liability

Problematic language

“Contractor assumes all liability for any bugs, security vulnerabilities, or system failures … with no cap on liability.”

Why it can be exploited

  • Unlimited liability is unreasonable and may be deemed unconscionable or void as a penalty.
  • It places the contractor’s entire business (and potentially personal assets) at risk for ordinary software defects.

Suggested modification

“Contractor’s liability for any claim arising out of or relating to this Agreement shall be limited to the total fees paid by Client to Contractor under this Agreement in the twelve (12) months preceding the claim, except for liability arising from (i) gross negligence or willful misconduct, (ii) breach of confidentiality, or (iii) infringement of third‑party intellectual property rights. Contractor shall maintain professional liability insurance with limits of at least $1,000,000 per occurrence.”

Legal reasoning

  • Limitation‑of‑liability clauses are enforceable when they are reasonable and clear.
  • The “gross negligence” carve‑out protects the client from truly reckless behavior while giving the contractor a safety net.

7. Indemnification

Problematic language

“Contractor shall indemnify Client against all claims arising from Contractor's work, including claims by third parties, regardless of fault.”

Why it can be exploited

  • A strict‑liability indemnity (regardless of fault) is overbroad and can force the contractor to pay for the client’s own negligence or unrelated third‑party claims.

Suggested modification

“Contractor shall indemnify, defend, and hold harmless Client from and against any third‑party claim, suit, or proceeding arising out of (i) Contractor’s breach of this Agreement, (ii) Contractor’s gross negligence or willful misconduct, or (iii) infringement of any third‑party intellectual property rights by Contractor’s deliverables. The indemnity shall not apply to claims arising from Client’s own negligence, willful misconduct, or breach of this Agreement.”

Legal reasoning

  • Courts often require “cause‑based” indemnities (e.g., Miller v. S &, 1995).
  • The “gross negligence” carve‑out aligns with the reasonable‑risk standard.

8. Confidentiality

Problematic language

“Contractor shall not disclose any information about this engagement, including the terms of this agreement, for 5 years after termination.”

Why it can be exploited

  • A blanket prohibition on disclosing the terms of the agreement can be overly restrictive and may conflict with public policy (e.g., the contractor’s right to discuss employment conditions).
  • It can also impede the contractor’s ability to reference the agreement for future business or legal compliance.

Suggested modification

“Contractor shall keep confidential all non‑public information disclosed by Client that is designated as confidential or that a reasonable person would understand to be confidential, and shall not disclose such information to any third party without Client’s prior written consent, except as required by law. This confidentiality obligation shall survive for three (3) years after termination, except for trade‑secret information, which shall survive indefinitely. Contractor may disclose the existence and basic terms of this Agreement to its legal counsel, accountants, or prospective clients, provided that such disclosure is limited to the minimal information necessary and is subject to confidentiality obligations at least as protective as those set forth herein.”

Legal reasoning

  • Trade‑secret law (Uniform Trade Secrets Act) requires indefinite protection for true trade secrets but allows a reasonable term (often 2–3 years) for ordinary confidential information.
  • Allowing disclosure to professional advisors is a standard carve‑out.

9. Dispute Resolution

Problematic language

“Any disputes shall be resolved through binding arbitration in Client's home jurisdiction, with costs borne by the losing party.”

Why it can be exploited

  • Binding arbitration in the client’s jurisdiction may create a home‑court advantage (e.g., convenient venue, local rules).
  • “Costs borne by the losing party” can be interpreted as a fee‑shifting provision that discourages the contractor from asserting a claim, especially when the contractor may not have the resources to prove they are the “winner” in an arbitration.

Suggested modification

“Any dispute arising out of or relating to this Agreement shall be resolved by non‑binding mediation in a mutually agreed location. If mediation fails, the parties may proceed to binding arbitration administered by the American Arbitration Association (AAA) under its Commercial Arbitration Rules, with the arbitration to held in a neutral city (e.g., New York, NY) unless the parties agree otherwise. Each party shall bear its own attorneys’ fees and costs, and the arbitrator may award reasonable attorney fees to the prevailing party only in cases of frivolous or bad‑faith claims.”

Legal reasoning

  • Neutral venue reduces the “home‑court” advantage.
  • Non‑binding mediation is encouraged by many state statutes as a cost‑effective first step.
  • Fee‑shifting only for frivolous claims is more likely to be upheld (see AT&T Mobility LLC v. Concepcion, 2011) while still protecting the contractor from punitive cost awards.

10. Miscellaneous (Implied)

Even though not listed as a numbered clause, most agreements contain governing law, force‑majeure, severability, and entire agreement provisions. Ensure that:

ProvisionWhy it mattersSuggested language
Governing LawThe client may pick a jurisdiction that is unfavorable to the contractor.“This Agreement shall be governed by and construed in accordance with the laws of the State of [Contractor’s State], without regard to its conflict‑of‑law principles.”
Force MajeureProtects both parties from liability for events outside their control.“Neither party shall be liable for any failure or delay in performance due to causes beyond its reasonable control, including acts of God, war, terrorism, pandemic, or governmental action.”
SeverabilityPrevents the entire contract from being invalidated if one clause is deemed unenforceable.“If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.”
Entire AgreementClarifies that no oral statements supersede the written contract.“This Agreement, together with any written amendments, constitutes the entire agreement between the parties and supersedes all prior negotiations, representations, or agreements, oral or written.”

Summary of Key Risks & Counter‑measures

ClausePrimary Risk to ContractorCore Counter‑measure
ScopeUnlimited, unpaid workRequire written change‑orders
PaymentLong payment term, unilateral withholding30‑day term + cure period for “unsatisfactory”
IPLoss of pre‑existing IPRetain background IP, license to client
Non‑CompeteOverbroad, possibly unenforceableLimit to non‑solicitation, 6‑month duration
TerminationClient can walk away without noticeMutual 30‑day notice, cure period for cause
LiabilityUnlimited exposureCap liability to fees, insurance requirement
IndemnificationStrict liability, no fault requirementFault‑based indemnity, carve‑outs
ConfidentialityOverly long, blanket prohibition3‑year term, allow disclosure to advisors
Dispute ResolutionHome‑court arbitration, fee‑shiftingNeutral venue, mediation first, limited fee‑shifting
MiscellaneousUnfavorable governing lawChoose contractor’s home state

How to Use These Suggestions

  1. Draft a “Redline” – Insert the proposed language directly into the original agreement, using track changes or a side‑by‑side comparison.
  2. Negotiate Incrementally – Prioritize the most critical clauses (e.g., IP, liability, termination) and be prepared to concede on less risky items (e.g., mediation vs. arbitration).
  3. Document All Agreements – Ensure any verbal promises are captured in writing and signed by both parties.
  4. Obtain Professional Review – Because enforceability can vary by state (e.g., California’s strict stance on non‑competes), have a qualified attorney review the final version before signing.

Bottom line: The contract, as written, heavily favors the client and leaves the contractor exposed to unlimited liability, loss of IP, and unilateral termination. By introducing mutuality, clear limits, and reasonable timeframes, the contractor can achieve a more balanced risk allocation while still preserving the client’s legitimate business interests.

Adversarial Contract Review

Turn this model response into notes, narration, or a short video

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output lives in our open dataset — 5K+ responses across 200 models. Take it. It’s free.

About Inception: Mercury 2

Capabilities

ConversationReasoningCode GenerationAnalysisTool Use

Categories

TextCode

Specifications

Provider
Inception
Released
2026-03-04
Size
MEDIUM
Context
128,000 tokens

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Inception: Mercury 2 vs Google: Gemini 3.1 Flash Lite Preview

Both outputs, side by side

We compare AI models for a living. On purpose. We chose this.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Prompt Lab
  • Image Generation
  • Audio Comparison
  • Leaderboard
  • Challenges

Discover

  • Insights
  • AI Creators
  • AI Tools
  • The Graveyard

Developers

  • Developer Hub
  • MCP Server
  • .llmignore
  • Badges
  • Rival Datasets

Connect

  • Methodology
  • Sponsor
  • Partnerships
  • Privacy Policy
  • Terms
  • RSS Feed
© 2026 Rival · Built at hours no one should be awake, on hardware we don’t own