Agent infrastructure · Paid

LockMyAction
Make sure your agent only does it once.

Retries are normal. Duplicate refunds, emails, orders, and destructive actions are not. LockMyAction gives an agent a durable idempotency key outside the model before it acts.

1. Lock refund-order-82731
2. Execute the external action only when safe_to_execute: true
3. Complete using the returned lock_id
Retry? The same key returns already_completed

What it solves

An agent can lose a response after an external action already succeeded. Without persistent state it may retry and perform the action again. LockMyAction makes the claim atomic and stores completion state independently of the model.

Important: checking an action is not enough. The integration should call lock_action and execute only when that call returns safe_to_execute: true.

Current behavior

  • Default active lock: 5 minutes.
  • Default completed-action protection: 30 days.
  • Completion protection can be configured from 1 hour to 1 year.
  • A stale lock_id cannot complete a later reacquired lock.
  • All operations are scoped to the paid API key.

Try LockMyAction

Uses your paid ScrubMyText API key. The key stays in this browser field and is sent only to api.scrubmytext.com for the requests you make.

Result will appear here.

Each authenticated operation counts as one API call.

REST endpoints

POST /v1/actions/lock
POST /v1/actions/check
POST /v1/actions/complete
POST /v1/actions/release

MCP tools

lock_action
check_action
complete_action
release_action

Developer docs →

Read the idempotency guide →