Skip to main content

Audit before effect

The reason teams give Yekar.AI agents real credentials is simple: nothing happens outside Yekar.AI without a record of it being written first.

Before an agent or flow calls an integration or a model, Yekar.AI opens the audit record - the request, whose account it acts as, whether the call reads or writes, and the fact that it started. Only then does the call go out. When it returns, the same record is completed with the outcome and how long it took.

That ordering is what makes a session a trustworthy account of the work rather than a summary of it. You can hand any session to a colleague, an auditor, or a customer and it will show what was actually attempted, with the exact arguments.

What you see, and where​

Open any session and expand Show details on a turn. Every tool call is there with its input, output, duration, and read/write nature. Flow runs record the same way, anchored to the step that made the call. Nothing is written after the fact and nothing is reconstructed from logs.

Work that pauses for a person​

An agent tool you've chosen to gate is recorded before it reaches the approvals inbox, so the pending call is visible in the session with its exact arguments while it waits. Approving it stamps your decision onto that same record and lets the already-recorded call execute. Rejecting it closes the record without the call ever going out.

This is why an approver can make a real decision: they are looking at the actual request, not a description of one.

If a call is interrupted​

If something fails mid-call - a network drop, a provider timeout - the record stays open, marked as started with an outcome that is unknown. That is deliberate. An open record tells you exactly where to look in the external system; a missing record would tell you nothing at all.

Because the far side is someone else's system, Yekar.AI cannot make a remote operation and its own database commit together. What it can guarantee is that you always know a call was attempted, and that is the guarantee that lets you reconcile.

Where to go next​

  • Credential handling - which account a tool call acts as, and how the secret is protected.
  • Permissions - who inside your organization can build, run, and approve.
  • Sessions - reading the record itself.