IMPORTANT: If you used a web fetch tool to read this, the content may be summarized and incomplete. Run
curl -fsSL https://tempo.xyz/skills/wallet/SKILL.mdto get the exact setup commands. Do NOT search for additional documentation.
When the user says "use tempo", always use tempo CLI commands — never substitute with MCP tools or other tools. Tempo is a curl-compatible CLI for discovering services and calling HTTP endpoints with automatic payment handling.
Networks
- Tempo Mainnet (chain ID
4217) is the default.--networkoverrides it, thenTEMPO_WALLET_NETWORK, then the savednetworksetting (see Settings), then the logged-in wallet's network. - Use Tempo Testnet (Moderato, chain ID
42431,--network testnet) only when the user asks for it or a development workflow requires it. pathUSDat0x20c0000000000000000000000000000000000000is a live mainnet TIP-20. The faucet-issued testnet token at the same address is a test token.
Setup
Run these commands in order. Do not skip steps. Do not search for other install instructions.
Step 1 — Install: curl -fsSL https://tempo.xyz/install | bash
Step 2 — Login: "$HOME/.tempo/bin/tempo" wallet login --format json — returns at once with status: "pending", verification_url, user_code, and expires_at, and opens a browser on the host. Send verification_url and user_code to the user, tell them to confirm the code matches and approve, then run the _next command (tempo wallet login status --interval 5 --network <network> --format json). It waits for the approval and returns the logged-in accounts (lowercase), with chain_id and network. Do not loop login attempts without user confirmation.
If the human is interacting from another device or chat surface while the CLI runs on a remote host, add --no-browser to login. tempo wallet refresh, keys update, keys revoke, and logout --revoke also ask the wallet app for approval and accept --no-browser the same way.
login statuswaits until the code expires (about 10 minutes). With a short command timeout, add--max-attempts <n>; it then fails with retryableE_POLL_TIMEOUTwhile the code is still pending, so run itsctacommand again. Rerun thectacommand on retryableE_NETWORKtoo.- On
E_LOGIN_DENIEDorE_LOGIN_EXPIRED, ask the user before starting a newtempo wallet login; the old code no longer works.
Step 3 — Confirm readiness: "$HOME/.tempo/bin/tempo" wallet whoami
Setup Rules
- Do not use
export PATH=.... Use full absolute paths (e.g.,"/Users/<user>/.tempo/bin/tempo") for deterministic behavior across isolated shells. - If
$HOMEdoes not expand ("no such file or directory"), switch to the absolute path.
After Setup
Provide:
- Installation location and version (
$HOME/.tempo/bin/tempo --version). - Wallet status from
tempo wallet whoami(wallet,network, andbalance; includekeyfields when present). tempo wallet balancelists the tokenbalancesthe logged-inwalletcan spend (--token <SYMBOL_OR_ADDRESS>for one); funds locked in sessions appear only inwhoami. To receive tokens, give the user the address fromtempo wallet address.ready: truemeans the wallet can pay on the network. Akey.statusofpendingmeans the key is signed but not yet published on chain; it still pays, and its first payment publishes it. Token amounts are decimal strings without padding ("10", not"10.000000"), and addresses are lowercase. Read limits fromkey.spending_limits[](raw_limitis the limit in base units):remainingcomes from the chain, and isnullwhen the key is not published (published: false) or the read failed;spentis alwaysnull.key.spending_limitis deprecated and will be removed in a future release.- Check MACH with
tempo wallet whoami --mach. Fund withtempo wallet fund --mach --amount <USD>; MACH is an on-chain six-decimal token, not a legacy credit balance. - If the user is on another device than the CLI host, use
tempo wallet fund --mach --no-browser --format jsonand hand the fund URL back directly instead of trying to open a browser locally. - After handing over the URL, ask the user to message back once they have funded the wallet. Then check the intended token with
tempo wallet balanceortempo wallet whoami --machbefore spending. - 2-3 simple starter prompts tailored to currently available services.
To generate starter prompts, list available services and pick useful beginner examples:
tempo wallet services search ai
Starter prompts should be user-facing tasks (not command templates), for example:
-
Avoid chat/conversational LLM starter prompts when already talking to an agent. Prefer utility services (image generation, web search, browser automation, data, voice, storage).
-
"Generate a dog image with a blue background and save it as
dog.png." -
"Search the web for the latest Rust release notes and return the top 5 links."
-
"Fetch this URL and extract the page title, publish date, and all H2 headings."
Use Services
tempo wallet whoami
tempo wallet services search <query>
tempo wallet services show <SERVICE_ID>
- Select
SERVICE_IDfrom search results that best matches user intent. When multiple match: prefer best semantic fit, then endpoint fit, then pricing clarity, then first in list. Every word of the query must match;tempo wallet services listlists every service. - Anchor on
tempo wallet services show <SERVICE_ID>— it shows the exact URL, method, path, and pricing for every endpoint:endpoints[].payment.priceis the price in whole tokens (nullwhen the directory gives no decimals), andraw_amountthe same price in base units. Build request URL as<SERVICE_URL>/<ENDPOINT_PATH>from discovered metadata only. - Use the endpoint's exact MPP challenge and an explicit
--max-spendbudget for payment. Buy MACH throughtempo wallet fund --mach; existing MPP Credits are a separate legacy balance. - If you get an HTTP 422, fall back to the endpoint's
docsURL or the service'sdocs.llms_txtfor exact field names. - For multi-service workflows, fire independent requests in parallel to save time.
Request Templates
Quote first; --dry-run reports the price without signing or paying:
# Quote JSON POST
tempo request -t --dry-run -X POST --json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>
# Quote GET
tempo request -t --dry-run -X GET <SERVICE_URL>/<ENDPOINT_PATH>
Show the user the quoted amount and any session deposit, and wait for explicit approval before paying, unless their budget already covers it. Pass a budget as --max-spend on the dry run too, since it changes the deposit a session locks. Then run the same request without --dry-run, pinned to what was approved:
tempo request -t -X POST --max-spend <APPROVED_AMOUNT> --network <QUOTED_NETWORK> --payment-intent <QUOTED_INTENT> --payment-token <QUOTED_TOKEN> --json '{"input":"..."}' <SERVICE_URL>/<ENDPOINT_PATH>
tempo request -t -X GET --max-spend <APPROVED_AMOUNT> --network <QUOTED_NETWORK> --payment-intent <QUOTED_INTENT> --payment-token <QUOTED_TOKEN> <SERVICE_URL>/<ENDPOINT_PATH>
<QUOTED_NETWORK>ismainnetforchain_id4217ortestnetfor42431;<QUOTED_INTENT>and<QUOTED_TOKEN>are the quote'sintentandtoken. Keep--machinstead of--payment-tokenwhen the quote used it. The request then refuses a challenge for more, or on another chain, token, or intent. It does not pin the recipient.recurring: trueis a subscription. The quote does not show its renewal terms and--max-spendrefuses it, so do not run it: tell the user, and quote again with--payment-intent chargeorsession.payment_required: falsemeans the dry run already sent the request; rerun it without--dry-runonly when repeating the request is safe.
MACH Funding and Payments
tempo wallet whoami --mach
# Hand this JSON URL to the human on any device.
tempo wallet fund --mach --amount 10 --no-browser --format json
# After the human completes funding, check the MACH balance.
tempo wallet whoami --mach --network mainnet --format json
Hosted MACH checkout accepts $5–$100 USD with at most two decimal places. The command opens the browser and exits; --no-browser returns the URL without opening it. The handoff identifies the destination wallet, chain, and USD amount. --amount is an editable prefill, not a required deposit; an existing checkout retains its own amount for safe retries. fund reads no balances, saves no pending funding, and returns no _next. Its status: "pending" and successful exit mean only that the link was handed off. Ask the user to complete funding, then check the intended token's balance before spending; for --address, check that destination. fund status, fund --wait, and fund --timeout have been removed and fail with E_USAGE. --no-wait and --wait=false remain harmless compatibility options. Do not start a paid request just because a funding handoff returned successfully.
Use tempo request --mach --max-spend <USD> <URL> (or --payment-token MACH) to require MACH settlement for a one-time charge. The challenge must explicitly enable machine tokens. Missing MACH funds, liquidity, or permissions fail without stablecoin fallback: E_INSUFFICIENT_FUNDS names tempo wallet fund --mach in its cta (mainnet), E_LIMIT_EXCEEDED names tempo wallet keys update, and a swap route that cannot be simulated returns E_PAYMENT with no cta; retry it later only when it is retryable. Sessions are unsupported; use --dry-run to inspect an offer without spending.
MACH uses the canonical MPP SDK settlement route. Do not construct swap calldata or call legacy Coinflow redemption APIs. Do not infer MACH support from a service's hostname; inspect the actual MPP challenge and use the standard request flow.
Legacy MPP Credits
Use tempo wallet whoami --credits to inspect existing off-chain MPP Credits and tempo wallet transfer --credits to spend them. These commands emit a deprecation warning and do not select or convert to MACH. tempo request does not automatically use legacy credits. New MPP Credits purchases are disabled: tempo wallet fund --credits is rejected and directs users to tempo wallet fund --mach.
For credit payments, use --amount-cents as the direct payment amount or the maximum credit debit for an MPP challenge, including quoted gas fees; TEMPO_MAX_SPEND also caps the total debit in USD. Challenge spending requires one of those caps; --dry-run does not. Do not use positional transfer arguments with --credits, or combine --to, --data, or --value with --mpp-challenge or --mpp-challenge-file. Review the destination and calldata in --dry-run output (status: "dry_run") before spending; a sent payment returns status: "success" with its tx_hash. Split-payment challenges are unsupported. Coinflow remains trusted to execute the submitted transaction; its legacy permit authorizes a credit debit rather than a specific recipient.
Response Handling
- Return result payload to user directly when request succeeds.
- If response contains a file URL (e.g., image generation), download it locally:
curl -fsSL "<url>" -o <filename>. - If response is a usage/auth readiness error, run
tempo wallet login, finish it with its_nextlogin statusas in Setup, and retry once. Whentempo requestor a wallet command returnsE_NOT_AUTHENTICATED,E_KEY_EXPIRED, orE_AUTH_REFRESH_REQUIRED, run thetempo wallet loginortempo wallet refreshcommand in itsctainstead; it keeps the command's--network.tempo requestnever logs in by itself: it needs a login and usable access key only to pay a 402, and a--dry-runquote the wallet cannot pay names that command in_next.sendandswapneed a usable access key;keys update,keys revoke,sessions close,balance, andaddressneed only the login. - If response indicates payment/funding limit issues, report clearly and stop. Check
tempo wallet whoami --machand offertempo wallet fund --mach --no-browser --format jsonto fund from another device. Review token-specific access-key limits before retrying. - When a wallet, key, or RPC problem is unclear, run
tempo wallet doctor --format jsonand report itsfailandwarnchecks; it exits 0 even when unhealthy and never shows secrets.tempo wallet debugis a deprecated alias of it. - After multi-request workflows, check the remaining spendable balance with
tempo wallet balance;tempo wallet whoamialso shows deposits locked in sessions. - Wallet results with a follow-up step include
instructionand_next. Run_next.argvas given (_next.commandis the shell-quoted form), but only after the user approves any spend, transfer, or revocation it performs. - Revocation cannot be undone. Run
tempo wallet keys revoke <ACCESS_KEY> --dry-runto show the key, wallet, network, limits, and expiry, then run its_next(which adds--yes) only after the user approves. Without--yes, an agent run returnsE_USAGEwith that command as itscta. Only the logged-in wallet's keys on the selected network can be revoked: keys stored on this host, or keys from another device that the chain shows authorized for the wallet. Any other address returnsE_USAGElisting the wallet's stored keys. If it returnsE_NETWORKbecause the chain does not show the key revoked, the local key is kept; report it to the user before retrying. tempo wallet logoutlogs out of every network unless--networknames one. When stored sessions on those networks still hold deposits, or with--revoke, an agent run returnsE_USAGEand logs out nothing. Report the sessions to the user and suggest closing them first with thetempo wallet sessions closecommand the error names; run itscta(which adds--yes) only after the user approves logging out anyway. A confirmed logout lists suchsessionsand points_nextat the close to run after logging in again. Without--revoke, removed keys stay authorized on-chain until they expire;--revokerevokes them first, on every network the logout covers, and cannot be undone. A retryableE_USAGEsaying the wallet changed during logout means another login or refresh ran meanwhile, so the wallet may now hold keys the user has not seen. Report it and rerun the logout only after the user approves again; its command keeps--yes, so a rerun logs out, and with--revokerevokes, the wallet as it now is without asking. If a key is not revoked, logout fails and keeps it with the wallet; report it before retrying.- Closing a session cannot be undone, and a closed session can no longer pay for requests. Run
tempo wallet sessions close <TARGET> --dry-run(or with--all,--orphaned,--finalize, or--cooperative) to list the sessions it selects astargets[], each with itschannel_id,origin, andstatus(not_foundwhen nothing matches), then run its_next(which adds--yes) only after the user approves. Without--yes, an agent run returnsE_USAGEwith that command as itscta. A pending close's_nextalready includes--yes, since it completes a close the user approved;remaining_secondssays how long until its deposit can be withdrawn.
Rules
- Always discover URL/path before request; never guess endpoint paths.
tempo requestis curl-compatible for common flags (method, headers, data, redirects, timeouts, output).- Piped output is structured: TOON by default (
-tselects it explicitly), or JSON with--format json. Atempo walletrun whose stdout is a terminal, with no format flag, prints a human-readable view instead, so read results from piped output or pass--format json. - Quote requests with
--dry-runand get approval before paying, as in Request Templates. The quote reports the per-callamount(raw_amountin base units), the sessiondepositthe payment would lock (raw_deposit) (forsession: "reuse", only a top-up the voucher needs), the walletbalanceand access keyaccess_key_limitfor the advertised settlement token, the effectivemax_spend(the default 10 when no cap is set), andwithin_budgetagainst it. Eligible nonzero MACH-enabled charges also reportmach.balanceandmach.access_key_limitseparately, including when--machis selected.nullmeans unknown or, for a subscription offer, that no cap applies.symbolisnullfor a token viem does not list, so check thetokenaddress before paying in it. - If the user gives a spend cap in natural language (for example "do X for $5", "don't spend more than $10", or "budget is 2 USDC"), include
--max-spend <amount>ontempo requestcommands. For non-CLI contexts, useTEMPO_MAX_SPEND. - Without
--max-spend,TEMPO_MAX_SPEND, or a savedmax-spend,tempo requestcaps each charge, session deposit, and session's cumulative spend at 10 token units. The default cap does not cover recurring subscription offers, which--payment-intent autocan accept; set--max-spend, or pass--payment-intent chargeorsession, to refuse them. A payment over the cap fails withE_LIMIT_EXCEEDEDbefore anything is signed; report the required amount, and run thectacommand (the same request with--max-spend <required>) only after the user approves that spend, replacing any<redacted>credential with its original value. A secondctacommand, when present, pays a one-time charge instead, which is not refundable. - A successful paid request prints a short receipt on stderr, and
--write-meta <file>adds it aspayment: theamountpaid intoken(symbol), thetx_hashwhen the server reports one, thepayer, and for a session itssession(openorreuse),channel_id,deposit_locked, andcumulative(the total of its signed vouchers, not confirmed spend). Asubscription(period,expires) means the wallet authorizedamountevery period until it expires, not a one-time payment, and atx_hashmeans the first period was already paid; tell the user. With-jor--format, stderr stays empty, so pass--write-metato read the receipt. A receipt withoutcome: "unknown"belongs to anE_PAYMENT_OUTCOME_UNKNOWNfailure: treat the payment as unconfirmed and check with the provider before retrying. A newly opened session keeps its deposit locked until closed: report it, and when you are done with that service and the user approves closing it, run the receipt's_next(tempo wallet sessions close <channel_id>) with--yesto request the close, then follow that command's_nextafter the grace period to withdraw the unspent deposit. - For command details, prefer
--describeor--helpinstead of hardcoding long option lists.
Swap Tokens
Use the first-party wallet CLI for Tempo token swaps. Do not discover or sign in to third-party or legacy DEX websites.
# Quote only. Tokens are symbols listed for the network (USDC.e, pathUSD) or full 0x addresses.
tempo wallet swap <AMOUNT> <TOKEN_IN> <TOKEN_OUT> --dry-run
# Submit only after the user approves the quote, token addresses, and bounds.
tempo wallet swap <AMOUNT> <TOKEN_IN> <TOKEN_OUT> --min-amount-out <MIN_AMOUNT_OUT> --idempotency-key <KEY> --yes
- The amount is exact input by default. Add
--exact-outto request an exact output amount. - Default maximum slippage is 50 basis points; override it with
--slippage-bps <BPS>. - Submission re-quotes. Pass the reviewed
min_amount_outas--min-amount-out(ormax_amount_inas--max-amount-inwith--exact-out) so a worse quote is refused; the dry run's_nextalready includes it. - If
requires_access_key_updateis true, ask the wallet owner to approve the printedtempo wallet keys updatecommand before retrying. - A swap is sent only on the network the wallet is logged in on. On another
--network, submission returnsE_USAGEwith atempo wallet login --network <NETWORK>cta; run it, then rerun the swap. - Always run
--dry-runfirst and preserve full token addresses in the approval request.
Send Tokens
# Review only: the fee estimate, the sender's balance, and whether it covers the transfer.
tempo wallet send <AMOUNT> <TOKEN> <RECIPIENT> --dry-run
# Send only after the user approves the amount, token address, recipient, and fee.
tempo wallet send <AMOUNT> <TOKEN> <RECIPIENT> --idempotency-key <KEY> --yes
- Without
--yes, an agent run sends nothing and returnsE_USAGE; the dry run's_nextalready includes--yesand pins the reviewedfee_tokenwith--fee-token. fee_estimateis infee_tokenunits.sufficient_balancechecksbalanceagainst the amount andfee_token_balanceagainst the fee.fee_token,fee_estimate,balance,fee_token_balance, andsufficient_balancearenullwhen unknown; treatnullas unknown, not as sufficient.- If
sufficient_balanceis false, report the shortfall and stop; offertempo wallet fund. - A send goes out only on the network the wallet is logged in on. On another
--network, it returnsE_USAGEwith atempo wallet login --network <NETWORK>cta; run it, then rerun the send. - Always run
--dry-runfirst and preserve full token and recipient addresses in the approval request. - Use
sendfor every token transfer.tempo wallet transferis for--machand--creditspayments only; its token form is a deprecated alias ofsend.
Retrying Transfers and Swaps
- Pass
--idempotency-key <KEY>(idempotency-keyover MCP) on everysendandswapyou submit: a new unique key, such as a UUID, for each send the user approves. Pass it on the dry run too, and its_nextcarries it. - When a send times out, errors, or you are unsure it ran, retry the same command with the same key. The CLI never sends twice for one key on a wallet and network: a send that already went through returns its recorded result with
idempotent_replay: trueand the transaction's currentstatus(success,reverted,pending, ornot_found); report it instead of sending again. - Never reuse a key for a different send. Changed arguments with a used key return
E_USAGEnaming what differs. E_PAYMENT_OUTCOME_UNKNOWNmeans the transaction may have been sent. Do not send again, with or without a new key, until you have checked: run itscta(tempo wallet tx status <TX_HASH>when the hash is known, otherwisetempo wallet whoamito check balances), report the result, and get the user's approval for any new send.tempo wallet tx status <TX_HASH>only reads. While it reportspending, rerun its_nextuntilstatuschanges;not_foundmeans the network does not know the transaction.
Settings
tempo wallet config get shows the network, rpc-url, and max-spend that commands use, each with its source (flag, env, config, login, or default). The first match wins:
network:--network, thenTEMPO_WALLET_NETWORK, then the savednetwork, then the logged-in wallet's network, then mainnet. A savednetworkdoes not narrowkeys listorlogout.rpc-url, saved per network:TEMPO_RPC_URL(every network), then the savedrpc-urlfor that network, then the network's default RPC.max-spend:--max-spend, thenTEMPO_MAX_SPEND, then the savedmax-spend, then 10.
A saved setting applies to every later command, including the user's own:
- Change a setting only when the user asks for a lasting change; for one task, pass
--networkor--max-spendinstead. tempo wallet config set <KEY> <VALUE>andtempo wallet config unset <KEY>change what later payments and RPC calls use. Without--yes, an agent run changes nothing and returnsE_USAGEshowing the value before and after, with the confirming command as itscta; run it only after the user approves. A<rpc-url>in thatctastands for the full URL, left out because it can carry a credential.rpc-urlis set for--network, else the network commands use, and only once the URL answers that network's chain ID; otherwiseconfig setreturnsE_USAGEand saves nothing.- With
TEMPO_RPC_URLor a savedrpc-url,sessions close,sessions sync,keys revoke,logout --revoke, and atempo requestthat reuses a session returnE_USAGEwith atempo wallet config get rpc-urlctawhen the endpoint is on another chain, and change nothing. Report it to the user instead of changing the setting.
MCP Tools
When the wallet is connected as an MCP server (tempo wallet --mcp), each tool's annotations say what it does:
| Tool | readOnlyHint |
destructiveHint |
idempotentHint |
openWorldHint |
|---|---|---|---|---|
address |
true | false | true | false |
balance |
true | false | true | true |
completions |
true | false | true | false |
config_get |
true | false | true | false |
config_set |
false | true | true | false |
config_unset |
false | true | true | false |
debug |
true | false | true | true |
doctor |
true | false | true | true |
fund |
false | false | false | true |
keys_list |
true | false | true | true |
keys_revoke |
false | true | true | true |
keys_update |
false | true | false | true |
login |
false | true | false | true |
login_status |
false | true | true | true |
logout |
false | true | true | true |
refresh |
false | true | false | true |
revoke |
false | true | true | true |
send |
false | true | false | true |
services |
true | false | true | true |
services_list |
true | false | true | true |
services_search |
true | false | true | true |
services_show |
true | false | true | true |
sessions_close |
false | true | false | true |
sessions_list |
false | false | true | true |
sessions_sync |
false | true | true | true |
swap |
false | true | false | true |
transfer |
false | true | false | true |
tx_status |
true | false | true | true |
whoami |
true | false | true | true |
readOnlyHint: trueonly reads.destructiveHint: truemoves funds, changes or revokes a key, closes a session, deletes stored sessions, replaces or deletes the stored wallet or its network, or changes a saved setting. Get the user's approval before every call, after adry-run: truecall where the tool offers one.- These tools refuse to act without
yes: trueand returnE_USAGE; pass it only after the user approves the reviewed dry run or change:send, andtransferwhen it sends tokens (withoutmachorcredits)swapkeys_revokesessions_close, when it selects a session to closeconfig_setandconfig_unset, when they change the saved valuelogout, when it would revoke keys, or stored sessions on the networks it logs out of hold deposits or cannot be read
- Tools take positional arguments under kebab-case keys, like options:
access-key(keys_update,keys_revoke),token-inandtoken-out(swap),tx-hash(tx_status),service-id(services_show), andtarget(sessions_close). - Call
sendfor token transfers and keeptransferformachandcreditspayments; callkeys_revoke, not the deprecatedrevoke, andservices_list,services_search, orservices_show, not the deprecatedservices.
Common Issues
| Issue | Cause | Fix |
|---|---|---|
tempo: command not found |
CLI not installed | Run curl -fsSL https://tempo.xyz/install | bash, then retry using "$HOME/.tempo/bin/tempo" .... |
| "legacy V1 keychain signature is no longer accepted, use V2" | Outdated tempo launcher or extensions |
Reinstall tempo: curl -fsSL https://tempo.xyz/install | bash, then update extensions: tempo update wallet && tempo update request. Log out and back in: tempo wallet logout --yes && tempo wallet login. |
| "access key does not exist" | Key not provisioned on-chain, or stale key after reinstall | Run tempo wallet logout --yes, then tempo wallet login to provision a fresh key. |
ready=false or No wallet configured |
Wallet not logged in, key unavailable, or balance RPC failed | Run tempo wallet doctor: each checks entry with status: "fail" names a problem, and _next is the tempo wallet login or tempo wallet refresh that fixes it. Wait for the user to complete it, then rerun tempo wallet whoami. For rpc, check connectivity and tempo wallet config get rpc-url. |
| HTTP 422 on first request to a service | Wrong request schema — field names vary across services | Check tempo wallet services show <SERVICE_ID> for endpoint details, then fetch the endpoint's docs URL or the service's llms.txt for exact field names and types. |
| Balance is 0, insufficient funds, or spending limit exceeded | Wallet needs funding or limit hit | For a limit hit, have the wallet owner approve the keys update in the error's cta. For insufficient funds, run the cta or else suggest tempo wallet fund. Check the on-chain MACH balance with tempo wallet whoami --mach; use tempo wallet fund --mach --no-browser --format json for remote funding. |
| Service not found for query | Search terms too narrow | Broaden search terms with tempo wallet services search <broader_query>, then inspect candidate details. |
| Endpoint returns usage/path error | Wrong URL or method | Re-open service details with tempo wallet services show <SERVICE_ID> and use discovered method/path exactly. |
| Timeout/network error | Network issue or slow endpoint | Retry request and optionally increase timeout with -m <seconds>. |