
Inferrail
io.github.domondi1Published by GitHub account domondi1v0.4.18Updated Nov 3, 2026
Local, payload-free AI cost visibility for agents. Query spend by model, route, or tagged work.
Overview
Inferrail's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Inferrail in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Inferrail
Spending limits, receipts and paid execution for AI agents.
Give each AI job a dollar budget that's enforced before the provider is called,
and a cost receipt that never stores what the model said.
[CI] [PyPI version] [License: Apache-2.0]
Quickstart · For agents · How it works · Docs · tryinferrail.com
A real run of the gateway and dashboard with a local stand-in model: one job with a $0.04 limit, four calls answered, two refused with HTTP 402 before reaching the model. How it was recorded
What works today
Developer preview: interfaces may change before 1.0.
Also experimental: AP invoice-exception recovery, a hosted trial gateway, and Work Economics / Economic Authority (example; Base Sepolia testnet only).
Quickstart
Requires Python 3.11+.
Try it offline. No API key, no network calls, no provider charges:
The demo sends scripted requests through the real engine to a fake provider with made-up
prices labelled DEMO, and prints what they cost by customer.
Give one run a budget, inside your Python app. No config file, no second process:
Every call with the same work id shares that budget, including parallel calls; one that would
push the run past it gets HTTP 402 before it reaches OpenAI. inferrail work contract-review-42
shows what the run cost.
More: run it as a shared gateway with the local dashboard, framework snippets (LangChain, LangGraph, OpenAI Agents SDK, CrewAI, Haystack, LlamaIndex, Microsoft Agent Framework), and other clients, including the Anthropic SDK.
For agents
Start at tryinferrail.com/llms.txt: what's live, with links to each service's guide and the OpenAPI contract.
Web Read sells one public web page as clean markdown, with its word count, a SHA-256 of the
content and a receipt. $0.002 per delivered page, paid over x402 (USDC
on Base) or MPP (Tempo); no account or API key. The payment is checked first
and settled only after the page is delivered, so refusals (robots.txt, non-public addresses,
non-text, over 2 MB, target-site errors) are never charged. Retrying the same url and
request_id from the same wallet within 10 minutes returns the page already paid for.
Guides: Web Read · Hosted · service source.
MCP. Ask your agent what a job cost, from your local receipts:
Two read-only tools, get_spend (known cost and tokens by provider, model, route or any tag
such as work_id) and get_health. They don't run inference, write files or pay for anything.
Other clients: docs/integrations.md.
How it works
[Data flow. On your machine, your application sends requests to the Inferrail gateway, which reads the provider API key from its environment, forwards request content and the key to OpenAI or Anthropic, and returns the response. Separately, the gateway writes a metadata receipt (tokens, cost, status, timing, attributes, no message bodies) to a local JSONL or SQLite store that reports, the local dashboard, and MCP tools read. A usage beacon collector receives lifecycle events only if an endpoint is configured.]The gateway routes each request by model to a configured provider, checks any budget in
scope, forwards the call, and writes one receipt per request, including requests a budget
refused. A cost is recorded only when the provider reports usage and a price is on file;
otherwise it's unknown, never a guessed $0.
Attribution tags are stored as sent, so keep secrets and message content out of them.
inferrail verify-payload-free prints the live receipt schema, and canary tests check that
message bodies never reach receipts; neither is a security audit. The optional usage beacon
sends nothing unless an endpoint is configured (details).
Architecture: docs/ARCHITECTURE.md.
Current support
- Endpoints:
POST /v1/chat/completions(OpenAI-compatible) andPOST /v1/messages(Anthropic-compatible), with streaming and tool calls, plusGET /v1/models. - Providers: OpenAI, Anthropic, and endpoints compatible with either. Built-in prices cover OpenAI and Anthropic models; others need a price in your config, or their cost stays unknown.
- Not supported: the OpenAI Responses API, embeddings, image generation, audio and Realtime, batch, and native Gemini or Bedrock APIs. Fields the gateway can't account for are rejected with a clear error, never silently dropped.
- Scope: only calls through a running gateway are counted.
Exact contract and non-goals: docs/PRODUCT.md. Running agent jobs that spend real money? Open a production setup request.
Documentation
- Give one AI agent run a dollar budget
- Integrations: SDKs, frameworks, attribution, MCP, voice
- Self-hosting: install, configuration, storage, budgets, dashboard
- Product scope and architecture
- Machine-readable: llms.txt, openapi.json (the gateway), config.schema.json
Contributing, security, license
Questions and bugs: GitHub issues.
Security or privacy vulnerabilities: report privately, as described in
SECURITY.md. Contributing: CONTRIBUTING.md
(pytest needs no API key or network). License: Apache-2.0.
Source: README.md at commit 7e3659f
Tools
0Version history
13- v0.4.18LatestNov 3, 2026
- v0.4.17Oct 31, 2026
- v0.4.16Oct 7, 2026
- v0.4.15Oct 6, 2026
- v0.4.14Oct 5, 2026
- v0.4.13Oct 4, 2026
- v0.4.12Oct 3, 2026
- v0.4.11Oct 1, 2026
- v0.4.9Oct 1, 2026
- v0.4.8Sep 30, 2026
- v0.4.6Sep 29, 2026
- v0.4.5Sep 26, 2026
- v0.1.1Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts