Skip to content
docs

Build & sell tools

The tools marketplace is where you submit a tool and set a fee. Submit your MCP server, set your fee per call, and once it passes review it is listed on Connections: users pay your fee plus a 10% platform fee, and you keep 100% of your fee, in USDC.

The marketplace is the Connections catalog, and it is where you submit a tool and set a fee. Any MCP server that speaks Streamable HTTP can be submitted. Users install a server once and call its tools from any MCP client signed in to their account (see MCP server); every call is charged from their balance, and you earn your fee on every paid call. Tools marked "by Xava Inference" are our own; the rest are community tools, made and run by their builders.

Submit a tool and set your fee

  1. Submit your tool: add your MCP server in My connections (Add custom MCP server). It starts private: only you see it, there is no review, and its tools are live in your own MCP client as soon as they are indexed. Up to 20 servers per account.
  2. Set your fee per call for each tool, from free up to $100.00. You see what users pay and what you earn as you type (try the calculator).
  3. Submit for review. We check what each tool says it does and its fee. Until it is approved the server stays private and keeps working for you.
  4. Listed on Connections; earn on every paid call. Once approved, anyone can install your tools, and every successful paid call earns you your fee (see payouts).

How a submission is made today. A submission goes through a community app listing in My apps: a name, a link, a card image and a description, all required. The card is what people see on Community. Link your server to the listing (pick it in the listing's "MCP server" field, or choose the listing in the server's "Community app" select in My connections; "Create new app…" works too), set your fees with Edit price list (your price list is your fee for each tool), then Save and submit for review.

Your MCP server

  • Endpoint: https on a public host name. IP addresses and private or local host names are refused.
  • Authentication: none, a secret header (stored encrypted and never shown again), or OAuth, detected automatically when your server asks for it. With OAuth, each user signs in to your server when they install it, and the server is installed only once that sign-in succeeds.
  • Change endpoint: keeping the same host and path (for example adding ?mode=tools for a server that offers a tools mode) keeps the stored sign-in or secret; a different host or path drops them. Either way the server is indexed again. Re-index any time after you change your tools.
  • Large tool lists: up to 1,000 tools per server and 16 MB per list answer; a tool whose input schema is over 64 KB is left out. A server with one gateway tool (an exec-style tool that runs tools and call <name>) stays one tool, and we index up to 2,000 of its commands so users can see them.
  • Resources and prompts: indexed when your server advertises them (up to 1,000 resources, 200 resource templates and 500 prompts) and shown to users who installed it. Reading them is free.

Review

  • The listing card is reviewed before it appears on Community. An edit to a live listing becomes a draft; the live version stays up until the edit is approved.
  • Your fees are reviewed on their own: draft, submitted, live. A change to live fees becomes a draft, and the live tools and fees keep serving until the change is approved.
  • A server's tools are listed and callable only while its listing is approved. Unpublish hides the listing from Community and its tools from Connections; nothing is deleted, and Publish again on an unchanged listing needs no new review.
  • Choosing another server or None for a listing takes its tools off Connections. The server stays yours, private.
  • Limits: up to 20 listings (community apps) per account, a name of up to 60 characters, a description of up to 255, and a card image of up to 2 MB (JPEG, PNG, WebP or GIF), cropped to 16:9.
  • Review checks what a tool says it does and its price, not that it is safe for every use.

Your fee

  • You set a fee per call for each tool, in USD with up to 6 decimals, from 0 (free, the default) to $100.00 per call.
  • A tool with a fee costs users your fee + the 10% platform fee. You keep 100% of your fee: a $1.00 fee costs users $1.10 and earns you $1.00.
  • A free tool costs users a platform minimum per call: $0.0003, $0.0002 for Pro holders and $0.0001 for Elite. It pays for serving the call; you earn nothing on it. Your private servers work the same way: every tool is free, so each of your calls costs you the minimum.
  • Where the platform fee goes: the caller's cash back comes out of the 10% platform fee (or the minimum) first, at their Reward Status rate (0.5%, 2% or 5% of what they pay, capped at the fee); the rest joins the hourly margin split (10% protocol fee, and 90% buys $INFX: 54% of the margin is distributed to $INFX holders, 27% is burned and 9% is permanently locked by the team). Neither ever comes out of your fee.
  • Our own tools are priced by us, and their whole price is platform margin.
price calculator
  • Your toolType a price per call to see what users pay and what you earn.
    Users pay (+10%)$1.10 per call
    You earn$1.00

Free tools cost users $0.0003 per call (Pro $0.0002, Elite $0.0001); you earn nothing on them. A priced tool costs users your price + 10%; you earn your price.

How tool calls are billed

  • Each call reserves the user's price from their balance, runs the tool, and is charged only if the tool succeeds. If your server cannot be reached, the tool returns an error, or the user still has to sign in to your server, the reservation is released and nothing is charged. A call that succeeds is charged even if its result is too large to pass on.
  • The fee is read from your live fees at call time, and a free tool's minimum follows the caller's Reward Status at that moment.
  • Reading resources and getting prompts is free.
  • Tool calls use the same balance, credits and limits as models: a signed-in app's monthly cap, the account's monthly usage limit and an API key's own spend limit and expiry apply to them too. A call refused by any of these never reaches your server and earns nothing.

Payouts

Builder payouts are coming soon. Your earnings accrue now: every paid call records your fee in the usage ledger, and accrued earnings are paid in USDC to your linked Solana wallet once payouts launch.

  • You earn your fee on every charged call of your approved community tools. Free tools and private servers earn nothing.
  • Earnings are totalled per reward period (24 hours of usage) and paid in USDC (6 decimals, rounded down) to the Solana wallet linked to your account. Link one in Settings. With no wallet linked, the payout is held until you link one.
  • Each payout is recorded with its Solana transaction. There is no minimum amount.
  • If you merge accounts, unpaid earnings go to the account you keep.

Use the tools in your own app

Your app can require your published tools (or anyone's) and call them with each user's credits after they sign in: see Sign in with Xava. You earn your own tools' fees, not from what users spend on models through your app.