AGENT CONNECTION

Give your agent
one safe tool.

Connect any AI runtime that can make an HTTP request. Manda keeps the delegated signer on the service, evaluates every payment intent, and returns a precise result the agent can understand.

Get integration code

The connection page never displays the private agent key or bearer token.

CONNECTION STATUS CHECKING

AGENT SERVICEChecking local service…

WAIT

DELEGATED AGENTNot loaded

OWNER SESSIONWallet not connected

LOCKED

ACTIVE MANDATEWaiting for service

UNKNOWN

Create or edit mandate

Checking whether the Manda agent service is available.

SERVICE URL/api/agent

The live site and external agent runtimes use the guarded HTTPS API. Local development connects directly to the loopback service.

AUTHENTICATIONBearer token

Load `MANDA_AGENT_TOKEN` from the ignored `.agent-api-token.local` file or your deployment secret manager.

PAYMENT TOOLPOST /pay

Send a unique request ID, supported chain, approved recipient, and positive amount in wei.

OWNER-VERIFIED ACCESS

See exactly what
the agent can do.

A wallet signature creates a short-lived browser session. After verification, this page reads the selected policy from the private service route and explains the limits without exposing service credentials.

MANDATE INSPECTORARBITRUM SEPOLIA

Authenticate the owner

Connect the policy owner and verify access to load private mandate details.

READY-TO-COPY TOOLKIT

Connect the runtime
you already use.

Manda is framework-independent. Choose a format, copy the adapter, place the token in an environment variable, and expose the function as a tool to your agent.

manda-payment.js

SECRET HANDLING

Set MANDA_AGENT_TOKEN in the agent runtime environment. Never paste the token into a prompt, browser page, public repository, or client-side bundle.

WHAT THE AGENT EXPERIENCES

One request.
A useful answer.

1
Describe the payment
The agent provides a unique request, network, destination, and amount.
2
Receive a policy decision
Manda returns allowed, approval required, limit exceeded, wrong recipient, expired, replayed, or another exact reason.
3
Use transaction evidence
An approved request returns UserOperation and transaction hashes after settlement.

BUILT AROUND LEAST AUTHORITY

The integration cannot quietly become a wallet.

The agent API exposes payment intent, policy inspection, and attributed activity. It does not expose arbitrary signing, private-key export, wallet recovery, mandate replacement, or owner revocation.

Separate signer

The agent service owns only the delegated key installed by the human.

Authenticated routes

Private policy, activity, and payment calls require a bearer token or owner session.

Replay protection

Every request ID is reserved and cannot be reused after a terminal result.

Owner override

The human can revoke the installed validation entity without moving the account.

Give your agentone safe tool.

See exactly whatthe agent can do.

Connect the runtimeyou already use.

One request.A useful answer.

Describe the payment

Receive a policy decision

Use transaction evidence