mcpbeat Sign in

Foundry: prepaid AI compute in USDF MCP Server

answering

Foundry: prepaid AI compute in USDF is answering right now. Last checked 11 min ago. It exposes 10 tools.

Prepaid AI compute in USDF: models, quotes and chat with a receipt; pay per call (x402) or by key

Uptime history 10 days of history
10 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
252 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 October 2026. No other catalogue keeps this.

20 Oct 2 tool descriptions were rewritten balance, chat
18 Oct 7 tool descriptions were rewritten agents_market_call, balance, chat and 4 more
18 Oct a tool changed the parameters it asks for x402_pay

Nothing serious here today

Today is the operative word: we check Foundry: prepaid AI compute in USDF every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add gateway --transport http https://api.usdf.fi/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.usdf.fi/mcp
~/.codex/config.toml
[mcp_servers.gateway]
url = "https://api.usdf.fi/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "gateway": {
      "url": "https://api.usdf.fi/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "gateway": {
      "type": "http",
      "url": "https://api.usdf.fi/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agents
agents_market_call
Calls a listing of the agents market by its id (svc_..., from agents_market_search), paid from this key's USDF balance (never free credit) within the key's and its agent's limits and at most max_price: what one call costs and nothing on top; a call its seller does not answer 2xx costs nothing, or no more than what its seller kept of it. Every listing is called the same way, and answers 503 market_calls_unarmed while calls to the market are not switched on. Needs an API key. Returns the seller's answer and the receipt. The input goes to the seller, whose own policy governs what it keeps.
agents_market_search
Agents, APIs and tools priced per call, in one market, every listing in the same shape: its id (svc_...), name, description, tags, site and logo, how it is called (GET or POST), what one call costs in USDF from this key's balance, input and output examples, and the data policy. Ordered by popularity (default), price or newest. No key needed to search; agents_market_call calls one.
quote
quote
The hold the chat tool places before running a request, in USDF and USD (output capped at 4096 tokens). It is an estimate, not a ceiling: a completed request is billed the provider's reported usage, normally less. Pass prompt or messages. No key needed; a request for attested hardware (a :private model id or provider.private), and any request from a Private-tier key, is quoted on its attested routes, at the model's price.
quote_tool
What a call to a tool would hold for this input before it runs (its most it can cost), in USDF and USD, with the tool's price. It checks the input as the call would, and runs and holds nothing. No key needed.
balance
balance
With an API key: what the key can spend now, the account's balance and the amount held for requests running, and what is left of the key's budget, in USDF. With address instead, and no key: that wallet's USDF and USDG on the chain now, and how much USDF it lets the signature-transfer contract spend, which x402 payments come from.
chat
chat
Runs a chat completion and returns the text with its receipt (tokens, price, cost, balance, settlement). With an API key it spends from that key's balance, holding the most the request can cost first. Not streamed. Output is capped at 4096 tokens. A call without a progress token answers within 55 s of arriving. With a progress token, progress is sent every 15 s and the call may run 10 minutes, so the client must reset its timeout on progress (resetTimeoutOnProgress: true in the TypeScript SDK) or wait that long. At its deadline, or when the client's connection closes, a call is cut: the text produced so far is returned with finish_reason "length" and billed on the provider's usage report where the provider gives one, otherwise on an estimate never above max_tokens; for a model whose reasoning is not streamed, at the held output budget. Cancellation messages are not supported: a call the client stops waiting for without disconnecting runs to completion or its deadline and is billed. With no key, the call is paid with x402 in USDF (signature transfer) or USDG (signed transfer), as POST /x402/v1/chat/completions: without a payment it returns isError with the payment requirements (x402Version, resource, accepts) as structuredContent; sign one accept and call again with the payment in _meta["x402/payment"], the payment argument or the PAYMENT-SIGNATURE header. The quote is the call's maximum cost at the published price (prompt at one token per byte, output at max_tokens, capped as above, no minimum), paid up front; the call is charged what it uses at that price and the rest is refunded in the asset paid, the gateway paying the gas. A paid call runs to its end or its deadline whether or not the client waits and returns the receipt and _meta["x402/payment-response"]; at the deadline the text so far is returned with finish_reason "length" and a note, charged what it used and the rest refunded. A call no provider accepted before its deadline, or whose provider failed or ended with nothing, is refunded in full in the asset paid; so is one cut by the deadline after the provider accepted it, with nothing produced. A call with less than 20 s left before its deadline is refused before the payment is settled (deadline_too_close), nothing charged. MPP clients pay the same quote: the payment-required result also carries _meta["org.paymentauth/payment-required"] with evm charge challenges (USDG by signed transfer authorization, USDF by signature transfer); call again with the credential in _meta["org.paymentauth/credential"], and the paid result carries _meta["org.paymentauth/receipt"].
models
list_models
Models the gateway serves with their prices (USD per 1M tokens, the same figure in USDF), context window, output limits and whether a route is available right now. No key needed.
receipt
receipt
With the API key that made the request: its receipt, with the usage, the price sheet version, the cost and, once settled, the settlement, its transaction and the rows behind the onchain digest. With no key: the public receipt of any request id, x402 ones included, with its line in the usage log, the payment, the settlement and where its proof is (GET /x402/v1/receipts/{id}).
tools
list_tools
Tools you can call through POST /v1/tools/{id}, paid from the same balance and key as chat, each with its price in USDF (what it costs plus 5% at most) and the input it takes, ordered by title. Every tool listed can be called now. q keeps the tools whose id, title or description has those words; a page holds up to 200, and page.next names the next one. No key needed.
x402
x402_pay
Calls a URL that asks for an x402 payment and pays it for you: the gateway pays the seller in USDC from its own float and charges this key in USDF cost plus 5% at most, no minimum (the seller's amount and a fee of at most 5% of it; never free credit), within the key's and its agent's limits. Needs an API key. Returns the seller's answer with the payment and its receipt; a payment is charged only once the chain shows it, and one that never settles costs nothing. quote: true answers what it would cost and pays nothing. Third-party tools to call this way are listed under marketplace in list_tools (GET /v1/tools?source=marketplace).

Endpoints

URLTransportStateLatencyChecked
https://api.usdf.fi/mcp streamable-http answering 221 ms 11 min ago

Alternatives to Foundry: prepaid AI compute in USDF

same job, measured the same way
corpusAI Cloud Pricing
by jtraversa

Cloud, GPU and LLM token prices with index fixings. Pay per call over x402 or with a prepaid key.

34 installs/wk 35 tools answering
Mapleai MCP
by veenrek

Pay-per-request GPT chat, embeddings, agents and prepaid keys with local x402 USDC signing

42 installs/wk local only
Quartermaster
by surewhynot-quartermaster

x402 toolkit for AI agents: paid web, AI, and Base chain tools per call in USDC. Free tools too.

49 tools answering
Distill
by spencermcw-data

Pre-computed answers with sources and confidence, paid per call over x402 (USDC on Base).

19 tools answering
trustai.center pay
by trustai-pay

Pay-per-use LLM inference for agents: pay in USDC/USDT or per call via x402. 247 chat models.

10 tools answering
X402 Payagent MCP
by stevemilton

Pay x402 APIs in USDC on Base, Solana, and BNB Chain with spend mandates, receipts, idempotency.

154 installs/wk local only
Payagent MCP
by stevemilton

Pay x402 APIs in USDC on Base, Solana, and BNB Chain with spend mandates, receipts, idempotency.

local only
Agentreader MCP
by ajanani1

11 pay-per-call web tools for AI agents, auto-paid in USDC on Base via x402. No API keys.

20 installs/wk local only

Foundry: prepaid AI compute in USDF — questions

Answers built from our own checks of this server.

What can Foundry: prepaid AI compute in USDF do?
It exposes 10 tools, read directly from the server on our last check. Among them: agents_market_call, agents_market_search, balance, chat, list_models, list_tools and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Foundry: prepaid AI compute in USDF mostly used for?
Its tools cluster around agents and quote. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Foundry: prepaid AI compute in USDF working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 252 ms. The bar chart above shows every period we have measured.
How do I connect Foundry: prepaid AI compute in USDF?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Foundry: prepaid AI compute in USDF need an API key?
No. Foundry: prepaid AI compute in USDF completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Foundry: prepaid AI compute in USDF?
It answers our handshake in 252 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.