Deploy and Host pumplexity-dex-agent on Railway

pumplexity-dex-agent is a self-hosted Solana trading agent. It receives signals from the Pumplexity API and executes them on-chain via Jupiter using your own wallet. Funds, keys, and the open-position ledger stay in your Railway service — non-custodial by design. One agent serves any number of strategy subscriptions.

About Hosting pumplexity-dex-agent

The agent runs as a long-lived Node.js v22 Fastify service. It exposes POST /execute for the Pumplexity API to dispatch trade events, and calls back to pumplexity-api for swap quotes and trigger-order placement. Both directions are authenticated by a single AGENT_KEY issued at agent registration. Your SOLANA_PRIVATE_KEY is held only in this service's environment and signs each trade locally before broadcasting. A small SOL balance in the agent wallet covers transaction fees and the auto-topped-up $PLEX gas reserve. Mount a Railway volume at /data if you want the open-position ledger to survive redeploys.

Common Use Cases

• Auto-execute Pumplexity smart-wallet copy-trade and signal strategies without surrendering custody of funds or keys
• Run multiple Pumplexity strategy subscriptions through a single agent on one Railway service
• Self-host a non-custodial trading layer that can be paused, key-rotated, or shut down at any time from the Pumplexity My Agents page

Dependencies for pumplexity-dex-agent Hosting

• A registered agent on Pumplexity (yields the AGENT_KEY, shown ONCE at registration)
• A Solana wallet you control, exported as a base58 private key, used for SOLANA_PRIVATE_KEY

Deployment Dependencies

• Pumplexity agent registration: app.pumplexity.com/agents
• Source repository: github.com/pumplexity/pumplexity-dex-agent
• (Recommended) Free Helius RPC for reliable transaction broadcasts: helius.dev — paste the Mainnet RPC URL into the optional SOLANA_RPC_URL variable
• Solana wallet capable of base58 private-key export (Phantom, Solflare, or any compatible signer)

Implementation Details

Two required environment variables, both Sensitive:

• AGENT_KEY — issued at app.pumplexity.com/agents on agent registration, shown ONCE. Authenticates both inbound dispatches (X-Agent-Key header) and outbound calls back to pumplexity-api (x-api-key header).
• SOLANA_PRIVATE_KEY — base58 export of the agent wallet keypair. Signs every trade and the API-dispatched $PLEX top-up swap.

Optional environment variables:

• SOLANA_RPC_URL — defaults to the public Solana mainnet RPC, which rate-limits and drops broadcasts under load. Override with a Helius / QuickNode / Triton URL for production reliability.
• PUMPLEXITY_API_URL — defaults to https://api.pumplexity.com. Override only for staging or local development.
• AGENT_LEDGER_PATH — defaults to ./data/agent-ledger.json. Point at /data/agent-ledger.json with a mounted Railway volume so open positions survive redeploys.

After deploy: copy the Railway service's public URL, paste it into the agent's URL field at app.pumplexity.com/my-agents, fund the agent wallet with a small amount of SOL, then subscribe to any strategy and pick this agent from the dropdown.

Why Deploy pumplexity-dex-agent on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying pumplexity-dex-agent on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.