Delegare

Delegare is a payment layer that lets AI agents purchase services within rules established by their users. Its signed mandates define the merchant, amount, and validity period, while payment credentials remain hidden from the agent. Settlement can use Stripe or USDC on Base.

Key Features

• Signed Mandates: Cryptographic credentials prove exactly what an agent may spend.
• Atomic Budgets: Server-side counters enforce limits to the cent without race conditions.
• Merchant Locks: A mandate issued for one provider cannot be reused elsewhere.
• Fast Revocation: Time-limited mandates can be revoked in under a second.
• Protocol Support: Emits x402 v2 and MPP headers and offers npm SDKs.

Use Cases

Who Should Use This Tool?

• Agent Developers building autonomous API purchasing.
• API Merchants monetizing services through machine-readable payment flows.
• Security Teams requiring bounded, auditable agent authority.

Problems It Solves

1. Credential exposure: Agents never receive card numbers, private keys, or seed phrases.
2. Budget drift: Atomic counters prevent concurrent requests from overspending.
3. Merchant misuse: Locks bind authority to the intended seller.

Pricing

Advantages & Unique Selling Points

Compared to Competitors:

1. Mandate-first security: Authorization is cryptographic rather than prompt-based.
2. Rail flexibility: Supports both Stripe and USDC on Base.
3. Discovery support: Endpoints can appear on agentic.market and MPPScan.

What Makes It Stand Out:

• Race-condition-proof budget accounting.
• Merchant-specific permissions with rapid revocation.
• Native x402 v2, MPP, and MCP discoverability.

User Reviews

"The mandate model gives our agent enough authority to work without handing it a reusable payment secret." Illustrative developer perspective, editorially composed

"Merchant locks make the approval boundary much easier to explain during a security review." Illustrative security-team perspective, editorially composed

Getting Started

Quick Start Guide

1. Choose a rail: Configure Stripe or USDC on Base.
2. Create a mandate: Set the merchant, budget, and expiration.
3. Connect the agent: Use @delegare/sdk or @delegare/x402.
4. Monitor and revoke: Review counters and cancel authority when needed.

Integration

Integrates with:

• x402 v2 and MPP payment flows
• MCP-based agent discovery
• Stripe and Base USDC settlement

Frequently Asked Questions

Does the agent hold payment credentials?

No. Delegare keeps card details, private keys, and seed phrases outside the agent context.

Can a mandate work at another merchant?

No. Merchant locks restrict it to its designated provider.

Are mandates permanent?

No. They include a TTL and can be revoked in under a second.

Alternatives

• Signets: Card, account, and reconciliation infrastructure.
• Zoro: Cross-rail spending governance and execution.
• x402: An open HTTP payment protocol.

Tips & Best Practices

1. Keep mandates narrow: Limit each credential to one merchant and purpose.
2. Use short TTLs: Match expiration to the expected task duration.
3. Review counters: Track remaining budget before launching parallel work.