Dagon Inference
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DAGON_API_KEY | No | Account key (gk_...) for balance, purchases and chat. Required when DAGON_WALLET_SECRET_KEY is set; purchases cannot override it. | |
| DAGON_BASE_URL | No | Gateway URL. Must use https://; http:// is accepted only for localhost, 127.x, or [::1]. | https://inference.dagon.so |
| DAGON_MAX_SOL_FEES | No | Worst-case SOL (fees plus treasury account rent) unsponsored purchases may cost the payer per UTC day. | 0.05 |
| DAGON_SPEND_LEDGER | No | File holding the daily spend totals. Defaults to %APPDATA%\dagon-mcp\spend-ledger.json on Windows, or $XDG_CONFIG_HOME/dagon-mcp/spend-ledger.json (or ~/.config/dagon-mcp/spend-ledger.json) elsewhere. | |
| DAGON_SOLANA_RPC_URL | No | RPC URL for submitting signed purchases that are not fee sponsored. | https://api.mainnet-beta.solana.com |
| DAGON_TREASURY_WALLET | No | Trusted Solana treasury owner whose USDC associated token account receives purchases. Required for any purchase and when DAGON_WALLET_SECRET_KEY is set. | |
| DAGON_MAX_PURCHASE_USD | No | Largest single dagon_buy_credits amount in USD (whole cents). Set to 0 to disable purchases. | 50 |
| DAGON_MIN_PURCHASE_USD | No | Smallest single dagon_buy_credits amount in USD (whole cents). | 1 |
| DAGON_WALLET_SECRET_KEY | No | Optional Solana secret key: 64-byte base58 or JSON byte array; a 32-byte seed is accepted only in JSON byte-array form. A 32-byte base58 value is a Solana address and is refused. Enables validated self-signed purchases. | |
| DAGON_MAX_PURCHASE_USD_PER_DAY | No | Total USD of purchases per UTC day, persisted across restarts in the spend ledger. | 200 |
| DAGON_MAX_PURCHASE_USD_PER_SESSION | No | Total USD of purchases one MCP server process may prepare. | 200 |
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 |
|---|---|
| dagon_modelsA | List the models available on Dagon Inference, with their pricing (GET /v1/models). No API key needed. |
| dagon_balanceA | Show the credit balance of a Dagon account key in USD: total credits, total usage, available (GET /v1/credits). |
| dagon_create_keyA | Create a new Dagon account key (POST /v1/keys). The secret is shown only once: store it securely (e.g. as DAGON_API_KEY) and never paste it into shared chats or files under version control. |
| dagon_buy_creditsA | Buy credits for the configured Dagon account, paid in USDC on Solana. The server checks that the gateway's transaction is exactly the USDC payment to the configured treasury (DAGON_TREASURY_WALLET). If the MCP server has a wallet (DAGON_WALLET_SECRET_KEY), it then signs and confirms it (submitting it itself unless the purchase is fee sponsored, in which case the payment service adds the fee payer's signature and submits it). Otherwise it returns the verified unsigned transaction for payer_wallet to sign; then call dagon_confirm_purchase with signed_transaction (fee sponsored: do not submit it yourself) or with the signature of the transaction you submitted (not fee sponsored). |
| dagon_confirm_purchaseA | Report a dagon_buy_credits payment you signed yourself so the configured account is credited (POST /v1/credits/purchase/confirm). Fee sponsored: pass signed_transaction, the base64 wallet-signed transaction, without submitting it (the payment service adds the fee payer's signature and submits it; resending the same one is safe). Not fee sponsored: submit it yourself and pass its signature. |
| dagon_chatB | Send a chat completion to a Dagon model (POST /v1/chat/completions, non-streaming) and return the reply. Spends credits. |
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 6 tools
Each tool targets a distinct resource or step: model listing, balance, key creation, credit purchase, purchase confirmation, and chat. The only potential confusion is between dagon_buy_credits and dagon_confirm_purchase, but their descriptions make the two-phase payment flow (initiate vs. report signed transaction) explicit.
All tools share a dagon_ prefix and snake_case, with compound verb_noun names like dagon_create_key and dagon_confirm_purchase. Minor deviation: dagon_models and dagon_balance are bare nouns without a verb, breaking the otherwise consistent verb_noun pattern.
Six tools is well-scoped for an inference gateway: discover models, check balance, mint a key, buy credits, confirm payment, and chat. Each tool earns its place with no redundant operations.
The core lifecycle (discover → fund → authenticate → chat) is fully covered, including the tricky manual-signing purchase flow. Gaps exist around key management (no list/revoke/delete key) and chat is non-streaming only, but agents can work around these.