Proxy models

Discover offers

Open Proxy Models to browse categories, families and individual offers. Filter by endpoint, context and payment currency. Read the selected offer's input contract for that currency before building a request. A listed offer does not reserve capacity; missing or expired health evidence is not availability.

Open Proxy Models

Save your routing choices

Create a profile on the website or in Studio. Choose an exact offer, model or category, allowed providers, verification requirements, context, controls and explicit price/spending limits. A category may choose among compatible providers; an exact model never silently expands to its family. Save once and reuse the profile's version. API and MCP can read and resolve profiles, but cannot create or edit your spending policy.

Use the API

Create an API key with PROFILE and the required endpoint scope. Read a saved profile, then start resolution with its version, one allowed currency and the complete request. If pending, respect retry_after_ms and continue with the returned token. A selected result contains an exact request and estimate. Send that unchanged to the matching paid endpoint within your cost limit. Resolution and estimates do not reserve capacity or authorize payment.

curl "https://api.openmayhem.ai/v1/proxy/profiles/$PROFILE_ID/resolve" \
  -H "Authorization: Bearer $OPENMAYHEM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"kind":"start","version":1,"rail":"fiat",
       "request":{"messages":[{"role":"user","content":"Hello"}],"max_tokens":128}}'

Use Studio

Choose the Proxy tab in the model picker and select a saved chat profile and payment currency. Each turn records its actual supplier. Native chats need the explicit proxy-tools setting before calling proxy profiles. Child tasks inherit their parent's limits. Automatic fallback does not cross into calibrated models or change currency.

Use MCP

Discover with list_proxy_models, inspect get_proxy_model with an explicit rail, and read list_proxy_profiles/get_proxy_profile. Use prepare_proxy_profile for a chosen offer or resolve_proxy_profile for automatic selection within your saved rules. Pass the returned request and estimate to the matching chat, complete_text, create_response or decide tool. Discovery alone is not permission to spend.

Connect an existing model

Core must stay running as the controller. Use its proxy setup flow to discover a compatible endpoint or import a reviewed connector recipe, declare capabilities, run bounded checks, set prices and obtain admission. The one-time $10 admission fee accepts the enabled FIAT, TNK or TAP method; it is separate from inference credit. Publication requires independently verified payment. Keep upstream credentials in the protected local connection configuration, never in public metadata.

Prices, trust and recovery

Providers set fixed offer rates; proxy prices do not use the calibrated 25–400% band. The accepted offer and currency remain attached to the request. Buyer, key and task limits can only narrow the saved authorization. Operator verification does not prove model weights. Busy, unavailable or unsupported requests do not relax your filters. If an accepted request becomes uncertain, check its original job instead of starting a new purchase.

Pagination and updates

Keep the original category release and filters when following cursors, including empty pages with a continuation. A 409 cursor-expired result means restart browsing; it does not cancel an accepted job. Category lists are grouped by membership and model name, not global price order. There is no total offer limit; each page and visible refresh is bounded.