Tracking TinyFish Agent runs

Short answer. Meridian attributes completed TinyFish Agent runs that arrive through a LiteLLM pass-through. Each run with a cost lands on the agent mapped to that virtual key, at the cost LiteLLM recorded. A pass-through run with no cost is not stored. Browser minutes are not on this path.

Where to set it up

The full steps are TinyFish Agent runs via LiteLLM. LiteLLM itself is the LiteLLM guide.

1. Point TinyFish at the LiteLLM proxy with a virtual key, one key per agent.
2. Open Settings → Keys & API → Gateway key registry. Hashes Meridian has seen with no mapping are under Unmapped keys. Assign each hash to its agent.
3. On Agents & allocation, give that agent a department and an owner. A cost center on the registry is stored on the event. It can set the department when every event for that agent and day has the same cost center and the value matches one department, or a cost-center mapping. The agent stays the one from the key.
4. After the next ledger rollup, at 20 minutes past the hour UTC, the run is on that agent. The provider is tinyfish and the model is tinyfish/automation-run.

Runs that arrived before the mapping stay on Agents & allocation → Unattributed until you assign them. Later runs from the mapped key land on the agent.

Browser minutes are not on this path. A direct TinyFish connection is not available yet.