STRUCTURED DATA · ONE INVOICE · BEFORE PAYMENT

Catch unsupported freight charges before your system pays.

Compare the freight invoice you already hold with your dated contract rate card and shipment-service evidence. Receive line-level exceptions, a documented rate-cap variance and a review draft. No carrier login, document upload, phone call or automatic transfer.

Inspect a free synthetic exampleGet the machine API contract

Price and format

$0.05 USDC per authorized request · Base

POST JSON to the x402-protected /audit endpoint, using your existing compatible, separately authorized payment client. 100 audits = $5 in API fees only. There is no subscription here, and no browser/card checkout.

Inputs: invoice lines and total, a dated rate card with clause references, and shipment-service/proof codes. Prior paid invoice IDs are optional.

Evidence-based output

  1. Flags repeated paid invoice IDs for ledger review.
  2. Checks totals and matching carrier, shipment, currency and contract dates.
  3. Compares charge-code totals against caller-supplied PER_INVOICE rate caps.
  4. Holds missing service evidence rather than inventing savings.
  5. Prepares an unsent line-item dispute request.

How an AI procurement agent uses it

  1. Read the synthetic input and output for free; no wallet.
  2. Map your existing invoice, rate card and shipment feed to the OpenAPI contract.
  3. Before authorizing payment to the freight vendor, request the current 402 quote and check its chain, recipient and amount.
  4. With explicit user-approved x402 budget, call POST https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/glin-freight-invoice-payguard-x402-v1/audit once; reconcile an uncertain payment before retrying.
  5. Review holds and confirm contract facts before taking action. No API response authorizes a carrier payment or proves a recovered claim.
POST https://ozeejewwpjmabshxyitc.supabase.co/functions/v1/glin-freight-invoice-payguard-x402-v1/audit
Content-Type: application/json
Payment-Signature: [supplied by the buyer's authorized x402 client]

Body: { "invoice": {...}, "contract": {...}, "shipment": {...}, "priorInvoices": [] }

When to buy — and when not to

Good fit: a developer or AI integration with already structured invoices, rate cards and shipment records, especially where invoices are checked repeatedly.

Not a fit: only scanned PDFs, unknown contract terms, missing shipment proof or a requirement for the vendor to directly approve/refund an invoice. An OCR+full ERP integration product may be better for these cases. This API does not OCR documents, access carrier portals, issue payments or guarantee recovery.