Skip to content
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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
Rival
Models
CompareBest ForArena
Sign Up
Sign Up

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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
  1. Home
  2. Models
  3. Z.AI: GLM 4.7
  4. Adversarial Contract Review

See how Z.AI: GLM 4.7 compares on this challenge:

  • Z.AI: GLM 4.7 vs Claude Sonnet 4.6
  • Z.AI: GLM 4.7 vs Gemini 3.1 Pro Preview
  • Z.AI: GLM 4.7 vs Z.ai: GLM 5

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
Sign Up
Sign Up
Back to Z.AI: GLM 4.7

Adversarial Contract Review

Glm 4 7's response to the 'Adversarial Contract Review' challenge.

Z.AI: GLM 4.7
February 3, 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.

Z.AI: GLM 4.7
Response

glm-4.7 logo
Z.AI: GLM 4.7Adversarial Contract Review
glm-4.7 logo
Z.AI: GLM 4.7

Here is an analysis of the clauses in the Software Consulting Agreement that present significant risks to the Contractor, along with suggested modifications and the legal reasoning for each.

1. Scope of Work (Clause 1)

Exploitable Element:

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

The Risk: This is a "blank check" clause. It allows the Client to demand unlimited work, feature creep, or entirely new projects without paying the Contractor for the extra time. It destroys the certainty of the contract.

Suggested Modification:

"Contractor shall provide software development services as described in Exhibit A (Statement of Work). Any changes to the scope must be agreed upon in writing by both parties and may be subject to additional fees and timeline adjustments."

Legal Reasoning: A contract requires a "meeting of the minds" regarding consideration (value exchanged). If one party can unilaterally change the scope without changing the pay, the consideration becomes illusory. Defining the scope in an exhibit and requiring a "Change Order" for modifications ensures the Contractor is paid for all work performed.


2. Payment Terms (Clause 2)

Exploitable Element A:

"Payment is due within 90 days of invoice receipt."

The Risk: Net-90 terms are highly unfavorable to independent contractors. It creates severe cash flow problems, effectively forcing the Contractor to float the Client’s costs for three months.

Suggested Modification:

"Payment is due within 30 days of invoice receipt."

Exploitable Element B:

"Client may withhold payment if deliverables are deemed 'unsatisfactory' at Client's sole discretion."

The Risk: This allows the Client to refuse payment based purely on their subjective opinion, even if the code works perfectly and meets industry standards. It removes objective quality standards.

Suggested Modification:

"Payment is contingent upon the delivery of materials that meet the acceptance criteria defined in Exhibit A. If deliverables are deemed non-conforming, Client must provide a written notice of specific defects. Contractor shall be given 14 days to cure such defects."

Legal Reasoning: Contracts require objective standards to be enforceable. "Sole discretion" creates an illusory promise to pay. Requiring specific acceptance criteria and a "cure period" (a chance to fix bugs) ensures fair payment practices.


3. Intellectual Property (Clause 3)

Exploitable Element:

"...including any work created using Contractor's pre-existing IP."

The Risk: This is a massive overreach. If the Contractor uses their own proprietary code library, a generic boilerplate function, or a licensed tool to save time, this clause claims ownership of that underlying IP. This could prevent the Contractor from using their own tools for future clients.

Suggested Modification:

"All work product specifically created for the Client under this Agreement shall be the exclusive property of Client. Contractor retains all rights to its pre-existing intellectual property, methodologies, and tools. Contractor grants Client a non-exclusive, royalty-free license to use such pre-existing IP solely for the purpose of operating the delivered software."

Legal Reasoning: Vendors cannot transfer rights to IP they do not own or that existed prior to the contract. This modification protects the Contractor’s "background IP" while still giving the Client the right to use the final product.


4. Non-Compete (Clause 4)

Exploitable Element:

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

The Risk:

  1. Duration: 24 months is an eternity in software; technology changes too fast for this to be reasonable.
  2. Breadth: "Any company in the same industry" is overly broad. If the Client is a bank, this prevents the Contractor from working for any other bank, effectively banning them from their sector.
  3. Enforceability: Many jurisdictions (e.g., California) ban non-competes entirely. In others, courts rarely enforce broad restrictions.

Suggested Modification:

"For a period of 6 months following termination, Contractor agrees not to solicit services from [List of specific direct competitors of Client]. Contractor retains the right to provide services to other clients, including those in the same industry, provided Contractor does not use Client's confidential information."

