The agreement is the product. The agent runs it.

Paqt is a workspace for the whole life of an agreement: the conversation, the draft, the clause-level negotiation, the signature and the record afterwards. An AI assistant executes that work under a mandate you write, with a kill switch, attributed actions and a human review queue for the steps that still need a person.

One workspace, an agent inside it

The surfaces below exist in the product today. A page on this site exists only when we can describe the mechanism, not the aspiration.

  • The room — Counterparties, counsel and reviewers share a chat room with the document, the negotiation and the signature request. The thread is the record, not a copy of a copy in someone's inbox.
  • The assistant — Given a mandate, it drafts from your library, negotiates clause by clause, routes the steps that need a person and sends for signature. It is an AI assistant, not a clerk and not a suggestion box.
  • The protocol surface — Your own agents drive the same work over Model Context Protocol. The same mandate, the same gates and the same kill switch apply whether the run started in the composer or from your system.

What we do not claim

A company page is where vendors pad. These are the rules the rest of the site is tested against, stated here so they are not a footnote on a healthcare page.

The same test covers this page. If a certification claim, a vendor name we have not announced, or an invented statistic appears in the catalog, CI fails.

  • Not on this site: Health-information and other compliance certifications we have not completed
  • Not on this site: Named third-party integrations we have not announced
  • Not on this site: Invented performance statistics, customer counts or quotes
  • Not on this site: Roadmap language dressed as a present-tense capability
  • True today: Capabilities are described in the present tense because they ship
  • True today: The agent is called an AI assistant, not a job title in a law firm
  • True today: MCP is treated as operational wherever it is mentioned
  • True today: An automated test fails the build if those rules are broken

Read the page that matches the question

Most visits here are a person trying to find a more specific page. These are the ones that answer the usual questions.

  • What the agent actually does: The AI assistant page is the run from intake to signature
  • What the agent actually does: Bot negotiation is the clause-by-clause exchange inside that run
  • What the agent actually does: MCP is how your own systems drive both
  • Trust and money: Security & control states the mechanisms and withholds the adjectives
  • Trust and money: Pricing is the same plan catalog as Settings → Subscription
  • Whether this is the right tool: Compare pages are written against categories, not named products
  • Whether this is the right tool: Each one says when the thing you already have is the better answer

Questions about Paqt

  • Is Paqt a document editor, a messenger, or an AI tool? It is the workspace those three become when they share a record. Chat, the document, clause-level negotiation and signature live in one room. The AI assistant runs that room under a mandate; it is not a third product bolted on.
  • Who is it for? Teams that close agreements as part of the work, not as a side task: law firms, in-house legal, sales and procurement, and the industries with a page under Solutions. If we cannot name the clause, date or approval that goes wrong in a sector, that sector does not have a page yet.
  • Where do I start? Start free from the login screen, no card. If you want to see the agent before you sign in, the AI assistant page is the honest tour — it is a nine-stage run, not a feature list.
  • How do I reach someone? Create an account and write to us from inside the workspace, or use the contact paths on paqt.chat. This preview site is the product tour; it is not a second support desk.