Skip to main content
Glama

azeth_smart_pay

Discovers the best service for a capability, pays automatically, and falls back to alternatives if the best one fails. Returns data and payment details.

Instructions

Discover the best service for a capability and pay for it automatically.

Use this when: You need a service by CAPABILITY (e.g., "price-feed", "market-data", "translation") and want Azeth to pick the highest-reputation provider, handle payment, and fall back to alternatives if needed.

How it differs from azeth_pay:

  • azeth_smart_pay: "I need price-feed data" → Azeth discovers the best service, pays it, returns the data.

  • azeth_pay: "I need data from https://specific-service.com/api" → You know which service, Azeth pays it.

Flow: Discovers services ranked by reputation → tries the best one → if it fails, tries the next. Set autoFeedback: true to automatically submit a reputation opinion based on service quality after payment. Note: autoFeedback defaults to false in MCP context (ephemeral client). Enable it if the MCP server has a bundler configured.

INTENT (recommended): pass intent (loose token(s)) or params (exact) to get exactly the asset/resource you want. Azeth matches your intent deterministically (no LLM, low latency): for a provider that exposes a CATALOG of many paid endpoints (e.g. price of BTC, ETH, XRP) it navigates to the right priced route; for a provider with a single fixed priced route it pays only when the asset you named appears in that route. SAFETY GUARANTEE: with an intent set, smart_pay NEVER spends on a non-matching asset — on a miss it returns { paid:false, resolved:false, options:[…] } (the catalog menu + valid param values), so you refine and retry in one shot with no money spent on the wrong thing.

Returns: The response data, which service was used, attempts, payment details, and (for catalog navigation) a resolved receipt of the entry + bound params.

Example: { "capability": "price-feed", "intent": "bitcoin" } → pays the BTC price route and returns the data. Example: { "capability": "price-feed", "params": { "coinId": "ethereum" } } or { "capability": "translation", "maxAmount": "0.50", "method": "POST", "body": "{"text": "hello"}" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").
capabilityYesService capability to discover (e.g., "price-feed", "market-data", "translation", "compute").
intentNoWhat you want, as loose token(s) (e.g. "bitcoin", or ["bitcoin","fresh"]). When the chosen provider serves a catalog of paid endpoints, these are matched deterministically against the catalog's param values to pick the concrete route. On a miss, the response returns the catalog "options" so you can retry with an exact value.
paramsNoPrecise catalog params (e.g. { "coinId": "bitcoin" }) — overrides intent. Use when you already know the provider's param names (e.g. from a prior "options" response).
methodNoHTTP method. Defaults to "GET".
bodyNoRequest body for POST/PUT/PATCH requests (JSON string, max 100KB).
maxAmountNoMaximum USDC amount willing to pay per service (e.g., "1.00"). Rejects if service costs more.
minReputationNoMinimum reputation score (0-100) to consider. Services below this are excluded.
autoFeedbackNoAutomatically submit a reputation opinion after payment based on service quality. Defaults to false.
smartAccountNoSmart account to pay from. Use "#1", "#2", etc. (index from azeth_accounts) or a full address. Defaults to your first smart account.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so description fully covers behavior: discovery by reputation, fallback, autoFeedback defaults, safety guarantee on intent miss, return structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections and examples. Slightly lengthy but front-loaded with core purpose and differentiation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

10 parameters and no output schema, but description covers return values, intent resolution, and safety guarantees adequately for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3). Description adds significant value: explains intent vs params, autoFeedback defaulting, chain aliases, maxAmount rejection behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it discovers and pays for the best service by capability. It distinguishes from sibling azeth_pay by contrasting capability-based vs. URL-based selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (by capability) and how it differs from azeth_pay. Provides flow description and intent usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

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/azeth-protocol/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server