models

mimo-v2-pro

Markdown · JSON

mimo-v2-pro

MiMo-V2-Pro is Xiaomi’s agent-focused text model for software engineering, multi-step planning and tool-driven work. Its context of up to 1 million tokens helps keep substantial project material, task constraints and successive observations within a coherent workflow.

About the model

This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.

Foundation for agent work

MiMo-V2-Pro is Xiaomi’s flagship foundation model for complex agent workloads and software engineering. Its role is to reason about a task, organize the required steps and use information returned by tools to continue toward a defined result. The model’s emphasis goes beyond composing a single answer: it is designed around connected work in which earlier decisions and observations affect what happens next.

Scale and efficient architecture

The manufacturer describes more than 1 trillion total parameters with 42 billion active parameters. Pro extends the hybrid attention approach of MiMo-V2-Flash, using a 7:1 balance of sliding-window to global attention. A lightweight multi-token prediction layer supports generation, and the advertised context reaches 1 million tokens. These are architectural and context properties of Pro; they do not specify the execution speed, memory allocation or request limits of a particular integration.

Release lineage

Hunter Alpha is identified by Xiaomi as an early internal test build preceding MiMo-V2-Pro. The released Pro model has its own name and refinements to long-context work and agent-scenario stability. This distinction matters when comparing descriptions or retaining a model identity: an earlier test build, MiMo-V2-Flash and MiMo-V2-Omni each have a separate role and specification.

Built for agents

The model is fine-tuned through supervised learning and reinforcement learning across varied agent frameworks, with attention to tool calls and multi-step reasoning. Prepare a task with an observable completion condition and descriptions of the available tools. For example, a project assistant can receive a change request, examine the supplied modules, propose the affected components and continue after a tool returns a build error. The useful output is a sequence of decisions tied to actual observations, followed by the requested code, explanation or work summary. The connected environment performs the actions.

Software engineering and frontend tasks

Xiaomi highlights system design, task planning and code-oriented problem solving. Its demonstrations include interactive web pages and a browser-based game produced within an agent environment. An illustrative development brief can specify page behavior, navigation, data states and a responsive layout, then ask for an implementation and checks against those requirements. For an existing project, supply the current files, the failing case and the interfaces that must remain unchanged. Ask for a focused change and an explanation of the dependencies it touches rather than an unrelated replacement application.

Long context and a checkable result

The context of up to 1 million tokens is useful when several files, documents, instructions and prior observations belong to the same task. Organize that material by its role: authoritative requirements, current code, reference examples and tool results. Specify the final artifact and its acceptance conditions before asking the agent to proceed. A documentation task might need a comparison with unresolved questions; an engineering task might need a patch and a record of what was checked.

Practical limitations and edition scope

A long context provides room for material but does not guarantee that a generated project is correct or that every requirement has been satisfied. Return actual errors and observations for the next step and validate the result in the intended environment. The manufacturer explicitly frames robustness across complex real tasks as something to assess and improve. This description covers the text-and-tool agent specialization of MiMo-V2-Pro; modality features of Omni and specifications of later MiMo generations belong to their respective models. The tools, available parameters and output handling remain properties of the connected application.

Practical task

Correct an error-state transition

Technical example in English

Correct an error-state transition

A text specification says a search box has idle, loading, results and error states. Existing logic sets loading=true before fetch and false only on success, so failures leave the spinner visible. Propose pseudocode that preserves results on success, shows an error on failure and always clears loading. Include the two distinguishing checks.

Expected result

Focused async pseudocode and success/failure checks covering final loading state and visible result or error.

Check the result

Check that loading is cleared in both branches without suppressing the error.
Ailoot Ultra · OpenAI Chat POST /v1/chat/completions mimo-v2-pro

mimo-v2-pro

Xiaomi /mimo-v2-pro

Overview

MiMo-V2-Pro is Xiaomi’s agent-focused text model for software engineering, multi-step planning and tool-driven work. Its context of up to 1 million tokens helps keep substantial project material, task constraints and successive observations within a coherent workflow.

Accepted inputs
Text
Results
Text

Available in Ailoot · inputs & methods

