Noul
Yes / no“Does this message describe a billing issue?”
Probability of yes0.94
Test one property. Your application chooses when to act or request review.
if (p > 0.9) flagForReview()Open in playground Workspace
Support ticketFast decisions.
Example library
56 examplesSelect to load. Run separately.
01
The context for every questionState
Image input is not available on this machine yet. You can keep using Text and JSON.
Resized to 512 px before sending. One shared state image; add references in questions and options.
Camera input
Live workspace
Point your camera at a scene.
Set your questions below.
Your camera is off
LIVEEnable it to preview. Choose Run live
when you’re ready to send frames.
Camera off
Preview first. Each new frame is sent after the previous answer returns.
About this example
02
Questions
3 questionsKey each question by name. Instructions and descriptions can be text, image objects, arrays, other objects, or null. Use {"image":"data:image/png;base64,…","text":"Optional text"} for an image.
Add questionUp to 32
Evaluation settings
Compare all levels in one read, or evaluate each level separately. Separate evaluation uses more reads and needs a description for every level. Questions remain separate.
Live camera
LIVEEach answer uses a captured frame. The preview stays live.
03
No run yetAnswers
Last successful run
- Model processing
- Unavailable
- Hosting & transfer
- Unavailable
- Total response
- Unavailable
Measured for the whole request, across all questions.
Model & hosting details
- Model
- Djev
- Inference host
- Modal
- Site & API delivery
- Vercel
- Model token usage
- Unavailable
Model processing includes preparation and backend requests, not isolated GPU time. The remaining browser-observed time includes API work, routing and response delivery. Recoverable requests also include queueing, retries and polling. After resuming, a continuous browser total is unavailable.
Token usage includes repeated internal reads. It is not a billing total.
Your answers appear here.
Prepare your state and questions,
then run them on Djev.
Yes / noChoiceScore
Use this request
Copy the exact request, including images and its request ID when available.
Request & response Developer tools
Draft preview · POST https://api.djev.dev/v1/request
Your workspace
Access & keys
Welcome to Djev.
Enter your invitation to open the playground and create API keys. No email or social sign-in.
Already have access?
Save your recovery key
Shown onceSave your recovery key or you will lose access to your account. There is no email recovery.
Signed in
Account ID
Your unique account identifier. This is not a sign-in key.
API keys
Create a separate key for each app. Use it directly for API requests; your recovery key is only for signing in.
Loading keys…
Your invitations
Invite someone
Share one code with each person. Each invitation can be used once.
Loading your invitation allowance…
The export contains access codes. Store it privately.
Your workspace
Usage & credits
One balance for your playground and every API key.
Available credit
—Shared across your account.
$35 / billion input tokens
$0.035 per million · Output tokens are free
Add credit
Loading credit availability…
Activity
Your usage
- Input tokens
- —
- Completed requests
- —
- Spend
- —
Input tokens over time
UTCYour usage will appear here.
View usage table
| Period (UTC) | Input tokens | Requests | Spend |
|---|
Completed requests only. Updates every few seconds while this page is open. Changing the source filters activity; your balance always covers the whole account.
Credits
Recent purchases
No purchases to show.
| Date (UTC) | Credit | Status |
|---|
Djev / Developer guide
Build with Djev.
Give your agent context, a clear question and a defined set of answers. Use the probabilities in your application’s next step.
Set up your agent- 01Context
Text, structured JSON or images.
- 02Typed questions
Ask for yes/no, a choice or a score.
- 03Probabilities
Read a small, structured response.
- 04Your code acts
Route, rank, flag or ask for review.
Choose the answer shape
Three ways to ask.
Illustrative values, not live results.
Probabilities are not guarantees of correctness.
Choice
One of your options“Which team should handle this request?”
- billing
- 0.91
- technical
- 0.06
- other
- 0.03
Compare named options. Get the winning label and a probability for each.
routeTo(answer.choice)Open in playground Score
Ordered levels“How fully does the source support the answer?”
Weighted level · scale 0–21.6 / 2
0 × 0.1 + 1 × 0.2 + 2 × 0.7
Define a rubric from low to high. Get a fractional score and level probabilities.
rankBy(answer.score)Open in playground These snippets illustrate application logic. Test your criteria and thresholds on your own examples before automating decisions.
From idea to integration
Install the Djev skill.
Paste this into your coding agent, then describe what you want to build. It points to the current API contract and project skill.
Create a key in Access & keys. Set DJEV_API_KEY on your server. Keep your recovery key for account sign-in.
No credentials are included. The prompt does not create an account or send model requests.
Install from a terminal instead
For agents that support .agents/skills. Run from your project root. Review an existing Djev skill before replacing it.
The command downloads documentation only. Add your API key separately.
Put it to work
Patterns for your next build.
Keep each question focused.
Your code owns the workflow.
- 01Agent routing
- Use Choice to select a tool or team from explicit descriptions. Add an “other” option when a request may not fit.
- 02Retrieval ranking
- Give each candidate the same relevance rubric, then compare Score results. Check the ranking against examples you have labeled.
- 03Evidence checks
- Provide the claim and its source together. Ask a Noul question about support, or use Score for levels of coverage.
- 04Image comparison
- Attach a reference image and image-bearing Choice options. Ask about a specific visible property, such as shape or arrangement.
- 05Live frames
- Evaluate individual camera frames with the same questions. Keep one request in flight and send the newest frame next.