ScrubMyText sponge mascotScrubMyText
Free action identity · Paid atomic locking

LockMyAction
Make sure your agent only does it once.

Retries are normal. Duplicate refunds, emails, orders, and destructive actions are not. LockMyAction can derive a stable identity from the action itself and atomically reserve it before execution.

1. Describe the action and identity-defining JSON arguments
2. Fingerprint + lock in one atomic request
3. Execute only when safe_to_execute: true
4. Complete using the returned key and lock_id

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. lock_action_intent derives the key and makes the claim atomic, so safety does not depend on a model inventing a consistent identifier.

Important: execute only when the lock response returns safe_to_execute: true. A fingerprint identifies an action; it does not authorize or execute it.

Current behavior

  • fingerprint_action is free, stateless, and stores no action arguments.
  • Equivalent object-key order produces the same fingerprint.
  • 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.
Five-minute integration

Fingerprint and lock a structured action

curl https://api.scrubmytext.com/v1/actions/lock-intent \
  -H "Authorization: Bearer smt_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"send_invoice","scope":"production","arguments":{"invoice_id":"inv_42","customer_id":"customer_7"}}'

Use the returned key and lock_id with the existing complete or release operations. Use the same request without authorization at /v1/actions/fingerprint when you only need a stable identity and no reservation.

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 →

Run the developer quickstart →Read the idempotency guide