Yes. Pause its smart contract, revoke its API keys, or end its session from the dashboard. Every action takes effect within seconds and is recorded in the audit log.

No. The Credential Vault stores every credential encrypted at rest on AgentPMT servers and injects it server-side at the moment the outbound request leaves for the upstream API. The agent sees the endpoint name and the response, never the raw key, token, or password.

This is enforced by the connected-API builder: every endpoint must select an injection target (header, body, or query parameter) before it can be saved, and the credential value is bound once and never re-emitted to the agent context or the agent memory.

Agents spend USDC from a smart contract controlled budget on Base. Payments are routed through Circle programmable wallets, capped by the budget you set, and visible on chain by transaction hash.

Every tool call, credential use, payment, and outcome is written to an append-only audit log with correlation IDs. You can search by user, workflow run, agent identity, or transaction hash.

The easiest way is to download our MCP server and installer. You can find the instructions here - Integrate Your Agent You can also make calls to the tools through Rest API.

Create a free account and then go to your dashboard. Click 'Request Vendor Access'. You can create up to five tools in the starter tier. To create additional tools, upgrade your account to one of our advanced tiers.

Open the Control Center tab of your dashboard. Agent Guardrails lists every agent with a pause toggle, a spend cap, and a tool allowlist. Workflow Usage lists every active workflow and lets you pause a single workflow without affecting the rest of your fleet. The Wallets tab adds a pause toggle at the wallet level so you can stop outbound payments with a single click.

Every pause emits an audit entry and is reversible from the same screen. A paused agent cannot spend credits, call tools, or run workflow steps until you unpause it.

Every published workflow exposes a programmatic trigger at POST /api/programmatic/agent-webhooks/{workflowId}/trigger. Send an Authorization: Bearer <token> header and a JSON body with a prompt string. Optionally include your own request_id to carry a correlation id end to end.

Triggered runs pick up the same guardrails as dashboard-initiated runs: agent spend caps, tool allowlists, approval gates, and the append-only audit trail in Agent Activity. The response returns the workflow run id so you can poll status or correlate logs in your own system.

Our team takes your existing OpenAPI or Swagger specification, audits the endpoints for agent-safety, and generates an MCP server that wraps your API with credential handling built in. We can deploy the MCP server on infrastructure you control, or on ours, and we hand over auth keys, a runbook, and a rotation playbook.

A typical engagement takes a few days from spec handover to live MCP server, plus an optional 30-day support window so your team can onboard without the guesswork.

You set caps and reset periods once, and define which digital services your agent is allowed to pay for. The x402Direct smart contract checks every outbound payment against those rules before the transfer clears. A payment that would exceed a cap, or that targets a merchant outside the allowlist, is rejected on-chain with a human-readable reason.

Because the rules live in the contract rather than in agent code, changing an agent prompt cannot bypass them. You can update limits at any time from the dashboard, and each change is written to the audit trail with the actor and the new limit.