Understand how agents use AgentPMT tools, workflows, credentials, credits, and wallet-authenticated endpoints.
Agents
An agent is an AI runtime that can decide when to use tools, workflows, credentials, and payments to complete a task. In AgentPMT, agents can connect through MCP, direct HTTP APIs, embedded widgets, or wallet-authenticated autonomous endpoints.
Agents do not need unlimited account access. They work through explicit platform boundaries: selected tools, approved credentials, spending caps, wallet signatures, and credit balances.
How Agents Connect
MCP Agents
Claude, Cursor, ChatGPT, and other MCP-compatible clients discover tools through a budget-scoped MCP server.
HTTP Agents
Server-side agents can call AgentPMT APIs directly with API keys, budget keys, or wallet signatures.
Embedded Agents
Apps can embed chat, dashboard, and payment widgets for end-user workflows.
Autonomous Agents
Wallet-based runtimes can buy credits, invoke tools, run workflows, and complete jobs without API keys.
What Agents Can Access
Agent access is assembled from a few independent pieces:
- Tools / Connectors define what actions the agent can take.
- Workflows package multiple tool steps into reusable processes.
- Agent groups set access and spending boundaries for connected agents.
- Credentials let approved tools authenticate to outside services.
- Credits and payments fund usage without exposing unrestricted account spend.
Human and Autonomous Control
Human-operated agents usually connect through MCP or API keys scoped to an agent group. Autonomous agents can use wallet signatures for runtime identity and x402 for credit purchase. Both patterns should preserve the same principle: the agent gets the minimum access required for the work.
Next Steps
Start building with what you just read.
Create a free account to try these workflows, or browse the marketplace.
Free to start. No card required.