7 open checks (4 failing) can be handed to an AI agent: C2, B3, P2, P4, E1, E2, E4. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)

npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://inneedcloud.com/”.

Option B — Claude Code (CLAUDE.md)

curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client

https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://inneedcloud.com/" }.

Option D — REST API

curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Finneedcloud.com%2F'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://inneedcloud.com/. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

01Fail
/llms.txt
+6 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details
02Fail
OAuth discovery metadata
+4 pts if fixed
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
See full details
03Fail
Correct 404 handling
+4 pts if fixed
Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
See full details

Hand-off prompt for your coding agent7 issues

# Agent-readiness remediation brief

Site: https://inneedcloud.com/
Platform: sveltekit (99% confidence)
AIScan score: 63/100 — Level 3 (Governed)
Rubric: v2026.08.2

## Failing checks (sorted by weight)
- **[C2] /llms.txt** — FAIL
  - Evidence: no response
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[P2] MCP Server Card** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: n/a, protected-resource: 200
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-onpslh → HTTP 200 (soft 404 — returns 200 for a missing page), 351608 bytes, text/html
  - Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
- **[E4] HTTPS & canonical host** — PARTIAL
  - Evidence: final origin https://inneedcloud.com · http:// upgrades to https · www.inneedcloud.com serves its own copy (duplicate origin) · no HSTS header
  - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL.
- **[B3] Web Bot Auth key directory** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory.
- **[E2] Machine-readable API description** — FAIL
  - Evidence: no /openapi.json, /api/openapi.json or swagger document found
  - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

## General guidance
- Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards.
- Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`.
- Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot).
- Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first.
- Re-scan at aiscan.site after deploying.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a SvelteKit — so checks that don't apply never drag you down.

Essential

26 / 31 pts

Baseline every site should meet.

Recommended

15 / 28 pts

Strong signals most sites benefit from.

Bonus earned

3 signals

Emerging standards. Can only add points.

Not counted (2): P3, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

Can agents find your pages? robots, sitemaps, llms.txt.

311

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E1
What we found
GET /aiscan-404-probe-onpslh → HTTP 200 (soft 404 — returns 200 for a missing page), 351608 bytes, text/html
Measured against
RFC 9110 §15.5.5 — 404 Not Found Google Search Central — soft 404s
How to fix it
Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover.
Return a real 404 status
A missing page must answer 404 (or 410), never 200. A soft 404 makes agents index your error page as real content.
Make the body recoverable
The 404 body should name the site and link to the homepage, sitemap, docs, and search so an agent can find its way back instead of dead-ending.
Verify
curl -sI https://yoursite.com/this-page-does-not-exist-123 | head -n 1
Fix in ChatGPT Fix in Claude

Content

Can agents read your content cleanly? Markdown, structured data.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C2
What we found
no response
Measured against
llms.txt proposal
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
Generate it free
Use the AIScan llms.txt Generator to create a standards-shaped starting file from your site details, then publish it at /llms.txt.
Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then ## sections of markdown links.
Template
# Example Co > One-line summary of what this site / product does. A short paragraph explaining the audience, what's here, and how to navigate it. ## Docs - [Getting started](/docs/quickstart): install, first call in 5 min - [API reference](/docs/api): all endpoints, params, examples ## Pages - [Pricing](/pricing): plans and limits - [Changelog](/changelog): recent releases ## Optional - [Brand assets](/press): logos and screenshots
Fix in ChatGPT Fix in Claude

Bot Access

Are AI crawlers explicitly allowed or blocked?

Capabilities

Can agents do things? APIs, auth, MCP, Agent Skills.

112

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we found
auth-server: n/a, protected-resource: 200
Measured against
RFC 9728 — OAuth 2.0 Protected Resource Metadata RFC 8414 — OAuth 2.0 Authorization Server Metadata
How to fix it
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at /.well-known/oauth-authorization-server and/or RFC 9728 at /.well-known/oauth-protected-resource.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E2
What we found
no /openapi.json, /api/openapi.json or swagger document found
Measured against
OpenAPI Specification 3.1 RFC 9727 — `service-desc` link relation
How to fix it
Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.
Publish an OpenAPI 3.1 description
Serve it at /openapi.json (or /openapi.yaml). Describe every public endpoint, its parameters, and its response schema.
Advertise it
Reference it from /.well-known/api-catalog as a service-desc link and from a Link response header.
Link: </openapi.json>; rel="service-desc"; type="application/json"
Content sites can skip this
If you expose no programmatic API, this check is informational and costs you nothing.
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of inneedcloud.com on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Finneedcloud.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (63/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=63&grade=C&host=inneedcloud.com" alt="AIScan.site Grade C — 63/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade C — 63/100](https://aiscan.site/api/public/badge.svg?score=63&grade=C&host=inneedcloud.com)](https://aiscan.site/?u=https%3A%2F%2Finneedcloud.com%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Dig deeper

Scan any site from Telegram

Send a URL to @AISiteScanBot and get an instant AI-readiness score + top fixes.

Open in Telegram

Automate your AI-readiness

Plug AIScan into your agent stack or chat with it on the go.

Use the MCP server

One line in Claude Code or Cursor to scan any site from your agent.

Chat with the Telegram bot

Scan sites and get fixes right from @AISiteScanBot.

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Re-test this site Scan your site

Or browse the community feed to see what others have scanned.

Is inneedcloud.com AI agent ready? C · 63/100

inneedcloud.com

Fix automatically with AIScan

Quick Wins

/llms.txt

OAuth discovery metadata

Correct 404 handling

How this score is calculated

robots.txt present & sane

XML sitemap

Link header for discovery

Correct 404 handling

Return a real 404 status

Make the body recoverable

Verify

HTTPS & canonical host

Markdown content negotiation

/llms.txt

Generate it free

Create /llms.txt at the site root

Template

Structured HTML (title, meta, JSON-LD, single H1)

Heading hierarchy & server-rendered text

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Publish OAuth discovery metadata

Machine-readable API description

Publish an OpenAPI 3.1 description

Advertise it

Content sites can skip this

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Dig deeper

Automate your AI-readiness

Scan your own site