AgentPMT - The Agentic Economy

Multi-Protocol Bridge

Communications
$0.05/requestMin Purchase: 20Min Purchase Price: $1

Details

Protocol Bridge is an HTTP gateway that enables AI agents, automation workflows, and modern applications to interact with traditional network protocols without native protocol support. It translates simple HTTP requests into FTP, SSH, and MQTT operations, making it easy to integrate file transfers, remote command execution, and IoT messaging into any system that can make web requests. The tool supports secure connections including FTPS, SSH key authentication, and MQTTS with TLS, ensuring enterprise-grade security for sensitive operations. Connection details can be passed via intuitive URL strings or explicit parameters, giving developers flexibility in how they configure each action. Protocol Bridge is ideal for building automation pipelines, connecting legacy infrastructure to modern APIs, orchestrating DevOps tasks, and enabling large language models to perform real-world actions across diverse systems. For email sending workflows, use the dedicated SMTP Mailer tool which provides a streamlined interface specifically optimized for email delivery.

Use Cases

FTP file upload automation, FTP file download, secure FTPS file transfer, remote directory listing, automated file deletion, SSH remote command execution, server administration automation, DevOps task orchestration, IoT MQTT message publishing, sensor data transmission, smart home device control, MQTT broker integration, AI agent protocol access, LLM tool integration, workflow automation, legacy system integration, HTTP to FTP bridge, HTTP to SSH gateway, HTTP to MQTT proxy, no-code automation backend, serverless protocol access, cloud function protocol support, CI/CD pipeline integration, infrastructure automation, remote server management, file synchronization, backup automation, system monitoring automation

Parameters

(required properties listed first)

action*required
Type:string
Description:Use 'get_instructions' to retrieve documentation. Protocol action to execute
Allowed values:
get_instructionsftp_uploadftp_downloadftp_listftp_deletessh_executemqtt_publish
url
Type:string
Description:Protocol URL containing host, port, credentials, and path. The URL scheme determines the protocol and encryption. Examples: • FTP Upload: ftp://user:pass@ftp.example.com:21/path/to/file.txt • FTPS (secure): ftps://user:pass@ftp.example.com:21/path/file.txt • SSH: ssh://user:pass@server.example.com:22 • MQTT: mqtt://user:pass@broker.hivemq.com:1883/topic/name • MQTTS (TLS): mqtts://user:pass@broker.hivemq.com:8883/topic/name For SSH with key auth, omit password and provide private_key in options. For FTP list operations, path should be directory: ftp://user:pass@host:21/directory/
content
Type:string
Description:Content to send, upload, or execute. Usage varies by action: • ftp_upload: File content to upload (text or base64-encoded binary) • ssh_execute: Shell command to execute (e.g., 'ls -la /home/user') • mqtt_publish: Message payload (can be plain text or JSON string) • ftp_download: Not used (download returns content) • ftp_list: Not used (list returns directory contents) • ftp_delete: Not used (delete requires confirm_delete in options) For binary files, set content_encoding to 'base64'.
content_encoding
Type:string
Description:How content is encoded. Use 'base64' for binary files (images, PDFs, etc.), 'text' for plain text. Default: text
Default:text
Allowed values:
textbase64
options
Type:object
Description:Optional action-specific settings. All fields are optional unless noted. • FTP Options: - return_base64 (boolean): Return downloaded file as base64 (ftp_download). Default: false - recursive (boolean): List directories recursively (ftp_list). Default: false - confirm_delete (string): Must be 'DELETE' to confirm file deletion (ftp_delete). Required for delete. • SSH Options: - timeout (integer): Command timeout in seconds. Default: 30 - private_key (string): SSH private key in PEM format for key-based auth - known_hosts (string): SSH known hosts string for host verification • MQTT Options: - qos (integer): Quality of Service level (0=at most once, 1=at least once, 2=exactly once). Default: 0 - retain (boolean): Broker retains message for future subscribers. Default: false - client_id (string): MQTT client identifier. Auto-generated if not provided. Example: {"qos": 1, "retain": true} or {"timeout": 60}

API Example

curl -X POST "https://api.agentpmt.com/products/purchase" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: your-api-key-here" \
  -H "X-Budget-Key: your-budget-key-here" \
  -d '{
    "product_id": "6948d263b54506f955d789f0",
    "parameters": {
      "action": "get_instructions",
      "content_encoding": "text"
    }
  }'

Login to view your API and budget keys. The example above uses placeholder values. Sign in to see personalized code with your actual credentials.

About The Developer

Apoth3osis logo

Apoth3osis

★13 stars

Joined Agent Payment: August 14, 2025

We build tools that enable AI agents to excel in the mathematical realm.

Our small team develops experimental and unique solutions in the AI arena, with a strong focus on modular computing for agentic applications and custom model deployment. We have handled projects for a variety of applications across many sectors, from algorithmic trading and financial analysis, to molecular simulations and predictions, to habitat and biodiversity monitoring and wildlife conservation.