Preparing for launchPaid API access is not open yet.Ask about availability

For the builders

A familiar starting point.
Room for more models.

An integration outline for the planned Modtrix text API. Learn the request shape and how usage will be billed before access opens.

Integration preview. Create and manage credentials in the Console. The examples are templates for the planned model API.

  1. Create an API key

    Register or sign in to the Console and create a key. Save it when it appears. Future model access will require an enabled account and a supported model.

  2. Keep your key on the server

    Store your API key and base URL in environment variables. Never include a secret key in browser code, public repositories, or shared screenshots.

  3. Choose a model and send text

    The planned interface follows the OpenAI-compatible chat completions format. Send a model ID and a list of text messages. Final compatibility details will be documented at launch.

  4. Track token usage

    Input and output are priced separately. Conversation history counts as input. Any model-specific reasoning, cache, or optional charges will be documented before they are enabled.

cURL · TEMPLATE
curl "$MODTRIX_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $MODTRIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "MODEL_ID",
    "messages": [
      {"role": "user", "content": "Hello, Modtrix."}
    ]
  }'
Example only · Replace MODEL_ID after access is enabled.

The cURL example uses Bash. MODTRIX_BASE_URL must include the version path supplied at launch.

We’re starting with text.
Text input. Text output. No media generation.

The billing model

A request.
Two clear components.

Each model has its own input and output rate. Billable reasoning, where applicable, is included in output usage according to the model’s accounting.

INPUT COST

Input tokens × input rate ÷ 1M

OUTPUT COST

Output tokens × output rate ÷ 1M

For standard, uncached text requests. Check model-specific pricing conditions.

Try the cost estimator

A conversation away

Let’s build what comes next.

Tell us what you’re building. We’ll share availability and help you plan your integration.

Get in touch