drex-v2.0 API
drex-v2.0 from nace-ai is listed for classification. A classifier predicts labels or scores; the exact input, label set and billing basis must be confirmed for this model.
PreparingService type
Sale prices will appear after provider configuration is complete.
- API model ID
- di-nace-aidrex-v20-1629d02ec3
- Model developer
- nace-ai
- Service type
- Classification
- Current availability
- Preparing
Model features
No additional gateway capabilities have been confirmed for this model.
What is drex-v2.0?
Use the public identifier di-nace-aidrex-v20-1629d02ec3 for drex-v2.0 in ServerNet. The gateway uses this identifier to select the configured route; the developer is nace-ai.
Where to use drex-v2.0
- Check which inputs and labels drex-v2.0 supports.
- Evaluate false positives and false negatives on your own dataset.
- Choose thresholds according to your application’s review process.
Build your integration
A native classification route must validate the model-specific input and response. Runtime-based billing also needs a reliable cost ceiling before sale.
Inputs and service limits
A classification label does not guarantee any specific accuracy or safe automated decisions. The model listing does not create an executable or billable route.
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
Frequently asked questions
Is drex-v2.0 available through ServerNet?
drex-v2.0 is currently unavailable for API use. A catalogue listing does not activate billing or access. Choose an available related model or check this page again after the route is verified.
Which model ID and API endpoint should I use for drex-v2.0?
This model needs a native execution route. A chat, embedding or reranking example would not execute the advertised task. Its public page remains a catalogue reference until the route and metering are ready.
How is drex-v2.0 usage charged?
Image, audio, video and other native services can use different billing units. A token tariff is not a valid substitute. Sale opens only after the execution path and bounded billing contract are verified.
What should I check before using drex-v2.0 in production?
A classification label does not guarantee any specific accuracy or safe automated decisions. The model listing does not create an executable or billable route.