failproofai-sdk

Solid

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?" Trigger when the user wants to: • plan an integration — which points in their agent loop to record, and what the platform must see before sessions, errors, and evals work at all; • write or fix instrumentation — add the `failproofai_sdk` Python SDK to an agent codebase, thread session/agent identity through it, emit tool, model, hook, or human events; • verify it — confirm events are being written, or debug an integration that looks correct and produces nothing. Served by the `failproofai_sdk` Python SDK, inside the user's own agent. NOT for reading telemetry that already landed or operating a deployment (that's `fp-cloud-cli`), or building the evaluator service that scores runs (that's `agenteye-evaluator`).

AI & Automation 5,161 stars 499 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Failproof AI Python SDK 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. ## 1. Install it ```bash 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. **One command to never run: `pip install agenteye`.** That name belongs to a stranded release of an old CLI — a different product that shipped under it before moving to `fp-cloud-cli`. PyPI versions cannot be withdrawn, so the name still resolves to that build forever. You get the CLI, `import failproofai_sd...

Details

Author
FailproofAI
Repository
FailproofAI/failproofai
Created
5 months ago
Last Updated
today
Language
TypeScript
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

fp-cloud-cli

The way to answer "how are my production AI agents doing?" and to run the team's agent-observability deployment — reach for it even on casual phrasing that names no tool. Trigger when the user wants to: • inspect agent telemetry — did agents error/fail/go flaky; sessions, events, latency, token usage, slowest models; eval/quality scores and whether quality dropped; • operate the deployment — ack/assign/resolve/mute/dismiss issues (alerts, reports, and audit findings) with notes; run and triage audits; see who has access and change roles (e.g. read-only); create or scope API keys (e.g. a push-only CI key); change settings; run saved or ad-hoc ClickHouse queries. Served by the `fp` CLI against FailproofAI Cloud. NOT for writing or designing an evaluator service / scoring logic (that's `agenteye-evaluator`), adding SDK/instrumentation to your app (that's `failproofai-sdk`, imported as `failproofai_sdk`), debugging the collector/daemon, or unrelated dev work (why a build/CI run failed, rotating non-FailproofAI Cl

5,161 Updated today
FailproofAI
AI & Automation Featured

ai-agent-reliability

Make an AI agent or automation reliable enough to trust — the tests, checks, and guardrails that catch its failures before they reach anything real. Use when asked how do I test my AI agent, make my automation reliable, my agent works sometimes, or how do I trust an AI workflow in production. Produces a map of where the agent can fail (bad input, hallucination, wrong tool call, edge cases, silent errors), the checks that catch each (validation, evals on real cases, human-in-the-loop gates, monitoring), a right-sized reliability plan scaled to the stakes, and a rollout that earns trust incrementally — so an agent that works in a demo becomes one that works in reality. For builders putting AI agents into real workflows.

1,404 Updated today
mohitagw15856
AI & Automation Listed

openai-agents-sdk

This skill builds AI agents with the official OpenAI Agents SDK for Python (`pip install openai-agents`), from hello world to professional production systems. Use whenever the user is writing agent code with the `agents` package — Agent, Runner.run/run_sync/run_streamed, @tool / function_tool, handoffs, agents-as-tools, input/output/tool guardrails, structured outputs (output_type), sessions & memory, RunConfig, ModelSettings, tracing, MCP servers, or multi-agent orchestration. Also use for questions about how the SDK works, its current API surface, or converting an idea into an agentic app. Provides the correct, docs-grounded API (no guessed imports).

6 Updated 1 months ago
sheikh-mohammad