Home / Home / Errors / Error: not_found

Error: not_found

The requested route or resource doesn't exist.

What it means

404 fires for unknown paths (e.g. /v1/transactions/evluate) or unknown resource IDs.

A typo in the endpoint path.

Referencing a rule, agent, or approval ID that was deleted or never existed.

Calling a hosted-only route on a self-host build (or vice versa).

Check the path against the API reference.

Verify the ID exists (list rules first, then act on a real ID).

curl -X POST https://sipi.bot/v1/transactions/evluate \
  -H "Content-Type: application/json" -d '{}'

HTTP/1.1 404
{"error": "not_found"}

Correct path: /v1/transactions/evaluate.

Does a typo in the path return 404?

Yes — unknown paths return not_found. The evaluate path is exactly /v1/transactions/evaluate.

What if a rule ID is missing?

Acting on a deleted rule ID returns not_found. List rules first to get current IDs.

One API call (or MCP tool) in front of every agent transaction — APPROVED, BLOCKED, or FLAGGED, deterministic, ~5 ms, fully logged.