failproofai-sdk
The way to make an AI agent report what it did to Failproof AI — planning what to record, writing the instrumentation, and proving the events land. Reach for it on vague phrasing too: "add observability to my agent", "why isn't my agent showing up?"
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 5121
- Лиценз
- NOASSERTION
- Последна проверка на записа
- 21.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add FailproofAI/failproofaiСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Failproof AI SDK — Python and TypeScript
Two packages, one pipe: failproofai-sdk (Python, imported as failproofai_sdk)
and @failproofai/sdk (TypeScript/JavaScript). They write the same 15 events in
the same wire format into the same spool directory. Everything in this file is
language-neutral unless it says otherwise, and code blocks are Python.
For a TypeScript or JavaScript agent, read references/typescript.md alongside
it: it has the camelCase names, the adapters, bundler and Next.js setup, the
no-framework wiring, shutdown and verification. Both packages also ship the
evaluator worker that scores finished sessions on your own infrastructure (§7,
references/evaluator.md).
The SDK records what your agent did, from inside your agent. You call it at points
you choose; it appends structured events to local .jsonl files. A separate
collector ships those files to the platform.
your agent calls failproofai_sdk.event.*
→ SDK queues it in memory
→ flush thread writes <base_dir>/events/event-<timestamp>.jsonl
→ collector picks the file up and ships it
→ visible as sessions / events / errors / evals
The SDK's job ends at the file. That boundary is the most useful thing to know
about it: everything up to the .jsonl is yours to get right and yours to verify,
and it is verifiable on a laptop with no server, no API key, and no network.
The API is small — 15 event methods, all keyword-only. The hard parts are deciding where to call them and knowing which silences are bugs, because this SDK does not raise when you get it wrong. Sections 1-3 are the plan, 4 is the code, 5-6 are the proof, 7 is scoring the runs.
1. Install it
TypeScript/JavaScript: npm install @failproofai/sdk — zero dependencies, Node ≥
20.9, Bun or Deno, ESM and CommonJS. The npm name has no lookalike trap; the rest of
this section is Python. See references/typescript.md.
pip install failproofai-sdk # or: uv add failproofai-sdk
The distribution is failproofai-sdk and the import is failproofai_sdk. Public
PyPI, no token, no dependencies.