{ "item_title" : "Not an Invoice", "item_author" : [" Ravi Vale "], "item_description" : "Forward deployed engineer is a job India Today reported on 2026-07-10 can pay up to a million dollars a year - though the article would not tell an automated reader whether that is base pay or a package, The Economic Times reported the same role at $200,000 five weeks earlier, and Anthropic posts no such title at all. Nobody agrees what this job is, so nobody agrees what it pays.The Wall Street Journal's headline on 2026-07-19 was The hottest job in tech isn't very glamorous, and that matches the work. You fly to somebody else's office, log into a network you do not control, and make their mess produce something. AWS has put a billion dollars into embedding engineers like this inside its customers.Here is what no job ad mentions. Six weeks in, somebody in finance asks what the agents cost, and every number you can reach disagrees with every other one.At least three first-party figures exist for the same week of spend, all produced correctly, all documented to differ, and no page tells you by how much. Spend limits estimate spend from token counts at USD list price; they're a circuit breaker, not an invoice. The figure a developer reads off their terminal may differ from your actual bill. The reporting API finance would trust warns that values for a given date can be revised for up to 30 days. Then the holes: Priority Tier spend missing from the cost endpoint, Workbench traffic arriving with a null API key id, Claude Code on Amazon Bedrock returning no activity. None of it is hidden. It sits on free pages nobody forwarding a spend figure to finance has read.Read this before you buy it. Nothing here ran against a live gateway, an admin key, an analytics key, a collector, or a cloud provider. I have none of them. The four programs that need one - two cap proofs, the cross-API probe, the skill's command - ship syntax-checked and never executed, and each page says so in the sentence, not a footnote. What did run on a laptop, output diffed against the run that made it: the cap resolver, the flip test, the path decider, the report assembler, the two collectors and their referee. Those run against fixtures I built by hand from the vendor's pages, and every fixture carries a note field saying so. It proves the client. It does not prove the API, and the book says which is which.So you get the instrument, not a receipt. capctl resolves which of four stacked caps wins a period and prints the reason it won, and points at either a self-hosted gateway or Anthropic's public Admin API by changing one base URL, which the vendor's contract licenses. collect names the one report path your key and plan permit, enumerates what it cannot produce, and returns nothing rather than a guess when closed. recon writes a chargeback report where every row names who supplied it, the reconciliation closes to zero or prints by how much it does not, and the signature block refuses when a declared row has no cause. verify-cap.sh asserts four things about a fired cap: status 429, error type billing_error, the header x-should-retry: false, and that the cap that fired is the one the resolver named. You will run it. I could not.The first page says what you will not get. Not a smaller bill, which is a different craft. Not an invoice-grade total for the last thirty days, because the vendor tells you to query dates thirty days back. Not a booted gateway, which a sibling volume owns. Every technical claim traces to an official page with its URL and the day it was read, and verify.sh prints NOT PROVEN with a reason where no script can settle it.", "item_img_path" : "https://covers4.booksamillion.com/covers/bam/9/79/819/127/9798191276267_b.jpg", "price_data" : { "retail_price" : "69.99", "online_price" : "69.99", "our_price" : "69.99", "club_price" : "69.99", "savings_pct" : "0", "savings_amt" : "0.00", "club_savings_pct" : "0", "club_savings_amt" : "0.00", "discount_pct" : "10", "store_price" : "" } }

Overview

Customers Also Bought

Details