AIScan.site

Is icancall.co AI agent ready? C · 59/100

Re-test this site

icancall.co

Next.js · 60% confidence
https://www.icancall.co/coming-soon
C59 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability
81Content
91Bot Access
100Capabilities
0Commerce
—
Why we think this is Next.js (2 signals)
  • · hosted on Vercel
  • · /_next/static/ asset

Scan history · 6 public scans of icancall.co

WhenScoreGradeSnapshot
4 Sept 2026, 14:01 UTCe946d3b159/100CView →
2 Sept 2026, 21:23 UTC4e72fe4159/100CView →
4 Jul 2026, 2:12 UTC0f3a597467/100BView →
4 Jul 2026, 1:24 UTC69d9d28868/100BView →
3 Jul 2026, 19:29 UTCdab2b36665/100BView →
3 Jul 2026, 19:29 UTCcff4ea1c65/100BView →
6 checks need fixing

4 failed · 2 partial out of 13 that apply to your site.

See top fixes

Fix automatically with AIScan

6 open checks (4 failing) can be handed to an AI agent: C3, P1, P4, E1, E2, E3. 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://www.icancall.co/coming-soon”.

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://www.icancall.co/coming-soon" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fwww.icancall.co%2Fcoming-soon'

Returns every check with its complete fix guide.

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

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    API Catalog (RFC 9727)

    +4 pts if fixed

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    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 agent6 issues
# Agent-readiness remediation brief

Site: https://www.icancall.co/coming-soon
Platform: nextjs (60% confidence)
AIScan score: 59/100 — Level 3 (Governed)
Rubric: v2026.08.2

## Failing checks (sorted by weight)
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 1, title: true, meta description: true, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[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.
- **[E1] Correct 404 handling** — FAIL
  - Evidence: GET /aiscan-404-probe-uye3nl → HTTP 200 (soft 404 — returns 200 for a missing page), 34835 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.
- **[E3] Heading hierarchy & server-rendered text** — PARTIAL
  - Evidence: 383 words of server-rendered text, 1 <h2>, 4 <h3>
  - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
- **[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 Next.js — so checks that don't apply never drag you down.

Essential
25 / 31 pts

Baseline every site should meet.

Recommended
17 / 28 pts

Strong signals most sites benefit from.

Bonus earned
0 signals

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

81

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

41

  • 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-uye3nl → HTTP 200 (soft 404 — returns 200 for a missing page), 34835 bytes, text/html

    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

91

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

22

Bot Access

100

Are AI crawlers explicitly allowed or blocked?

1

Capabilities

0

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

3

  • 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 found

    404 at /.well-known/api-catalog

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    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" }
  ]
}
    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 · P4

    What we found

    auth-server: 404, protected-resource: 404

    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

    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
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — www.icancall.co graded C
Post on X Share on LinkedIn Share on Facebook

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.

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 www.icancall.co on AIScan.site.

AIScan.site grade C
HTML
<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fwww.icancall.co%2Fcoming-soon" target="_blank" rel="noopener" title="Agent-Readiness Grade C (59/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=59&grade=C&host=www.icancall.co" alt="AIScan.site Grade C — 59/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade C — 59/100](https://aiscan.site/api/public/badge.svg?score=59&grade=C&host=www.icancall.co)](https://aiscan.site/?u=https%3A%2F%2Fwww.icancall.co%2Fcoming-soon)

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Sign up free Already have an account? Sign in →

Dig deeper

Scan any site from Telegram
Open in Telegram

icancall.co is built on Next.js. AI-agent readiness for Next.js walks through the same checks on that platform.

Scan any site from Telegram
Open in Telegram

This page always shows the most recent public scan for icancall.co.

Browse all public scansScan your site