Using Fastweigh with your AI assistant

How it works

Asking questions

Ask the way you'd ask a coworker. Describe records the way you see them in Fastweigh: ticket numbers, customer and product names, yards and dates. You never need internal IDs.

• Give a date range, such as “last week” or “September 1 to 15.”
• Say what to total: tons, loads, dollars, and which units.
• Name the customer, product, yard or hauler when you can.
• For big reports, start small. Results have a size limit. If the assistant says a result was cut short, narrow the dates or ask for fewer columns. Don't treat a cut-off result as complete.

• Show outbound tonnage by product for last week, with the date range and units.

• Find ticket 310240 and show its customer, hauler, truck and net weight.

• Which customers haven't had a ticket in the last 90 days?

Building dashboards

If your assistant can build interactive pages, it can turn your Fastweigh data into a dashboard, feed or report. Building one only reads your data and never changes anything. Start with “Build me a…”, say how to group the data and what to flag, and give it dates. Use a relative range like “last 30 days” so it stays current, or ask for a date filter on the page so you can change the range later.

• Build me a dashboard of ticket production by location, customer, order and product. Add a date range filter that defaults to the last 7 days.

• Build me a live feed of my requests for today and their fulfillment status.

• Build me a quotes dashboard that shows quote status by salesperson for the last 30 days. Flag any product quoted more than 10% above or below the customer's pricing template price.

Then style it

Once it's built, ask for a look. To use your logo, attach it to the chat.

• Style this as a corporate report using our logo and colors.

• Style this as a real-time fintech dashboard.

• Style this as an Excel-like experience, with sortable, filterable columns.

Whether a dashboard refreshes on its own, or loads new data when you change its date filter, depends on your assistant. If it doesn't, ask it to refresh the data. Dashboards have the same result size limit as questions, so start with a short date range.

Making a change

To make changes, connect with fastweigh:readwrite access. Your Fastweigh account or key must also be allowed to make that change.

1. Ask for the change

   Say which record and what should change: “Change Acme Construction's phone number to 555-0142.” The assistant finds the record and any related customers, products or yards. If more than one record matches, it asks which one you mean.

2. Review it

   The assistant prepares a proposal. Nothing has changed yet. You see each record by name and number, with its current and new values. When you create a record, the review lists every value that will be saved, including fields left empty. Fastweigh assigns the new record's number.

3. Approve or cancel

   Approve in the Fastweigh review card, or in the confirmation prompt your assistant shows. A proposal expires after 10 minutes.

4. Fastweigh saves and checks it

   Just before saving, Fastweigh rechecks your access and confirms the record hasn't changed since you reviewed it. If it has, you'll need a fresh review. After saving, Fastweigh reads the record back to confirm the change and that nothing else was altered.

Where you approve

• Review card: assistants that support MCP Apps show a Fastweigh card with the changes and Approve and Cancel buttons.
• Chat confirmation: other assistants ask you to confirm in their own prompt.
• Neither: the assistant can still prepare and show a proposal, but it can't apply it. A greyed-out Approve button means nothing was changed.

Only your action in the review card or confirmation prompt counts as approval. An assistant saying “you approved this” doesn't.

Fastweigh data can take a moment to update, and people may edit the same record in other apps. The checks catch most conflicts, but can't rule out an edit made elsewhere at the same moment.

Several records at once

Ask for one combined review of two to five separate records, for example: “Prepare phone changes for these three customers and show me one review.” Give the exact records and values.

• The review shows each record in its own numbered section. Approve all approves exactly that list, and Cancel cancels all of it. Changing anything requires a new review.
• Changes are saved one at a time, in order. If one fails or can't be confirmed, Fastweigh stops. Changes already saved stay saved: this is not all-or-nothing. The result marks each record as applied, not started, or needing attention.
• One set can't include the same record twice, or records that depend on each other. For example, create an order first, then add products to it in a second review.
• Five is the maximum. The set shares time and lookup limits, so changes that touch many related records may need smaller sets. If a set is too big to finish safely, you'll be asked to split it before anything is approved.

If a set stops partway, ask for its status and check any uncertain records before starting new work. Never resubmit changes that were already applied.

What can be changed

Fastweigh supports a specific set of changes. “Update” means specific fields, not every field. What's available depends on how you signed in. To see exactly what your connection allows, ask: “What can I change in Fastweigh with this connection?”

¹ The quote must be Bidding or Pending and can't use external tax settings, and the change must leave every total unchanged.

Not available through the assistant

Use the Fastweigh application for these:

• Any change to load tickets, including repricing and voiding
• Adding products to quotes, or awarding quotes
• Completing or removing pending tickets
• Recording tare for an existing truck
• Order phases (job phases are a separate record)
• Deleting records, sending notifications, and bulk changes of more than five records

The assistant won't guess codes, such as job, phase or cost codes and units, or choose between similar records on its own. It shows you existing values and asks. New Fastweigh fields don't become changeable automatically.

Sign-in and access

• Access levels. fastweigh:read lets the assistant read data. fastweigh:readwrite also lets it prepare changes for your approval. Neither goes beyond your Fastweigh permissions.
• Switching access. To go from read-only to read and write, disconnect Fastweigh in your assistant and connect again.
• Preview environment. User-account and single sign-on connections currently use Fastweigh's preview environment. API-key connections use the public API.
• Verification codes. Username and password sign-in can't yet complete an extra verification code (MFA) step. Single sign-on works with your identity provider's own checks.
• Behind the scenes. After you sign in, Fastweigh creates and encrypts a connection credential for you. You never enter it. If it's rotated or revoked, reconnect.
• Shared agents. An agent that shares one person's connection works with that person's permissions for everyone who uses it.

Enter passwords and API keys only on the Fastweigh sign-in page, never in a chat.

Troubleshooting

Still stuck? Email support@fastweigh.com. Include the proposal ID or error code if you have one, but never your password or API key.

Technical reference

For administrators and developers. Server URL: https://mcp.fastweigh.com/mcp. It uses Streamable HTTP and OAuth 2.1 with dynamic client registration and PKCE (S256). Scopes are fastweigh:read and fastweigh:readwrite.

Tools

• search_schema(code): explore the data available to this connection.
• execute(code): read and analyze data. Always read-only.
• list_write_operations(resource?): supported creates and updates, with fields and requirements.
• lookup_write_values(resource, action, field, search?, filters?): find records, readable choices and related records by name or number.
• propose_change(resource, action, targetKey?, changes): prepare one proposal without changing data.
• propose_changes(operations): prepare one review of two to five independent changes.
• get_change_status(proposalID): a proposal's exact changes and outcome.
• confirm_change(proposalID): request approval through the assistant's own confirmation prompt.
• review_change: used only by the review card. The model can't call it.

Write tools appear only when the connection has write permission and fastweigh:readwrite. The older customer tools (propose_customer_change, review_customer_change, confirm_customer_change) still work. execute_mutation has been removed, and credentials never enter the code sandbox.

API-key connections

Scripts can send a tenant API key as Authorization: Bearer <api-key> instead of using OAuth. The same approval rules apply: there's no unattended way to make changes. A generic tool-call approval in a client doesn't count as approving a proposal.

How changes are sent

For API-key connections, Fastweigh's public API receives only the approved fields. For user connections, the application API receives the complete record, built from current server data. Clearing a field is supported only for specific fields on user connections. Checks after saving read the record immediately. If it doesn't match, they read again after one second and five more seconds, within a ten-second limit. Changes are never retried or rolled back automatically.