Skip to content

Optional mandate check before codflow executes a consequential action? (free, no dependency) #88

Description

@tolegm

Hi @bighadj22 - I'm building AstraNL, a non-custodial coordination protocol for AI agents (Netherlands, KvK 88449335). Found codflow while looking for MCP servers where an agent can actually commit money or a booking on someone's behalf - purchase is exactly that surface.

One thing MCP itself doesn't cover: when an agent calls such a tool, your server can't tell whether the human behind the agent really authorised that spend (scope, ceiling, time window), and nothing durable remains afterwards for a dispute.

We shipped a two-call handshake for that:

  • POST https://astranl.com/api/amh/verify before the action - returns ok / ceiling / window for the agent's mandate
  • POST https://astranl.com/api/amh/seal after it - a sealed, publicly verifiable receipt

Free, no custody (AstraNL never touches payment), no SDK - two HTTP calls. Docs: https://astranl.com/api/amh

Not asking you to change defaults. Would an optional flag in codflow that calls verify before the consequential tool runs (when a mandate is present) be welcome? Happy to send a PR. Equally happy to hear this is noise for your use case - one reply either way and I won't follow up.

  • Oleh, AstraNL (Zaandam)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions