AgentPay Pharos
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORK | No | Network to use: 'testnet' (Atlantic) or 'mainnet' (Pacific) | testnet |
| RPC_URL | No | RPC URL for testnet | https://atlantic.dplabs-internal.com |
| CHAIN_ID | No | Chain ID for the network | 688689 |
| PRIVATE_KEY | Yes | Your wallet private key (dedicated, low-value key) | |
| FACILITATOR_URL | No | Facilitator URL for x402 payments | https://x402.org/facilitator |
| MAINNET_RPC_URL | No | RPC URL for mainnet | https://rpc.pharos.xyz |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_wallet_balancesC | Get PHRS (native), USDC, USDT, WETH, and WPHRS balances for any wallet on Pharos Atlantic Testnet |
| get_token_priceA | Get the live USD price of PHRS, USDC, USDT, or WETH from CoinGecko |
| send_usdcC | Send USDC to an address on Pharos Atlantic Testnet, with an optional memo |
| send_tokenC | Send any supported token (USDC, USDT, WETH, WPHRS) to an address on Pharos Atlantic Testnet |
| conditional_paymentA | Send a payment only if a token price condition is met, e.g. send 5 USDC if WETH price > 2000 |
| batch_sendA | Send tokens to multiple recipients in one call and get a per-recipient result summary |
| get_transaction_historyB | Get recent transactions for an address from the Pharos Atlantic explorer |
| estimate_gasA | Estimate the gas cost of a token transfer in PHRS and USD |
| x402_pay_for_resourceA | Fetch an x402-protected URL, automatically paying for it with USDC if the price is within max_price |
| check_wallet_safetyB | Screen a wallet address for malicious activity, blacklists, and sanctions using the GoPlus Security API |
| check_token_safetyA | Analyze a token contract for honeypots, taxes, mint risk, and ownership risks using the GoPlus Security API |
| check_contract_safetyB | Analyze a smart contract for verification status, proxy patterns, and known risk items using the GoPlus Security API |
| safe_transferA | Screen the recipient with GoPlus first, then send the token only if the recipient is not high risk |
| create_payment_requestB | Generate a structured payment request payable to this wallet, with an expiry and a human readable payment URI |
| verify_payment_receivedB | Check recent transactions for a matching incoming payment of an expected amount and token |
| wrap_phrsA | Wrap native PHRS into WPHRS (WETH-style deposit) |
| unwrap_phrsA | Unwrap WPHRS back into native PHRS (WETH-style withdraw) |
| get_wallet_profileA | Build a full wallet intelligence report: balances with USD values, transaction count, wallet age estimate, and GoPlus safety status |
| get_network_statsA | Get live Pharos Atlantic Testnet stats: block number, gas price, and latest block details |
| multi_condition_paymentA | Send a payment only if multiple token price conditions pass, combined with AND or OR logic |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools have clearly distinct purposes, but there is some overlap among sending variants (send_token, safe_transfer, conditional_payment, etc.), which could cause misselection if descriptions are not carefully read.
All tools use snake_case with a verb_noun pattern, which is consistent. A few names like 'x402_pay_for_resource' break the pattern slightly, but overall it's predictable.
20 tools is on the higher end but still reasonable for a comprehensive payment and DeFi server. Each tool serves a specific function, and the count is justified by the scope.
The tool set covers all major workflows: sending (multiple variants), receiving verification, wrapping/unwrapping, safety checks, balances, network stats, and pricing. No obvious gaps for the declared testnet domain.