It returned an identifier and produced nothing
An exhausted quota returned a success with a session id and no artifact, and the message pointed at the prompt. The misdirection cost more than the outage.
api
5 posts
The banking API that deliberately will not tell you things
Fineract exposes a restricted self-service namespace rather than the full API. What it omits is a design decision, and it shapes the whole client.
Design for the API call you cannot take back
An API with create but no delete changes where your guards live. Four checks that run before the request, and the one that only exists because a create returns 201 on the wrong target.
Every action your AI agent takes should be safe to run twice
Agents retry after ambiguous failures, so every action needs to be safe twice. Ledgers, content checks and dry runs — and the create that is genuinely not idempotent.
Read the status code before you believe the README
Six documented endpoints, two that work. Probing an API's real surface takes a minute and changes the architecture you build on top of it.