Ailoot Ultra · OpenAI Chat POST /v1/chat/completions
Input types
text
Output types
text
Output format
json or SSE
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
mimo-v2-pro
Default—
FieldmessagesTypemessage[]RequirementRequiredValues & limits
Minimum items: 1
Default—
Fieldmessages[].roleTypestringRequirementRequiredValues & limits
Examples: system, user, assistant, tool, function
Conditions: These roles are explicitly represented by Source compatibility types; the exact model role set remains model-specific.
Model-specific
Default—
Fieldmessages[].contentTypestring|content_part[]|nullRequirementOptionalValues & limitsDefault—
Fieldmessages[].tool_callsTypetool_call[]RequirementOptionalValues & limitsDefault—
Fieldmessages[].tool_call_idTypestringRequirementOptionalValues & limits
Applies when: role=tool; use actual returned ID
Default—
Fieldmessages[].nameTypestringRequirementOptionalValues & limitsDefault—
Fieldmessages[].reasoning_contentTypestringRequirementOptionalValues & limits
Applies when: Round-trip actual returned reasoning where this model uses it
Default—
Fieldmessages[].reasoning_detailsTypeobject|arrayRequirementOptionalValues & limits
Model-specific
Default—
Fieldmax_tokensTypeintegerRequirementOptionalValues & limits
Minimum: 1
Model-specific
Default—
Fieldmax_completion_tokensTypeintegerRequirementOptionalValues & limits
Minimum: 1
Model-specific
Default—
FieldstreamTypebooleanRequirementOptionalValues & limitsDefaultfalse
Fieldstream_options.include_usageTypebooleanRequirementOptionalValues & limits
Model-specific
Default—
FieldtemperatureTypenumberRequirementOptionalValues & limits
Model-specific
Default—
Fieldtop_pTypenumberRequirementOptionalValues & limits
Model-specific
Default—
FieldstopTypestring|string[]RequirementOptionalValues & limits
Model-specific
Default—
FieldtoolsTypefunction_tool[]RequirementOptionalValues & limits
Model-specific
Default—
Fieldtools[].typeTypestringRequirementOptionalValues & limits
function
Model-specific
Default—
Fieldtools[].function.nameTypestringRequirementRequiredValues & limits
Applies when: function tool supplied
Default—
Fieldtools[].function.descriptionTypestringRequirementOptionalValues & limitsDefault—
Fieldtools[].function.parametersTypeJSON_schemaRequirementOptionalValues & limitsDefault—
Fieldtool_choiceTypestring|objectRequirementOptionalValues & limits
Model-specific
Default—
Fieldparallel_tool_callsTypebooleanRequirementOptionalValues & limits
Model-specific
Default—
Fieldresponse_formatTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
Fieldreasoning_effortTypestringRequirementOptionalValues & limits
Model-specific
Default—
FieldreasoningTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
Fieldservice_tierTypestringRequirementOptionalValues & limits
Model-specific
Default—
FieldinstructionsTypestringRequirementOptionalValues & limits
Compatibility field
Default—
FieldfunctionsTypefunction[]RequirementOptionalValues & limits
Model-specific
Default—
Fieldfunction_callTypestring|objectRequirementOptionalValues & limits
Model-specific
Default—
Fieldprompt_cache_optionsTypeobjectRequirementOptionalValues & limits
Model-specific
Default—
FieldmodalitiesTypestring[]RequirementOptionalValues & limits
text
Default—
FieldproviderTypeobjectRequirementOptionalValues & limits
Conditions: provider.options is rejected on this Ultra text route
Default—
Fieldcache_control.ttlTypestringRequirementOptionalValues & limits
Conditions: 1h is rejected in actual prompt-cache locations
Default—
Input material combinations

Text · UTF8 text

messages[].content

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, messages
Parametermaterial_typesContracttext
ParametermessagesContractmessage array with role/content shape
Parameterfile_materialContractactual UTF-8 document inserted as literal text; no file ID inferred
Parameteroptional_controlsContractstream, temperature, top_p, stop, max_tokens, max_completion_tokens, reasoning, response_format, tools, tool_choice
Parametercontrol_scopeContractmodel-specific; user function tools differ from hosted tools
Parameteroutput_modalitiesContracttext
Parameterhosted_operationsContractfalse
Parametermultimodal_input_bindingContractnull

Lifecycle: synchronous_or_streamed

Send exact model ID with messages.

Context length is not an output cap.

A text file may supply literal text; image/audio/file-object inputs need exact binding.

Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

ConfigurationRate scheduleCharge
ConfigurationBase token ratesRate scheduleBase rateCharge
Input · Input tokens $0.0022 / 1K tokens
Output · Output tokens $0.0066 / 1K tokens
Input · Cache read $0 / 1K tokens
Input · Cache write $0 / 1K tokens
Input · Cache write, 1 hour — / 1K tokens

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Example requests

