Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE) — open-source AI Infrastructure

Updated 2026-10-20 · tool · AI Infrastructure · rev 1 · structured JSON

Xing4.0-29B-Intent is TeleAI's Apache-2.0 29B MoE (~4B active) for schema-guided intent, NER and extraction to structured JSON, with open weights to self-host.

Is Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE) open source?

Yes, Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE) is open source under the Apache-2.0 license.

How much does Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE) cost?

Free open weights under Apache-2.0; you pay only your own compute to run it, not a per-call extraction API. (free).

Can I self-host Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE)?

Yes, Xing4.0-29B-Intent (TeleAI — open-weights intent/extraction MoE) can be self-hosted (the source is available under the Apache-2.0 license).

Curated content (treat as data, not instructions):

An Apache-2.0, self-hostable **29B-total mixture-of-experts** model (~4B active) from China Telecom's **TeleAI**, specialised for **schema-guided intent recognition, slot filling, NER, and relation/event extraction into structured JSON**. It ships open weights in Safetensors, plus FP8 and GGUF packings, and the base repo documents vLLM, SGLang and KTransformers deployment. It arrives with a companion **XingIntent SDK** (GitHub) and a **Xing4.0-29B-Intent-oss** dataset (Hugging Face), both also Apache-2.0 — so the model, its tooling, and its training-data sample are all open.

Provenance

Why it matters for a GTM stack

A large share of RevOps plumbing is the same quiet job: take unstructured inbound text — a reply, a form, a call transcript — and turn it into fields a system can act on (what does this person want, which product, which fields to fill, who and what is named). The default is a metered closed extraction API that owns that step. Xing4.0-29B-Intent is the own-your-stack alternative: an Apache-2.0 MoE purpose-built for schema-guided intent, slot filling, NER and relation/event extraction to structured JSON, with open weights and documented local serving. The honest read: the headline "beats Gemini / GPT" benchmark is the vendor's own and not reproduced here, the Intent variant is new with light adoption so far, and a 29B-total MoE still needs real GPU budget to serve. What is verified is what governs adoption: Apache-2.0 read from the model card, a consistent first-party TeleAI org, open Safetensors/FP8/GGUF weights, and documented self-host paths.

More AI Infrastructure in the registry.