QType
QType is a domain-specific language (DSL) for rapid prototyping of AI applications.
It is designed to help developers define modular, composable AI systems using a structured YAML-based specification. QType supports models, prompts, tools, retrievers, and flow orchestration, and is extensible for code generation or live interpretation.
🚀 Quick Start
Install QType:
pip install qtype[interpreter]
Create a file hello_world.qtype.yaml that answers a question:
id: hello_world
flows:
- id: chat_example
description: A simple chat flow with OpenAI
mode: Chat
steps:
- id: llm_inference_step
model:
id: gpt-4
provider: openai
auth:
id: openai_auth
type: api_key
api_key: ${OPENAI_KEY}
system_message: |
You are a helpful assistant.
inputs:
- id: user_message
type: ChatMessage
outputs:
- id: response
type: ChatMessage
Put your openai api key into your .env file:
echo "OPENAI_KEY=sk...." >> .env
Validate it's semantic correctness:
qtype validate hello_world.qtype.yaml
You should see:
INFO: ✅ Schema validation successful.
INFO: ✅ Model validation successful.
INFO: ✅ Language validation successful
INFO: ✅ Semantic validation successful
Launch the interpreter:
qtype serve hello_world.qtype.yaml`
And go to http://localhost:8000/ui to see the user interface for your application:
See the full docs for more examples and guides.
✨ Developing with AI?
Use the QType MCP server to speed yourself up! Just set your assistant to run qtype mcp.
For VSCode, just add the following to .vscode/mcp.json:
{
"servers": {
"qtype": {
"type": "stdio",
"command": "qtype",
"cwd": "${workspaceFolder}",
"args": ["mcp", "--transport", "stdio"]
}
}
}
For Claude Code:
claude mcp add qtype -- qtype mcp --transport stdio"
🤝 Contributing
Contributions welcome! Please follow the instructions in the contribution guide.
📄 License
This project is licensed under the MIT License.
See the LICENSE file for details.
🧠 Philosophy
QType is built around modularity, traceability, and rapid iteration. It aims to empower developers to quickly scaffold ideas into usable AI applications without sacrificing maintainability or control.
Stay tuned for upcoming features like:
- Integrated OpenTelemetry tracing
- Validation via LLM-as-a-judge
- UI hinting via input display types
- Flow state switching and conditional routing
Happy hacking with QType! 🛠️
Metadata
Release files for qtype 0.1.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qtype-0.1.18.tar.gz | 3.6 MB | With provenance | Details for qtype-0.1.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qtype-0.1.18-py3-none-any.whl | Python 3 | none | any | Details for qtype-0.1.18-py3-none-any.whl |
Total release size: 6.0 MB
Release files / qtype-0.1.18.tar.gz
| Download URL | qtype-0.1.18.tar.gz |
|---|---|
| Size | 3.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3aac77117c02386a76c2674565b1e2463d3574c57276817c7394a1e006344ba
|
|
BLAKE2b-256 checksum How to use checksums |
6f68288a03795d654552fd2695727d6482ed2cca479282266a0a0f3a4b0e40e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logRelease files / qtype-0.1.18-py3-none-any.whl
| Download URL | qtype-0.1.18-py3-none-any.whl |
|---|---|
| Size | 2.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fef702c78652599a36486ad76b677470fda87c17d653906955b1678cc74b15bd
|
|
BLAKE2b-256 checksum How to use checksums |
2ad37d5006ed249c89f2f7d12bd32c3d43edfdbb0a7ca3b0c157ad9a950999da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logSecurity for qtype 0.1.18
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for qtype-0.1.18.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.