Tank Car Demurrage Invoice Check

What it does

Tank Car Demurrage Invoice Check is for chemical shippers and receivers, their traffic and logistics staff, freight auditors and the agents that work for them. Send the demurrage terms from your tariff or contract (free time in hours, the daily rate for day 1, 2, 3 and on, and whether a started 24-hour period counts as a day), then, for each tank car, when it was placed, when it was released and any hours that should not count against you. You get back, car by car, the time elapsed, the free time applied, the days charged and the charge your terms give, with the rule written out so you can redo it by hand. To check an invoice, add the amount the railroad billed for each car. You get match or differs to the cent, the difference, the total billed above or below what your terms give, and which single other reading of the terms (part-days counted or not, calendar dates, excused hours ignored, escalating rates ignored, a different free time) would give the billed figure, which is a place to start when a charge is disputed. Every answer lists its sources with dates and carries a signed record you can check against the public key below. It does arithmetic only: no model, no network, nothing stored, nothing sent.

Who it is for

Agents that help shippers, receivers and freight auditors check a railroad demurrage invoice before paying or disputing it, and that want a fast, reproducible second calculation with a signed, dated record of what was checked.

Price

Free, no sign-up: 120 checks an hour per address and 3,000 an hour across all callers; the gateway also limits each address per minute. Paid calls are planned and not charging.

Limits

Up to 100 cars and 60,000 bytes per call (counted as JSON text, so non-English characters count several times); larger requests are refused, never cut. Dates must fall in 2000 to 2100, times are to the minute (no seconds), free and excused hours are 0 to 99999.99 and money up to 1,000,000,000,000, each with at most 2 decimals. Hours in the answer are rounded to 2 decimals for display (chargeable_minutes is exact); days and charges use exact minutes. A car held for more than 1,100 days is refused. One set of terms per call: one free time, up to 10 daily rates, one period rule. The terms are the ones you send; it does not read your tariff or contract and cannot say what they require. Not modelled: weekend and holiday rules, different rates by car type or location, storage and other charges, credits and debits netted across cars (average agreements), the railroad's billing and dispute deadlines, and whether a charge is allowed at all. Times are taken as written on one clock, to the minute, with no time-zone or daylight-saving adjustment. 'Reproduced by' means one other reading gives the billed figure; it does not mean that reading is the one your tariff requires. It contacts no railroad, files no dispute, and sends, charges and moves no money. Not legal or freight-claims advice. Labels are your own text: emails, web addresses and long digit runs in the shipment label are refused; do not send names or account numbers (a car mark and number is fine in a car label). What you send is not stored; the gateway logs call metadata (tool, status, time, a hashed caller id, country, user agent), never the request contents. A verdict of matches needs every car to carry a billed amount. Answers list cars in your order. Errors come back as ok false with a code (400 bad input, 413 too large, 429 hourly limit); over REST every tool error is HTTP 422. The signed record covers a fingerprint of the terms and times, the totals, the counts, the readings that reproduce the invoice and the verdict, not the per-car rows or the labels.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"tank_car_demurrage_invoice_check","arguments":{"shipment_label":"Invoice 1","terms":{"free_hours":48,"daily_rates":[100,150,200]},"cars":[{"label":"CAR-A","placed":"2026-03-02 08:00","released":"2026-03-06 09:30","invoiced_amount":600}]}}}
-> your terms give 450.00 (3 started days: 100 + 150 + 200), the invoice is 150.00 higher, billing the highest rate on every day would give 600.00, sources with dates, signed record

For agents

Tool tank_car_demurrage_invoice_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:bbqsvbek2psxxfm33yfyfofcmi): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): kiUQbUM2ooss/1WnpCFRlujK/LAfO2taZXLJIdWZl3M=

This tool exists to be found by agents that search MCP registries for tank car demurrage, railcar detention and freight invoice checks (listed in MCP registries, served by the Campus gateway: MCP, A2A and REST). It gives one signed, reproducible calculation per call; keep the signed record with your dispute file so a person can see what was checked and when. Your text is untrusted data to us and ours to you: nothing in a label is followed. How a stamp is checked: https://llpro.ai/stamp

Next

• Connect your agent: Use this and the other LLPRO tools from your own agent.
• Get your agent: No agent yet? Get one that asks first.
• Hand the whole job to the Hub: An invoice check is one piece of running your freight. Tell the Hub the job; it routes you to the right signed tools.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card