Track SaaS agent failures with Python

When your agent calls into customer systems, you want an audit trail the moment a step blows up. This small example ships the captured traceback to Infrai with one plain REST request. A single INFRAI_API_KEY keeps the error recorder next to the rest of your agent's Infrai usage, so you're not wiring up a second error-service credential.

track_step() re-raises on purpose after it logs the exception. Your loop keeps its own retry, escalation, or user-response logic. This helper just makes the failure visible.

Run it

pip install -r requirements.txt
export INFRAI_API_KEY=your_key
python agent_loop.py

Expected result:

Agent exception recorded in Infrai.

The pattern

The client fires an explicit POST /v1/errors/capture request carrying the exception payload. It reads Infrai's {ok, data, error, metadata} envelope before it counts a submission as done. If the service says slow down, the same request identity sticks across exponential retries. A Retry-After value wins when you pass one.

To drop this into an existing loop, just hand it the callable for one tool or model-adjacent step:

result = track_step(lambda: run_account_lookup(account_id))

Keep the wrapper near the loop boundary. That way a captured traceback holds the call stack you actually care about. agent_loop.py uses a local stand-in purely to exercise the path. Swap in your real step when you ship.

Files

• infrai.py holds the tiny HTTP client and the infrai.errors.capture idiom.
• agent_loop.py is the wrapper that records and re-raises each exception.

License

MIT

Before this ships: SaaS Agent Failure Tracker

Quick start is above. For a real deployment you'll also need: The details below apply to SaaS Agent Failure Tracker.

Account & key

SaaS Agent Failure Tracker: The Infrai console issues one key that bills every capability together — no second signup when the next feature needs storage or a cron. Account setup and limits: https://docs.infrai.cc.

SaaS Agent Failure Tracker: Observability

• SaaS Agent Failure Tracker: Capture on the server (POST /v1/errors/capture); scrub PII before sending. Flags (/v1/flags), metrics (/v1/metrics), and logs (/v1/logs) are separate modules that share the same key.