Sidequest: Iguana Necktie, the Codename Hiding in Your Usage Endpoint

The cold open

Iguana necktie is not filler, and it is not a joke written for you. It is an internal codename: the name Anthropic's own engineers gave to one field in the usage endpoint, the field that tracks your 250 dollar cloud session credit.

How it walked into the session

You were in Stats, working out which pot of money actually pays for an ultrareview. The session had just failed to get into the Anthropic Admin API. Your normal API key got a polite 401, because that door wants an organisation key and individual accounts do not have one. So it went back to the endpoint your machinery already polls every 5 minutes, the OAuth usage endpoint that fills in the 5 hour and weekly bars in the usage command.

That response has the buckets you would expect, with plain names like seven day and extra usage. Then, sitting among them, is a key called iguana necktie. It holds a used amount in dollars, a remaining amount, a limit of 250 and an expiry date. That is the claude dot ai cloud session credit, and it was the only bucket that moved when the ultrareview ran: about 2 dollars and 36 cents at minimum, reported to 6 decimal places, which you rightly did not want rounded away.

Why a billing field is named after a lizard in formal wear

Some of this is fact and some is my inference, so here they are separately.

The fact: I searched the web and nobody has documented this name. It is not in any public docs. Anthropic's own docs do not mention it, and as far as I can find no third party has written it up either. It is a field Anthropic never meant anyone outside to read closely. The Claude Code app reads it, and so do people like you who poll the same endpoint.

The inference, which I am confident about but have not verified: it follows a very old software habit of naming features before they launch. Put two random words together, usually an adjective or object plus an animal, and you get a label that says nothing about the product. Docker names containers this way. Heroku names apps this way. Plenty of companies name internal projects this way too.

There are 2 reasons it is done on purpose.

The first is secrecy. If the field were called something like cloud session credit, anyone watching this endpoint before launch would have spotted an unannounced product in a JSON key. Iguana necktie leaks nothing. In theory you cannot even tell it involves money until you see the dollar amounts next to it.

The second is that the name sticks after launch. Once the Claude Code app reads a key, renaming it means shipping a coordinated change to the server and every client, for no visible benefit. So the placeholder stays. That is how you end up, a few months later, with a real 250 dollar grant filed under a lizard in a tie, right next to sober names like seven day scoped fable.

So "random filler name" is about half right. The name was random. Its job was to say nothing.

Why this matters for your plumbing

A codename is a promise to nobody. Anthropic can rename it, retire it, or add a sibling called something like walrus cummerbund next month, and none of that would count as breaking a public contract, because there never was one.

The session already designed for that, and theassistant built it. Its dollar bucket reader does not search for the word iguana. It looks at shape: any bucket in the response that reports a dollar limit gets picked up and shown under Banked and expiring. The codename only matters for one thing, the friendly label. Iguana necktie displays as "cloud credit", and any unknown future bucket just shows under its raw name until someone gives it a label.

The other half: if the field disappears before its expiry date, the display does not quietly drop to zero. It warns that the bucket is "no longer reported" and shows the last balance it saw. That is the same honesty rule Stats follows everywhere. "I cannot see it" is a different statement from "it is empty", and a renamed codename looks exactly like a bucket that has vanished.

The memory note from that session says the same thing: codenames are internal and may be renamed.

The estate echo

You already run this pattern. The paid API usage lane in Stats rejects unknown fields rather than guessing at them, and a provider with no price rule stores "unknown", never zero dollars. Iguana necktie is the same lesson from the other side: when someone else owns the schema, read by shape, put labels on top, and set off an alarm when something goes missing.

If you remember one thing: iguana necktie is a pre-launch codename that nobody bothered to rename, so your tools find the credit by its dollar fields, not by its name, and they treat a missing field as a warning, never as zero.