Legal Reasoning: Non-competes must be reasonable in duration, geographic scope, and activity restriction to be enforceable. They should only protect trade secrets, not prevent general competition. Narrowing the definition to specific competitors and shortening the duration makes it more likely to hold up in court and less damaging to the Contractor's livelihood.


5. Termination (Clause 5)

Exploitable Element:

"Client may terminate this agreement at any time without notice. ... Upon termination, Contractor must immediately deliver all work in progress without additional compensation."

The Risk: This creates a "kill fee" scenario where the Client can fire the Contractor the moment a project is 90% done to avoid paying the final invoice, yet still demand the unfinished code.

Suggested Modification:

"Either party may terminate this agreement with 14 days written notice. Upon termination, Client shall pay Contractor for all hours worked and expenses incurred up to the date of termination, including payment for work in progress."

Legal Reasoning: Termination for convenience should require payment for services rendered. The current clause amounts to unjust enrichment (the Client gets the value of the work without paying for it). Requiring payment for work-in-progress protects the Contractor from last-minute cancellations.


6. Liability (Clause 6)

Exploitable Element:

"Contractor assumes all liability... including consequential damages, with no cap on liability."

The Risk:

  1. Consequential Damages: This covers lost profits, data loss, or reputational damage to the Client. These amounts can be millions of dollars, far exceeding the contract value.
  2. No Cap: If the software causes a glitch that costs the Client money, the Contractor could be liable for an infinite amount, potentially leading to personal bankruptcy.

Suggested Modification:

"Contractor's liability shall be limited to direct damages caused by Contractor's gross negligence or willful misconduct. In no event shall Contractor be liable for indirect, special, incidental, or consequential damages. Contractor's total liability under this Agreement shall not exceed the total fees paid by Client in the six months preceding the claim."

Legal Reasoning: Liability caps are standard in B2B contracts to ensure risk is proportionate to reward. Excluding "consequential damages" protects the Consultant from being liable for the Client's business losses that are beyond the Contractor's control.


7. Indemnification (Clause 7)

Exploitable Element:

"Contractor shall indemnify Client against all claims... regardless of fault."

The Risk: Indemnification means the Contractor has to pay for the Client's legal defense and damages. "Regardless of fault" means if the Client breaks the software or misuses it and gets sued by a third party, the Contractor still has to pay for it.

Suggested Modification:

"Contractor shall indemnify Client against claims alleging that the software infringes on a third-party intellectual property right, provided such infringement is not caused by Client's modification of the software or Client's specifications."

Legal Reasoning: Indemnification should be a safety net for specific risks (like IP theft), not a blanket guarantee. A party should not be forced to indemnify the other side for losses that are not their fault.


8. Dispute Resolution (Clause 9)

Exploitable Element:

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

The Risk:

  1. Jurisdiction: Fighting a legal battle in the Client's home state is expensive and inconvenient (travel costs, hiring local counsel).
  2. Loser Pays: This discourages the Contractor from suing for legitimate unpaid invoices because they fear losing and being stuck with the Client's expensive legal bills.

Suggested Modification:

"Any disputes shall be resolved through binding arbitration in the Contractor's home jurisdiction [or a mutually agreed neutral location]. Each party shall bear its own attorney fees and costs."

Legal Reasoning: "Forum selection" (choosing the court) should be neutral. The "American Rule" (each party pays their own fees) is standard; switching to "Loser Pays" creates an imbalance of power that favors the wealthier party (the Client) and deters justice.

Adversarial Contract Review

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

Auto NotesTranscriptNarrateVideo Cut

Partner link

This output is part of our open dataset — 5K+ AI responses across 200 models

About Z.AI: GLM 4.7

Capabilities

ConversationReasoningCode GenerationAnalysis

Categories

TextCode

Specifications

Provider
Openrouter
Released
2025-12-22
Size
LARGE

Keep exploring

SAME PROMPT

Claude Sonnet 4.6's version

Same prompt, different result

COMPARE

Z.AI: GLM 4.7 vs Gemini 3.1 Pro Preview

Both outputs, side by side

Compare AI vibes, not scores. Side-by-side outputs across the world's best models.

@rival_tips

Explore

  • Compare Models
  • All Models
  • Leaderboard
  • Challenges

Discover

  • 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