DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to hold high-value API calls until a person approves them with Agent Safe Pipeline

Route consequential HTTP requests through a gateway that holds the risky ones for approval.

Who it is forAn operations lead running an AI agent that calls a payments or customer-records API, who wants a person to approve actions above a certain level.

The problemConsequential requests from an agent should not reach the target without review, but small routine requests should not wait on a person.

The outcomeA large payment returns 202 and is held without reaching the upstream, while a small payment is forwarded once with its dossier id.

What you need first

  • A terminal on macOS or Linux, with Homebrew, a Linux package, Docker or Helm available
  • An HTTP API or tool endpoint you want the gateway to sit in front of, or the local demo target on localhost:3000
  • Optional: a Decionis key from `agentsafe login`, if you want decisions from the Decionis control plane instead of the local demo authority

Steps

  1. Install AgentSafe with Homebrew: brew tap decionis/agent-safe https://github.com/decionis/agent-safe-pipeline && brew trust decionis/agent-safe && brew install agentsafe
  2. Start the gateway in front of your API: agentsafe proxy --upstream http://localhost:3000 --port 8080
  3. Send a large payment through the gateway: curl -i -X POST http://127.0.0.1:8080/payments -H 'content-type: application/json' -d '{"amount": 500}'
  4. Check that the response shows Execution HELD and that the upstream received nothing.
  5. Point the agent's HTTP base URL at http://127.0.0.1:8080 instead of the target service. (inferred, check the README)

Prompt for your agent

Using the decionis/agent-safe-pipeline repository, install AgentSafe and start `agentsafe proxy --upstream <your-api-url> --port 8080`. Send one POST request to /payments through the gateway with an amount above the approval threshold, and report the decision and the HTTP status. Verify that the upstream received no request for that call.

Caveat. The approval step uses a loopback double that simulates the Presence ceremony for examples and proves nothing about a real human approval.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page