Framework Guides

Keito’s Python and Node SDKs provide API clients. They do not ship automatic LangChain/CrewAI callbacks, token pricing or failure-time deletion. Wrap the work you choose to record and make expense decisions explicitly.

Framework	Pattern	Guide
LangChain	Wrap one configured Runnable invocation	LangChain
CrewAI	Wrap the crew or a chosen task lifecycle	CrewAI
Custom Python	Application-owned completed-work function	Python
Custom TypeScript	Application-owned completed-work function	Node
Terminal agents	CLI or supported Agent Skill lifecycle capture	CLI workflows

Measure a run once at the chosen level. Counting both every nested tool call and the full enclosing run can duplicate time. Keep current credentials and project/task IDs, preserve unique operation IDs across retries, and choose whether failed work should be recorded. Metadata does not grant another user’s identity or billing permission.

Assistants that support MCP can use the hosted connector through its separate OAuth and tool-confirmation flow. A chat connector is distinct from automatic capture.

REST option

Use API v2 from other languages. Running timers use create, stop and restart endpoints; completed durations can use one create request. Expense creation is a separate bookkeeping operation. Neither recording time nor adding token counts sends an invoice or transfers money.