Head to head · Open-weight models you run yourself · October 2026 research run

occamy-1.0 vs Qwen3-Omni-30B-A3B-Instruct

occamy-1.0 scores 61 (C) on agent readiness against Qwen3-Omni-30B-A3B-Instruct's 41.8 (E), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Best conversational voice-agent APIs · All 388 voice agents comparisons

Which one, for what

occamy-1.0 C

Best for Agents that want an Apache 2.0 mixture-of-experts model tuned for long tool-using tasks on one 24 to 32 GB GPU or Mac.

Ahead on

  • Reach, 85 against 55
  • Agent interface, 70 against 60
  • Documentation and upkeep, 74 against 26

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5

Watch for

No safety results, prompt-injection guidance or security contact

Qwen3-Omni-30B-A3B-Instruct E

Best for Agents on a machine with about 96 GB to spare that need one local model to hear, see and answer by voice

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Only a 70.5 GB BF16 build, about 85 GB to run, with no quantised build from Alibaba

Score by category

CategoryWeight this runoccamy-1.0Qwen3-Omni-30B-A3B-InstructEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%258555occamy-1.0 +30
Risk20%205555even
Agent interface10%107060occamy-1.0 +10
Documentation and upkeep10%107426occamy-1.0 +48
Negative events≤1500
TotalC 61/100E 41.8/100

Facts side by side

Factoccamy-1.0Qwen3-Omni-30B-A3B-Instruct
KindOpen-weight modelOpen-weight model
VendorAccio (Accio-Lab)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-022025-09-22
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3/5 (4)2/5 (4)

Verdicts

occamy-1.0

A Qwen3.6-35B-A3B fine-tuned for long agent work with tools, files and code, under plain Apache 2.0, and Accio's 4-bit builds run in about 23 GB. The main gaps are no safety results, agent guidance or security contact, and every benchmark figure is Accio's own.

Qwen3-Omni-30B-A3B-Instruct

An omni-modal cousin that listens, watches and reads, then answers in text or one of three voices, with tool calls from spoken requests, under plain Apache 2.0. Its only build, BF16, needs about 85 GB, and speech out needs Transformers or vLLM-Omni. The main risk is no answers from Qwen and no safety work for speech-driven actions.

Before you call either

occamy-1.0

  1. Serve with --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on vLLM 0.19.0 or SGLang 0.5.10 and later
  2. BF16 is 70.2 GB, so on a 128 GB machine run it without the card's 8-way tensor parallelism
  3. Keep the whole assistant message, reasoning and tool calls included, in later turns, as the card says
  4. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 1.5
  5. With the GGUFs, NFC-normalise input text and read TOKENIZER.md, since the files store qwen2 pre-tokenizer metadata
  6. The base's MTP layer isn't in this checkpoint, Accio-Lab/occamy-1.0-MTP is an experimental separate head

Qwen3-Omni-30B-A3B-Instruct

  1. For text answers, mkdir -p media && vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --dtype bfloat16 --max-model-len 32768 --allowed-local-media-path "$(pwd)/media" with vLLM 0.11.1 or later serves the Thinker on an OpenAI-compatible API
  2. The card's command passes --allowed-local-media-path /, which lets anyone who can reach the server have it read any file on the machine through a file:// URL. Point it at a dedicated folder that holds only the media you mean to send, as above, and give vLLM an absolute path
  3. Send audio as audio_url and images as image_url content parts; vLLM serve doesn't take use_audio_in_video, so pass a video's audio separately
  4. For speech out, load Qwen3OmniMoeForConditionalGeneration in Transformers 4.57.0 or later with qwen-omni-utils, pick speaker Ethan, Chelsie or Aiden, and write the returned waveform at 24 kHz
  5. Call model.disable_talker() or pass return_audio=False when you only need text, which saves about 10 GB and time
  6. Parse tool calls as JSON inside <tool_call> tags yourself, since no parser is named, and confirm actions triggered by speech before running them
  7. Keep use_audio_in_video the same across every step of a conversation, the card warns results go wrong otherwise
  8. Budget memory for video, the card's table rises from 78.85 GB for 15 seconds to 144.81 GB for 120 seconds in BF16

Questions

Which is better for AI agents, occamy-1.0 or Qwen3-Omni-30B-A3B-Instruct?

occamy-1.0 scores 61 (C) on agent readiness against Qwen3-Omni-30B-A3B-Instruct's 41.8 (E), and leads in 3 of 4 scored categories.

Other comparisons with occamy-1.0 or Qwen3-Omni-30B-A3B-Instruct

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.