Same category
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric

Hosted playground, decision flows, batch processing and API for the Jev model
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.
“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.
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
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing at least 200 URLs.
Describes itself to machines with schema.org JSON-LD. 3 of 4 pages read pass. The page at /guides publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 202 of 202 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 272 of 273 assessed homepage links and buttons have a nonempty accessible name. +2.1 with its prompt in Pro.
Form fields have names and recognizable semantics. 1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 279 of 279 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. The homepage has 5 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 137 links across 2 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 93% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (at least 64 KB).
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
48 of the 50 base points above the line, 31 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of jevmodel.app
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
47.9 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing at least 200 URLs.
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.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
2.1 of 4.2 points.
272 of 273 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
279 of 279 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
The homepage has 5 section links, and every one reaches an element on the page.
Agent layer
31.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 137 links across 2 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 93% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (at least 64 KB).
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 1764 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
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.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
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.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://jevmodel.app/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://jevmodel.app/
Declared allow · robots.txt
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
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://jevmodel.app
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://jevmodel.app/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://jevmodel.app/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://jevmodel.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://jevmodel.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://jevmodel.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://jevmodel.app/
In its category
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.
Every scan is kept. Pro draws the history as a chart →
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.
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 →