Is instapect.com AI agent ready? D · 36/100
Why we think this is Lovable (1 signals)
- · 'lovable' string in JS bundle
7 failed out of 13 that apply to your site.
Fix automatically with AIScan
7 open checks (7 failing) can be handed to an AI agent: D3, C1, C2, B2, P1, P4, E2. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://instapect.com/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://instapect.com/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Finstapect.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://instapect.com/. Individual checks that need a specific probe list it in their own guide.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- 02Fail+6 pts if fixed
/llms.txt
See full detailsPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- 03Fail+5 pts if fixed
Explicit AI bot rules
See full detailsAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
You are helping me raise my AIScan.site agent-readiness score. Site: https://instapect.com/ Platform: lovable (50% confidence) AIScan score: 36/100 — Level 2 (Readable) Rubric: v2026.08.2 Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan. ### Failing checks - **[C1] Markdown content negotiation** — FAIL - Evidence: no response - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[C2] /llms.txt** — FAIL - Evidence: HTTP 404 - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links. - **[B2] Explicit AI bot rules** — FAIL - Evidence: 0 known AI agent(s) addressed in robots.txt - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc. - **[P1] API Catalog (RFC 9727)** — FAIL - Evidence: 404 at /.well-known/api-catalog - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions. - **[P4] OAuth discovery metadata** — FAIL - Evidence: auth-server: 404, protected-resource: 404 - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints. - **[D3] Link header for discovery** — FAIL - Evidence: no Link header or <link> tag - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag. - **[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. ### Constraints - Do not change visible UI or copy. - Keep changes additive and reversible. - Prefer static files in `public/` over server routes when possible. - For `llms.txt`, generate a real index of the site's most important pages.
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 Lovable — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (5): B1, B3, P2, 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
86Can agents find your pages? robots, sitemaps, llms.txt.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D3
What we foundno Link header or <link> tag
Measured againstHow to fix itAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
Example
Link: </.well-known/api-catalog>; rel="api-catalog"
Content
36Can 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 · C1
What we foundno response
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Serve text/markdown on Accept negotiation
When a client sends
Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel.mdfiles (e.g./about→/about.md) and rewrite based on the Accept header.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
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 foundHTTP 404
Measured againstHow to fix itPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.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
Bot Access
0Are AI crawlers explicitly allowed or blocked?
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found0 known AI agent(s) addressed in robots.txt
Measured againstHow to fix itAdd explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Add explicit User-agent blocks
Don't rely on
User-agent: *alone. Address each major AI crawler so your policy is unambiguous.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
Capabilities
0Can agents do things? APIs, auth, MCP, Agent Skills.
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P1
What we found404 at /.well-known/api-catalog
Measured againstHow to fix itPublish /.well-known/api-catalog linking to your OpenAPI descriptions.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Publish an API catalog (RFC 9727)
# Add to your homepage HTTP response headers Link: </.well-known/api-catalog>; rel="api-catalog" # And serve a JSON document at /.well-known/api-catalog: { "links": [ { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" } ] }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 foundauth-server: 404, protected-resource: 404
Measured againstHow to fix itPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.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 foundno /openapi.json, /api/openapi.json or swagger document found
Measured againstHow to fix itPublish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.
This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like
robots.txt,llms.txt, and.well-known/*belong in thepublic/folder — they're served from the site root automatically.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-catalogas aservice-desclink and from aLinkresponse 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.
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of instapect.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Finstapect.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade D (36/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=36&grade=D&host=instapect.com" alt="AIScan.site Grade D — 36/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Finstapect.com%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.