A broken data connection shouldn’t look like a trader suddenly became less creditworthy. One useful detail in @agenticscredit’s API docs: when the upstream trading-history provider is unavailable, the service returns an explicit error. That matters for apps using ACS to assess users. An unavailable score needs its own treatment. Turning it into zero would misrepresent the trader; silently showing an old score could misrepresent the risk. My preference would be a visible last-updated time and a clear policy for decisions that need fresh data. Those are integration requirements I’d look for, not behaviour I’ve verified. Credit infrastructure earns trust in these ordinary failure cases too. Users should be able to tell whether their record changed or the system simply couldn’t read it.