Ailoot Ultra · OpenAI Chat

curlPython SDKPython stream
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
python3 - <<'PY_REQUEST'
import json,os
from pathlib import Path
p=json.loads('{"model": "mimo-v2-pro", "messages": [{"role": "user", "content": "Explain the difference between an observation and a hypothesis in three sentences."}]}')

Path("request.json").write_text(json.dumps(p,ensure_ascii=False))
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/chat/completions \
  -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path
r=json.loads(Path("result.json").read_text())
for x in r.get("choices",[]):
    if x.get("message",{}).get("content"): print(x["message"]["content"])
PY_RESULT
from openai import OpenAI
import os

if not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")
client=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)
result=client.chat.completions.create(model='mimo-v2-pro',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}])
import base64, json
from pathlib import Path

def save_result(data, stem="result"):
    # Keep every field, including usage, IDs, reasoning and tool requests.
    Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")
    print(json.dumps(data, ensure_ascii=False, indent=2))
    def save_blob(encoded, suffix, label):
        raw = base64.b64decode(encoded, altchars=b"-_", validate=True)
        ext = "png" if raw.startswith(b"\x89PNG\r\n\x1a\n") else "jpg" if raw.startswith(b"\xff\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix
        file = Path(stem + "-" + label + "." + ext)
        file.write_bytes(raw)
        print("Saved", file)
    for index, block in enumerate(data.get("content") or []):
        print("Content", index, json.dumps(block, ensure_ascii=False))
    for choice in data.get("choices") or []:
        print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))
    for index, item in enumerate(data.get("output") or []):
        print("Output", index, json.dumps(item, ensure_ascii=False))
        if item.get("type") == "image_generation_call" and item.get("result"):
            save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))
    for ci, candidate in enumerate(data.get("candidates") or []):
        for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):
            print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))
            blob = part.get("inlineData") or part.get("inline_data")
            if blob and blob.get("data"):
                mime = blob.get("mimeType") or blob.get("mime_type")
                suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")
                save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))

save_result(result.to_dict(mode="json"))
from openai import OpenAI
import os
from pathlib import Path

if not os.environ.get("AILOOT_API_KEY", "").strip(): raise SystemExit("Set AILOOT_API_KEY before making a request")
client=OpenAI(base_url="https://api.ailoot.ai/v1",api_key=os.environ["AILOOT_API_KEY"],max_retries=0)
import base64, json
from pathlib import Path

def save_result(data, stem="result"):
    # Keep every field, including usage, IDs, reasoning and tool requests.
    Path(stem + ".json").write_text(json.dumps(data, ensure_ascii=False, indent=2), encoding="utf-8")
    print(json.dumps(data, ensure_ascii=False, indent=2))
    def save_blob(encoded, suffix, label):
        raw = base64.b64decode(encoded, altchars=b"-_", validate=True)
        ext = "png" if raw.startswith(b"\x89PNG\r\n\x1a\n") else "jpg" if raw.startswith(b"\xff\xd8") else "webp" if raw[:4] == b"RIFF" and raw[8:12] == b"WEBP" else suffix
        file = Path(stem + "-" + label + "." + ext)
        file.write_bytes(raw)
        print("Saved", file)
    for index, block in enumerate(data.get("content") or []):
        print("Content", index, json.dumps(block, ensure_ascii=False))
    for choice in data.get("choices") or []:
        print("Choice", choice.get("index"), json.dumps(choice.get("message", choice.get("delta", {})), ensure_ascii=False))
    for index, item in enumerate(data.get("output") or []):
        print("Output", index, json.dumps(item, ensure_ascii=False))
        if item.get("type") == "image_generation_call" and item.get("result"):
            save_blob(item["result"], item.get("output_format") or "bin", "output-" + str(index))
    for ci, candidate in enumerate(data.get("candidates") or []):
        for pi, part in enumerate((candidate.get("content") or {}).get("parts") or []):
            print("Candidate/part", ci, pi, json.dumps(part, ensure_ascii=False))
            blob = part.get("inlineData") or part.get("inline_data")
            if blob and blob.get("data"):
                mime = blob.get("mimeType") or blob.get("mime_type")
                suffix = {"image/png":"png", "image/jpeg":"jpg", "image/webp":"webp", "audio/wav":"wav", "audio/mpeg":"mp3", "video/mp4":"mp4"}.get(mime, "bin")
                save_blob(blob["data"], suffix, "candidate-" + str(ci) + "-part-" + str(pi))

