Cloudflare · Classification

clef API

clef from Cloudflare is listed for classification. A classifier predicts labels or scores; the exact input, label set and billing basis must be confirmed for this model.

Preparing

Service type

Sale prices will appear after provider configuration is complete.

API model ID
di-cloudflareclef-527cb65dad
Model developer
Cloudflare
Service type
Classification
Current availability
Preparing

Model features

No additional gateway capabilities have been confirmed for this model.

What is clef?

Use the public identifier di-cloudflareclef-527cb65dad for clef in ServerNet. The gateway uses this identifier to select the configured route; the developer is Cloudflare.

Where to use clef

  • Check which inputs and labels clef 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 clef available through ServerNet?

clef 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 clef?

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 clef 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 clef 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.

Compare models for the same task

Jev

typesafe/jev-1.13

Available Classification
Unit rate ceiling, IRT755
1 request · The final usage amount follows the reported result and the permitted request options.
Only available models are exposed by the API. Availability requires a configured provider, valid prices and a supported execution path.