Can rates be read by our own systems?

Yes. Paqt exposes its agreement surface over the Model Context Protocol, so an agent or internal service you run can read the operative terms, including extracted rates and accessorials, directly from the agreement rather than from a copy.

We amend agreements constantly. Does that get unmanageable?

That is the case this is designed for. An amendment attaches to the clause it changes rather than existing as a separate document, so the operative agreement stays readable no matter how many amendments accumulate.

Can the assistant handle rate conversations unattended?

Inside a policy you define, yes — and it escalates anything outside it. Insurance shortfalls and liability changes can be marked always-escalate, which stops the run regardless of how routine the rest of the proposal looks.

What do we get for a claim or a billing dispute?

The operative terms as of any date, every version of the agreement, the negotiation turns that produced them, the approvals and the signature identities — exportable as a single package.

The contract says one rate. Billing uses another.

Freight agreements are amended more often than they are negotiated, and the operative rate ends up spread across an original contract, four amendments and an email. Paqt keeps the agreement and its rate schedule as one versioned object, so the current terms are a fact.

Why nobody can say what the rate is

Freight contracts are living documents. The failure is not in negotiating them — it is in keeping the operative terms knowable after the fifth change.

An original PDF and a folder of amendments: The current rate is whichever amendment someone remembers
An original PDF and a folder of amendments: Accessorial terms live in a schedule nobody reconciles against billing
An original PDF and a folder of amendments: A rate change agreed by email never reaches the contract at all
An original PDF and a folder of amendments: Fuel surcharge mechanics are described differently in two documents
An original PDF and a folder of amendments: Auto-renewal passes because the notice window was in a PDF
An original PDF and a folder of amendments: Disputes are argued from attachments, not from a record
One versioned agreement: An amendment points at the clause it changes, so the operative text is unambiguous
One versioned agreement: Rates and accessorials are structured data extracted from the executed terms
One versioned agreement: Changes agreed in the room become versions, not stray messages
One versioned agreement: Surcharge mechanics live in one clause with one version history
One versioned agreement: Notice windows are known from the document and surface before they close
One versioned agreement: Every proposal, counter and approval is in order with its timestamp

The agreements that run a freight network

Carrier and broker agreements — Master terms drafted from your standard form, with the operating requirements, insurance minimums and liability terms your network depends on.
Rate schedules — Lane rates, minimums and tier breaks held as structured terms attached to the agreement, so a rate change is a versioned amendment rather than a spreadsheet.
Accessorial terms — Detention, dwell, layover, reconsignment and fuel mechanics captured as named obligations that billing can be checked against.
Insurance and liability — Coverage minimums, cargo liability limits and indemnity positions treated as clauses with gates, so a shortfall stops the agreement rather than surfacing after a claim.
Amendments at volume — Seasonal and lane-level changes attach to the clause they modify, which keeps the operative agreement readable after dozens of them.
Renewals and evergreen terms — Notice periods and auto-renewal triggers extracted from the executed document, so an evergreen agreement renews on purpose.

Rate negotiation inside a policy you set

Rate conversations are frequent, bounded and repetitive — the ideal shape for delegation. You define the floor, the ceiling and the clauses that are never tradeable; the assistant handles the rest and escalates the exceptions.

A rate policy, not a prompt — Acceptable ranges per lane or tier, which accessorials are negotiable, and the point at which a proposal stops being yours to accept.
The back-and-forth, handled — The assistant proposes your position, responds to counters inside the policy, and keeps the conversation moving without waiting for someone to open an inbox.
Escalation on the real exceptions — Insurance shortfalls, liability changes and rates outside the policy arrive as a decision with both positions attached.
Agreement becomes a version — When a rate is agreed it is written into the instrument as an amendment, so the operative schedule updates with the deal instead of after it.

What operations teams need it to survive

A freight network does not pause for a contract tool. These are the properties that make the record usable at operating speed.

Knowable terms: One operative version per agreement at all times
Knowable terms: Rates and accessorials available as structured data
Knowable terms: Amendments resolved against the clauses they change
Knowable terms: Obligations extracted from executed documents
Dates that hold: Notice windows surfaced before they close
Dates that hold: Auto-renewal triggers known from the document
Dates that hold: Insurance expiry treated as a blocking condition
Dates that hold: Seasonal amendment cycles handled at volume
Dispute evidence: Timestamped, tamper-evident agreement history
Dispute evidence: Every proposal and counter recorded in order
Dispute evidence: Approvals bound to a version and an identity
Dispute evidence: Exportable record per carrier relationship

What operators press on

Can rates be read by our own systems? Yes. Paqt exposes its agreement surface over the Model Context Protocol, so an agent or internal service you run can read the operative terms, including extracted rates and accessorials, directly from the agreement rather than from a copy.
We amend agreements constantly. Does that get unmanageable? That is the case this is designed for. An amendment attaches to the clause it changes rather than existing as a separate document, so the operative agreement stays readable no matter how many amendments accumulate.
Can the assistant handle rate conversations unattended? Inside a policy you define, yes — and it escalates anything outside it. Insurance shortfalls and liability changes can be marked always-escalate, which stops the run regardless of how routine the rest of the proposal looks.
What do we get for a claim or a billing dispute? The operative terms as of any date, every version of the agreement, the negotiation turns that produced them, the approvals and the signature identities — exportable as a single package.