with client.chat.completions.stream(model='mimo-v2-pro',messages=[{"role":"user","content":"Explain observations and hypotheses in three sentences."}]) as stream:
    with Path("stream-events.jsonl").open("w",encoding="utf-8") as log:
        for event in stream:
            payload=event.to_dict(mode="json")
            log.write(json.dumps(payload,ensure_ascii=False)+"\n"); log.flush()
            print(json.dumps(payload,ensure_ascii=False))
    final=stream.get_final_completion()
    save_result(final.to_dict(mode="json"),"stream-result")

Receive and save results

Ailoot Ultra · OpenAI Chat

json or SSE

Keep all completed results

Keep every complete returned response, file and content part.

Keep every choice and its content/tool calls/reasoning. In SSE assemble deltas by choice/tool index, retain the final finish reason and usage.

If the original response needs checking

Keep request/response IDs and headers. No generic text job retrieval URL is supplied.

Response fields
FieldType
Fieldchoices[].indexTypeinteger
Fieldchoices[].message.contentTypestring|null
Fieldchoices[].message.tool_callsTypetool_call[]
Fieldchoices[].message.reasoning_contentTypestring
Fieldchoices[].message.reasoning_detailsTypeobject|array
Fieldchoices[].finish_reasonTypestring|null
FieldusageTypeobject
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionInvalid required fields, material representation or parameter valueNext stepCorrect the indicated fields before a new creation request.

Aliases

Model aliases

Ailoot Ultra mimo-v2-pro

Method path aliases

Use the method paths shown above.

Related caller IDs

mimo-v2-pro

Ailoot Ultra · Anthropic Messages POST /v1/messages mimo-v2-pro

mimo-v2-pro

Xiaomi /mimo-v2-pro

Overview

MiMo-V2-Pro is Xiaomi’s agent-focused text model for software engineering, multi-step planning and tool-driven work. Its context of up to 1 million tokens helps keep substantial project material, task constraints and successive observations within a coherent workflow.

Accepted inputs
Text
Results
json · sse

Available in Ailoot · inputs & methods

Ailoot Ultra · Anthropic Messages POST /v1/messages
Input types
text
Output types
json, sse
Output format
JSON or SSE
FieldTypeRequirementValues & limitsDefault
FieldmodelTypestringRequirementRequiredValues & limits
mimo-v2-pro
Default—
FieldmessagesTypemessage[]RequirementRequiredValues & limitsDefault—
Fieldmessages[].roleTypestringRequirementRequiredValues & limits
user, assistant
Default—
Fieldmessages[].contentTypestringRequirementRequiredValues & limitsDefault—
Fieldmax_tokensTypeintegerRequirementRequiredValues & limitsDefault—
FieldstreamTypebooleanRequirementOptionalValues & limitsDefaultfalse
Input material combinations

Text · UTF-8 text

messages[].content string

Method parameters and lifecycle
ParameterContract
Parametercontent_typeContractapplication/json
ParameterrequiredContractmodel, messages, max_tokens
Parameteroptional_controlsContractstream
Parametermaterial_typesContracttext
Parametertext_file_materialContractRead the actual UTF-8 document and put its text in the indicated input or message content string.

Lifecycle: synchronous_or_streamed

Pricing

Tariff references do not add request options. Supported parameters are listed for the selected method.

Fast mode
Not specified When fast mode is selected
Flex mode
Not specified When flex mode is selected
Maximum reasoning effort
Not specified When maximum reasoning effort uses the default adjustment

Ailoot rates

Prices by configuration

ConfigurationRate scheduleCharge
ConfigurationBase token ratesRate scheduleBase rateCharge
Input · Input tokens $0.0022 / 1K tokens
Output · Output tokens $0.0066 / 1K tokens
Input · Cache read $0 / 1K tokens
Input · Cache write $0 / 1K tokens
Input · Cache write, 1 hour — / 1K tokens

Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →

Example requests

Ailoot Ultra · Anthropic Messages

Complete minimal JSON bodycurl · use your UTF-8 documentPython · save the complete result
{
  "model": "mimo-v2-pro",
  "max_tokens": 128,
  "messages": [
    {
      "role": "user",
      "content": "Summarize the incident report."
    }
  ],
  "stream": false
}
set -eu
: "${AILOOT_API_KEY:?Set your Ailoot API key}"
: "${AILOOT_TEXT_FILE:?Set your actual UTF-8 document}"
export AILOOT_TEXT_FILE
python3 - <<'PY_REQUEST'
import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'mimo-v2-pro', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
Path('request.json').write_text(json.dumps(payload, ensure_ascii=False), encoding='utf-8')
PY_REQUEST
curl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/messages \
  -H "x-api-key: $AILOOT_API_KEY" -H 'anthropic-version: 2023-06-01' -H 'Content-Type: application/json' \
  --data-binary @request.json -D response-headers.txt -o result.json
