Updated Jul 23, 2026

Connect An Agent

Connect your AI agents to AgentPMT to enable tool and workflow execution. AgentPMT supports two primary connection methods: Model Context Protocol (MCP) for modern AI platforms, and REST API for custom integrations.

Choose a Connection Method

Method	Best for	Credential	Notes
Hosted MCP	Browser-hosted clients and remote MCP clients	Agent Group Bearer token	Use `https://api.agentpmt.com/mcp` when the client supports streamable HTTP MCP.
Local STDIO	Claude Code, Codex, Cursor, Zed, and local agent runtimes	Agent Group Bearer token stored by the router	Use the local router when the client needs STDIO or a local command.
Bearer REST	Server-side integrations that call platform endpoints directly	Agent Group Bearer token	Use Programmatic Access for endpoint contracts.
Wallet-authenticated autonomous API	Autonomous agents that buy credits, invoke tools, run workflows, or complete jobs	AgentAddress wallet signature and optional x402 payment	Use Autonomous Agents for the generated endpoint catalog.

MCP Integration

The Model Context Protocol (MCP) provides a standardized way for AI agents to discover and use tools from AgentPMT. This is the recommended method for connecting AI agents like Claude, ChatGPT, and other MCP-compatible platforms.

30 Second Setup

STDIO connector for Claude Code, Codex, Cursor, Zed, and other LLMs that require STDIO or custom connections.

npm install -g @agentpmt/mcp-router
agentpmt-setup

Hosted Streamable HTTPS

MCP endpoint for browser-based apps like ChatGPT, Claude, Grok, or any time you want a streamable connection with no local install.

https://api.agentpmt.com/mcp

Config Example

Use the hosted endpoint directly in clients that support remote MCP. Store your Bearer token in the client config or secret field.

AgentPMT Agent Group settings showing the Show Bearer Token action used to reveal the token for an MCP or REST client — Reveal your Agent Group's Bearer token from Control Center, then paste it into your client's config.

{
  "mcpServers": {
    "agentpmt": {
      "type": "streamable-http",
      "url": "https://api.agentpmt.com/mcp",
      "headers": {
        "Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
        "x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
      }
    }
  }
}

For platform-specific setup and the full connection guide, see Connection.

Verify the Connection

List available tools
Ask the client to list AgentPMT tools. The list should match the tools enabled on the selected Agent Group.
Run a harmless tool or workflow
Use a low-cost action with known inputs so you can confirm authentication, authorization, and result formatting.
Check Agent Activity
Open Control Center and confirm the request appears with the expected Agent Group, tool or workflow, status, and safe metadata.

Troubleshooting

Symptom	Check
Authorization fails	Confirm the Bearer token or wallet signature belongs to the intended Agent Group or AgentAddress.
Tool is unavailable	Enable the tool or workflow on the Agent Group, then list tools again.
Credential is missing	Connect the required credential to the Agent Group before retrying.
Spending cap blocks the call	Raise the cap intentionally or choose a lower-cost path such as a reusable workflow.

RestAPI Integration

For custom integrations and advanced use cases, AgentPMT provides a REST API that gives you programmatic control over tool execution, workflow management, and agent interactions.

API Overview

The REST API allows you to:

Execute tools directly via HTTP requests
Manage workflows and their execution
Handle authentication programmatically
Monitor usage and billing
Integrate with existing systems using standard web protocols

API Reference

For complete API documentation, see the Programmatic Access reference.