Modexia
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MODEXIA_API_KEY | Yes | Your Modexia API key from modexia.software | |
| MODEXIA_BASE_URL | No | The base URL for the Modexia API. Defaults to sandbox (testnet). For production use https://api.modexia.software |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Retrieve the current USDC wallet balance for the Agent's Smart Contract Wallet. |
| transferA | Send a standard Modexia payment (USDC) to a recipient. Recommended to always provide an idempotency_key to prevent double charges. Optionally provide a memo to explain the reason for the payment (visible in audit trail). |
| cross_chain_transferA | Send a cross-chain CCTP payment natively to another blockchain using Squid Router.
Requires |
| get_historyC | Fetch the recent transaction history for the authenticated agent. |
| open_channelA | Open a high-frequency micro-payment vault channel with on-chain deposit.
Blocks funds for the specific provider, allowing instant, gas-free payments via |
| consume_channelB | Execute an instant, gas-free micro-payment inside an already open channel. Call this as many times as needed while the channel is open. |
| settle_channelA | Settle an open micro-payment channel, paying the provider, and refunding the remainder back to you. |
| get_channelA | Get the current status, deposit amount, and remaining balance of a specific payment channel. |
| list_channelsB | List all payment channels associated with the authenticated agent's wallet. |
| smart_fetchA | Fetch an external resource via HTTP. If the resource responds with a 402 Payment Required and a WWW-Authenticate header, this tool will automatically negotiate and pay the invoice via Modexia AgentPay, then retry the request with the cryptographic proof of payment. |
| submit_intentB | Submit an intent-based payment (v2 API). Creates a signed intent token, submits it through the validation pipeline, and returns a rich result with compliance metadata (policy limits, daily spend, balance). Always provide a memo describing why you are making this payment. |
| get_intentA | Get the status and details of a previously submitted payment intent. |
| list_intentsB | List the most recent payment intents with their status and details. |
| nanopayA | Fetch an x402-protected resource and automatically pay using Circle Gateway nanopayments. Gas-free, instant, supports payments as low as $0.000001 USDC. Use this for sub-cent API calls and premium data purchases. |
| nanopay_balanceA | Get the agent's Circle Gateway nanopayment balance (separate from main wallet balance). |
| nanopay_depositA | Deposit USDC from the agent's main wallet into the nanopayment Gateway. This is an on-chain transaction. After depositing, nanopayments are gas-free. |
| nanopay_withdrawB | Withdraw USDC from the nanopayment Gateway back to the agent's main wallet. |
| nanopay_activateA | Enable Circle Gateway nanopayments for this agent. Must be called once before using nanopay, nanopay_deposit, or nanopay_balance. Idempotent — calling again returns the existing activation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_payment_instruction | Provides internal guidelines to an agent on how to correctly structure a standard payment with Modexia. |
| setup_microtransactions_instruction | Provides internal guidelines to an agent on how to securely open and use a micro-payment channel. |
| create_intent_payment_instruction | Provides guidelines to an agent on how to use the intent-based payment system (v2). |
| nanopay_usage_instruction | Provides guidelines on how to use Circle Gateway nanopayments. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_modexia_context | Retrieve the comprehensive Modexia developer guide, containing rules on how AI agents should execute payments, open channels, and handle 402 Paywalls. Always read this before performing complex financial operations on Modexia. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Modexia/modexia-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server