python3 - <<'PY_RESULT'
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))
PY_RESULT
import json, os
from pathlib import Path

source_file = Path(os.environ['AILOOT_TEXT_FILE'])
if not source_file.is_file():
    raise SystemExit('Set AILOOT_TEXT_FILE to your actual UTF-8 document')
text = source_file.read_text(encoding='utf-8')
if not text.strip():
    raise SystemExit('Choose a document containing text')
payload = {'model': 'mimo-v2-pro', 'max_tokens': 128, 'messages': [{'role': 'user', 'content': 'Summarize the incident report.'}]}
payload['messages'][0]['content'] = 'Summarize this material and quote supporting source passages.\n\n' + text
from urllib.request import Request, urlopen
from urllib.error import HTTPError

api_key = os.environ['AILOOT_API_KEY']
if not api_key.strip():
    raise SystemExit('Set AILOOT_API_KEY before making a request')
headers = {'x-api-key': 'PLACEHOLDER_KEY', 'anthropic-version': '2023-06-01', 'Content-Type': 'application/json'}
headers['x-api-key'] = api_key
request = Request('https://api.ailoot.ai/v1/messages', data=json.dumps(payload, ensure_ascii=False).encode('utf-8'), headers=headers, method='POST')
try:
    with urlopen(request, timeout=120) as response:
        raw = response.read()
        Path('response-headers.txt').write_text(str(response.headers), encoding='utf-8')
except HTTPError as error:
    Path('result.json').write_bytes(error.read())
    Path('response-headers.txt').write_text(str(error.headers), encoding='utf-8')
    raise
Path('result.json').write_bytes(raw)
import json
from pathlib import Path

result = json.loads(Path('result.json').read_text(encoding='utf-8'))
print(json.dumps(result, ensure_ascii=False, indent=2))

Receive and save results

Ailoot Ultra · Anthropic Messages

JSON or SSE

Keep all completed results

Keep every complete returned response, file and content part.

Keep all content blocks, thinking signatures and actual tool-use IDs. Assemble all SSE block deltas; a first text block is not the complete output.

If the original response needs checking

Keep request/response IDs and headers. No generic text job retrieval URL is supplied.

Response fields
FieldType
FieldidTypestring
FieldmodelTypestring
Fieldcontent[]Typetext|thinking|tool_use|other content block
Fieldstop_reasonTypestring|null
FieldusageTypeobject
Errors and next steps
ResponseConditionNext step
Response400 · invalid_request_errorConditionInvalid required fields, material representation or parameter valueNext stepCorrect the indicated fields before a new creation request.

Aliases

Model aliases

Ailoot Ultra mimo-v2-pro

Method path aliases

Use the method paths shown above.

Related caller IDs

mimo-v2-pro

FAQ · mimo-v2-pro
What inputs and results are available?

POST /v1/chat/completions · mimo-v2-pro: text → text

POST /v1/messages · mimo-v2-pro: text → json, sse

Which fields does the request use?

POST /v1/chat/completions · mimo-v2-pro: model, messages, stream, modalities, provider

POST /v1/messages · mimo-v2-pro: model, messages, max_tokens, stream

What limits apply?

POST /v1/chat/completions · mimo-v2-pro: messages.min_items: 1

More details

Connect Ailoot to Claude Code, OpenCode, Hermes or your own app.

The company and its project portfolio

The company and its project portfolio: millions of customers; monthly sales in the billions.

Buy tokens at a discount.

Subscription discounts for regular use. Promo codes offer up to 50% off token purchases.

Subscription
Choose a discounted plan for your regular requests.
Promo code: up to 50% off
Enter your code at checkout. The price updates to reflect the current promotion.
Spending in your history
The model, tokens and amount are recorded for each request.

Choose a subscription · View model prices

Connect the API to a product you sell.

Use Ailoot in SaaS, apps and bots under its official service offer and licence agreement. Request a reseller licence for resale.

Commercial application
Add text, image, video and audio generation to paid features in your service.
Reseller licence
Send a description of your project and how you provide access. Request written terms for use and resale.
Documents on the website
The service offer, licence agreement and data processing policy are available before you connect.

Request a reseller licence · Service offer and licence agreement