Skip to content
inferiq

Roadmap

Gateway, fix agents and deposits shipped.

Inferiq is built in phases. Each one ends when it can be tried for real and its exit criteria are met, not on a date. The gateway came first because the fix agents call models through it: routing, metering and receipts are built once and shared.

  1. Phase 1

    Phase 1 — Core gateway

    Done

    One key for your coding tools, a receipt per request.

    • OpenAI-compatible chat endpoint with streaming and tool calls
    • Qwen3.8-27B, hosted by Inferiq, behind one key
    • Aliases inferiq/fast, inferiq/balanced and inferiq/best: one model, three reasoning levels, retried once on failure
    • Free Inferiq API keys, each limited to the models you pick, stored as hashes and shown once
    • Balance checks, daily key limits and a receipt for every request

    Exit criteria

    A coding tool runs a full session through Inferiq, receipts match usage, and no secrets reach the logs.

  2. Phase 2

    Phase 2 — First fix agents

    Done

    Quick Fix and Build Doctor are live and priced before they run; on 60 real errors they returned a correct patch 30/30 and 27/30 times.

    • Quick Fix: one error in, cause and patch out
    • Build Doctor: install, build and deploy failures
    • Three model tiers: Economy, Balanced, Strongest
    • Quote with a hard maximum before every run
    • Console pages for fixes, receipts and tool setup
    • Anthropic-format endpoint for Claude Code

    Exit criteria

    On a set of real errors, both agents return a correct patch most of the time, measured against a baseline.

  3. Phase 3

    Phase 3 — Wallet balance

    Done

    Deposit ETH or a stablecoin once, pay per call.

    • Deposits on Robinhood Chain (ETH, USDG) and Base (ETH, USDC) mainnet
    • ETH converted to US dollars when the deposit is credited
    • Ledger with holds, captures and refunds
    • Wallet page with deposit history
    • Low-balance alerts

    Exit criteria

    No negative balances under concurrent load, no double-credited deposit, and the ledger reconciles with the chain.

  4. 4

    Phase 4 — Fix from your editor

    In progress

    Call a fix agent without leaving Claude Code or Cursor.

    • Remote MCP server with fix, quote and balance tools (live at api.inferiq.run/v1/mcp)
    • Tested in Claude Code and Cursor

    Exit criteria

    A developer can ask for a fix from inside the editor and approve the quote there.

  5. 5

    Phase 5 — More agents and a CLI

    Planned

    More specialists, a CLI.

    • Type Fixer, Dependency Doctor and Test Fixer
    • CLI: npx inferiq fix

    Exit criteria

    Each new agent clears the same patch-quality bar.