RadixArk · Text chat

DaisyRose-27B API

DaisyRose-27B is a text-generation model from RadixArk. In ServerNet, its chat route accepts conversation messages and returns a generated answer; the price separates input and output tokens.

Available

Toman per million tokens

Input59,837
Output747,957

The usage rate is fixed at request admission. Reported consumption determines the final usage amount.

API model ID
di-radixarkdaisyrose-27b-d30aedfb61
Model developer
RadixArk
Service type
Text chat
Current availability
Available
Configured context limit
262,144 tokens
Gateway output cap
4,096 tokens

Model features

Reasoning ✓

Tool calling ✓

Streaming ✓

What is DaisyRose-27B?

Use the public identifier di-radixarkdaisyrose-27b-d30aedfb61 for DaisyRose-27B in ServerNet. The gateway uses this identifier to select the configured route; the developer is RadixArk.

Where to use DaisyRose-27B

  • Add DaisyRose-27B to a support assistant that receives the relevant conversation as text.
  • Test DaisyRose-27B on summaries and extraction using your own documents, with a small output limit first.
  • Compare answer quality, total token usage and cost per completed task before choosing DaisyRose-27B for production.

Model description

Original catalogue description in English. It describes the model; the gateway limits and availability on this page define what you can request here.

DaisyRose-27B is RadixArk's multimodal reasoning model, trained from Qwen3.8-27B with reinforcement learning only on long-horizon agent tasks. It improves on the base model in agentic coding, reasoning and instruction following, with thinking that can be enabled or disabled, image understanding and a 256K-token context.

SELECTION NOTES

How to evaluate this model

This gateway lists a context limit of 262,144 tokens and an output cap of 4,096 tokens for DaisyRose-27B. Keep instructions, history and the requested response within the applicable limits.

Before you integrate

  • Use a representative test set and check factual accuracy, format and failure cases.
  • Keep the first request bounded. Follow the operation-specific example and its API scope.
  • Record response time and usage in your own environment before setting a production budget.

Conversation & code

Compare output limits, tool calling and streaming on representative prompts.

Compare models ↗

Build your integration

Send system and user messages, set max_tokens and store X-Request-Id with your usage record. Stream only when this route supports it. Function calls describe actions for your application to run; the gateway does not execute your tools.

Inputs and service limits

The current chat route accepts text only and one completion per request. Images, audio and hosted paid tools are not enabled by the source model’s capabilities. The configured context and output limits may be below the developer’s maximum. Test language quality on your own dataset.

A request cost example

For 1,000 input tokens and 500 output tokens, without a cache discount. This is a catalogue estimate, not a fixed request fee. Reported consumption and the price frozen for your request determine the usage amount.

Estimated usage, Toman
435

Plan your token usage

Estimate from the displayed uncached token rates. This is a planning calculation; final billing follows actual usage and the applicable request contract.

Tokens are not words. Cached input, special modes and reported usage can change the final amount.

This calculator runs locally and makes no AI request.
Rate-based estimate · IRT—Per request · IRT: —

Connect to DaisyRose-27B API

Enable ai:chat on your key and ai:models:read to check availability. Set SERVERNET_API_KEY in your server environment. Change the idempotency key for each new request; keep it unchanged only for an identical retry.

ai:chat
curl https://servernet.cloud/v1/chat/completions \
  -H "Authorization: Bearer $SERVERNET_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: CHANGE_FOR_EACH_NEW_REQUEST' \
  -d '{
    "model": "di-radixarkdaisyrose-27b-d30aedfb61",
    "messages": [
        {
            "role": "user",
            "content": "Hello"
        }
    ],
    "max_tokens": 128
}'

Use the same Idempotency-Key when retrying an identical request. Successful responses are replayed without a second charge for 24 hours. Do not automatically retry when x-should-retry:false is present. The key is shown once. Store it in a server environment variable. Keep it out of browser code, GitHub and logs.

Keys, budgets and usage reports

Frequently asked questions

Is DaisyRose-27B available through ServerNet?

DaisyRose-27B is currently available on the configured route. Check GET /v1/models before sending a request: availability can change with provider capacity, catalogue freshness or account configuration.

Which model ID and API endpoint should I use for DaisyRose-27B?

Use di-radixarkdaisyrose-27b-d30aedfb61 as the model field, the endpoint shown below and the matching key scope. ServerNet keys are project-specific; an SDK also needs https://servernet.cloud/v1 as its base URL.

How is DaisyRose-27B usage charged?

Input and output tokens use separate tariffs. Reported reasoning tokens, where supported, count towards output consumption. Cached input receives a discount only when a verified cached tariff exists. The dashboard records consumption for each request.

What should I check before using DaisyRose-27B in production?

The current chat route accepts text only and one completion per request. Images, audio and hosted paid tools are not enabled by the source model’s capabilities. The configured context and output limits may be below the developer’s maximum. Test language quality on your own dataset.

Compare models for the same task

Only available models are exposed by the API. Availability requires a configured provider, valid prices and a supported execution path.