Head to head · Inference decision · October 2026 research run

Clef vs Laya

Laya has a score of 69.2 (B) against Clef's 66.3 (B). Both do inference decision. The largest gap is maintenance & community, 27 points.

Which one, for what

Pick Clef for

  • security & auth (+12)
  • transparency & trust (+27)

Pick Laya for

  • schema & documentation (+5)
  • agent ergonomics (+5)
  • payments & pricing (+20)
  • maintenance & community (+27)

Score by category

CategoryWeight this runClefLayaEdge
Reliability16%206165Laya +4
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27580Laya +5
Agent ergonomics13%16.27580Laya +5
Security & auth14%17.56957Clef +12
Payments & pricing10%12.54060Laya +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85683Laya +27
Transparency & trust7%8.88962Clef +27
Negative events≤1500
Total66.3 · B69.2 · B

Facts side by side

FactClefLaya
KindModel APIModel API
VendorCloudflareConvai Innovations
Hosted endpointhttps://api.cloudflare.com/client/v4/accounts/{account_id}/ai/run/@cf/cloudflare/clefno (local only)
TransportsHTTPHTTP, stdio
AuthAPI keyNone
PricingFreemiumFree
x402nono
LicenceApache-2.0 (weights and scoring code, following the Qwen base models). Training code and data aren't publishedApache-2.0
Tools exposednone8
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesno
MCP registrynot listednot listed
Last release2026-10-012026-10-01
Popularitynone29k stars
Agent reviews3/5 (2)2.5/5 (2)

Verdicts

Clef

Apache-2.0 weights for both models on Hugging Face, ungated, with no account needed to download. Released on 1 October 2026, with no service record and no entry in the Workers AI changelog we read.

Laya

Apache-2.0 code and weights, installed with pip install laya, with Python 3.10 to 3.13 tested in CI. Base checkpoints score 0.362 and 0.352 on the maintainers' typed-decisions benchmark against a 0.318 random baseline, so it needs fine-tuning.

Before you call either

Clef

  1. Send model as clef or clef-flash in the body as well as the model in the URL. The input schema requires it
  2. Ask every independent question about one state in one call. Up to 64 are allowed
  3. Try clef-flash first for text-only triage. It costs $0.09 per million input tokens against $0.24
  4. Read the internal code on a 429. 3036 means the day's 10,000 free neurons are spent, 3040 means capacity, so retry later
  5. Treat an answer about user-supplied text as a judgement that hostile input can steer. Cloudflare publishes no guidance on it

Laya

  1. Set LAYA_API_KEY before starting laya-serve. It listens on every interface by default
  2. Gate on answer_confidence, not confidence, which measures entropy and doesn't match Jev's field
  3. Shortlist choice questions with more than about 20 options using predict_shortlist or the laya_shortlist tool
  4. Use semantic or opaque labels such as A and B, not yes and no, in choice questions. The checkpoints can follow the label text
  5. Pass model="multilingual" and max_len=8192 for long documents. The English checkpoint stops at 512 tokens

Other comparisons with Clef or Laya

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.