Skip to main content
Every end user accepts the Polymarket US legal document set during onboarding, inside your app. This page covers the required documents, the acceptance language and flow, and how agreement versioning works. You can build against this now — the structure will not change. Identity verification (KYC), funding, and account provisioning are covered in the Integration Journey and the KYC documentation.
Regulatory context. Polymarket US is a CFTC-regulated marketplace for event contracts. Two distinct regulated entities are party to the customer relationship: QCX LLC d/b/a Polymarket US, the Designated Contract Market (DCM), and QC Clearing LLC d/b/a Polymarket Clearing, the Derivatives Clearing Organization (DCO).

​
Required documents

Four documents make up the complete legal set. No additional terms and conditions apply beyond these four. The Participant Agreement is a click-through agreement: its first-page language makes clicking “I Accept” the legal equivalent of a manual signature. Customers accept the unmodified document through an affirmative in-app action; it is not filled out or signed by hand.

​
Acceptance flow

Display the following language, exactly as written, immediately above the acceptance button. The four document names must render as live hyperlinks to the documents in Required documents:
“By clicking below, I hereby (i) acknowledge that I have read and understood, and consent to the terms of the Participant Agreement and the Rulebooks (Polymarket Clearing Rulebook, Polymarket US Rulebook) and (ii) certify that I will abide by the Rules stated therein, as may be amended from time to time, and any applicable laws or regulations affecting PMUS, my use of PMUS and the transactions executed and/or cleared through PMUS. I also hereby acknowledge that I have read and understood the Risk Disclosure.”

​
Requirements

​
Agreement versioning

The KYC start request (POST /v1/kyc/start) carries an agreement.version field identifying the version of the Participant Agreement the customer accepted. Version value. The version is the effective date of the current Participant Agreement, formatted MM.DD.YYYY. The current value is 08.06.2026.
How updates work:
  • Notice of agreement updates is posted on the Polymarket US website.
  • When the agreement is updated, the new effective date becomes the value to send in agreement.version.
  • The updated Participant Agreement publishes automatically to its location in Required documents, so the document link in your acceptance flow always resolves to the current version.
Do not hard-code the version. Treat the version value as configuration your system can rotate without a code change.

​
Next steps

Start KYC

Submit the accepted agreement.version on POST /v1/kyc/start.

Onboard Participants

How acceptance fits into the wider participant onboarding flow.