Skip to content
Good for Bots

JevModel

jevmodel.app

Hosted playground, decision flows, batch processing and API for the Jev model

Good for Bots: Good, 79 of 100Get this badge →

On your homepage, it turns this report’s link to jevmodel.app dofollow.

Scanned

What is JevModel?

JevModel is an independent service providing a hosted playground, decision flows, batch processing, and an API for TypeSafe AI's Jev structured decision model. It is designed for developers and applications needing typed answers such as choices, scores, and yes/no judgments from text or JSON states. The platform allows users to test prompts without signup, build multi-step decision chains on a visual canvas, process batch files in formats like CSV or TXT, and integrate decision-making into code using an API key. It offers multiple pricing options including a free tier with signup tokens, one-time purchase token packs, and subscriptions.

Through a bot’s eyes

“JevModel is an independent hosted playground and API for TypeSafe AI's Jev decision model, offering tools for choice selection, scoring, and boolean judgments.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns that JevModel provides access to TypeSafe AI's Jev decision model through a web console, batch tools, decision flows, and an API. The text covers specific use cases such as content moderation, spam filtering, support ticket triage, routing, sentiment analysis, and prompt injection screening. The homepage details concrete pricing tiers ranging from a free tier with 100,000 tokens to one-time purchase packs priced at $4.90, $9.90, $19.90, and $49. Additionally, the provided llms.txt file outlines the request shape for the API endpoint POST /api/v1/systemone, sample JSON payloads, available guides, and links to external GitHub repositories. The JSON-LD blocks provide structured Organization, WebSite, SoftwareApplication, and FAQPage data. All necessary details regarding what is offered, pricing, API usage, and operational limits are fully present as text across the homepage, llms.txt, and JSON-LD inputs.

Good for Bots report

JevModel scores 79 of 100: 48 of the 50 base points, 31 of the 50 agent-layer points, no penalties.

Earned

48 of the 50 base points above the line, 31 of the 50 agent-layer points below it.

79

Still open

Behind the checks below, with prompts in Pro.

3
Penalties0
How scoring works · current methodology →

For the owner of jevmodel.app

3 prompts, 18 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

47.9 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Passes.

8.3 of 8.3 points.

3 of 4 pages read pass. The page at /guides publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

202 of 202 assessed homepage navigation links expose usable destinations.

Half passes.

2.1 of 4.2 points.

272 of 273 assessed homepage links and buttons have a nonempty accessible name.

Prompt in Pro →
Passes.

2.5 of 2.5 points.

1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

279 of 279 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

31.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 137 links across 2 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 93% of links.

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (at least 64 KB).

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1764 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 645 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Detected
A sign-in or sign-up link
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://jevmodel.app/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://jevmodel.app/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://jevmodel.app/

    https://jevmodel.app/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

12th of 57 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 12JevModel · this reportjevmodel.app

The prompts in the owner view would take JevModel to 97, 2nd in its category.

To the prompts →

Category average 63. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
4 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
1.3 MB
Took
16.9 s
Homepage
645 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /guides/what-is-jevarticle · linked from the homepage · from the sitemap · read
  • /guidescollection · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read

More like JevModel:Developer Tools & APIsAI & Machine LearningDevelopersFreemium

Same category

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

Same category

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Also AI & Machine Learning

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also Developers

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Developers

brivoy.com

Community site where makers launch new products and early adopters discover them

Also Good

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Do you run jevmodel.app? Open the owner view → Removing the listing is free. Remove →