visibility

capability

minimax.io

✓ verified

AI Visibility: ✓ check completed — level L5

AI Capability: ✓ check completed — level L3

L1 Basic Accessibility 6/6

✓ Major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are permitted to access your site. AI crawling allowed

✓ Main content is visible in the HTML source, not only rendered after JavaScript executes. Page content directly readable

✓ The page has a clear title and meta description, helping AI quickly identify the topic. Clear title and description

✓ The page responds quickly enough to avoid AI crawl failures or timeouts. Reasonable response time

✓ The site uses a valid HTTPS certificate. HTTPS secured

✓ Core content isn't blocked by login walls, membership gates, or paywalls. Content is not gated

L2 Content Comprehensibility 6/6

✓ Uses Schema.org / JSON-LD to help AI understand page content more accurately. Has structured data

✓ Open Graph tags provide supplementary title and summary information. Has social sharing info

✓ A canonical URL tells search engines and AI which version of the URL is authoritative. Clear canonical address

✓ The page has a clear H1 and uses H2/H3 headings to organize content logically. Clear heading hierarchy

✓ The HTML lang attribute is set, helping AI identify the page language. Language declared correctly

✓ The page has meaningful text content, not just a few sentences of boilerplate. Substantial content

L3 Discoverability 5/6

✓ An accessible XML sitemap helps AI and search engines discover your pages. Provides a sitemap

✓ The sitemap includes recent pages and isn't neglected over time. Sitemap stays updated

✓ Key content pages are easily reachable from the homepage and main pages. Clear internal linking

✓ Page URLs clearly reflect the content topic, rather than being cryptic parameter strings. Clean, readable URLs

✗ A /llms.txt file proactively tells LLMs which content is most worth paying attention to. Provides llms.txt

✓ The canonical tag points to the current page's standard address, avoiding duplicate page confusion. Consistent canonical setup

L4 Trust & Authority 5/6

✓ Structured data includes basic info like company/organization name, website, and logo. Organization info is clear

✓ Both users and AI can easily find your contact or about page. About and contact info visible

✓ Pages attribute content to an author, team, or organization. Content source is clear

✓ Pages include publish or update dates, helping assess content freshness. Publication dates are clear

✓ The site has essential pages like privacy policy and terms of service. Legal info is complete

✗ Basic security response headers are set, reflecting site maintenance quality. Proper security configuration

L5 AI-Optimized 5/6

✓ Page content is structured for AI to directly extract answers. Has FAQ / HowTo / Q&A structure

✓ Helps AI understand the page's position and hierarchy within the site. Has breadcrumb structure

✓ Products, services, or content include structured Review/Rating data. Has review information

✓ Multilingual pages have clear corresponding relationships, such as hreflang tags. Supports multiple languages

✓ Uses multiple effective Schema.org types, not just one. Richer structured data

✗ Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Clear content block structure

L1 Basic Accessibility 6/6

✓ Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. Semantic HTML

✓ Includes essential metadata such as page title, description, and social sharing tags to improve machine interpretation. Metadata

✓ Provides JSON-LD structured data based on Schema.org to make entities and page meaning more explicit. Structured Data

✓ Public content is accessible without CAPTCHA or other anti-bot challenges that block legitimate automated access. No CAPTCHA Barriers

✓ Core content is present in the initial HTML response, rather than relying entirely on client-side JavaScript rendering. Server-Rendered Content

✓ Uses stable, human-readable URLs without excessive query parameters, session tokens, or hash-fragment routing. Clean URLs

L2 Discoverability 4/6

✓ Provides a robots.txt file that permits access for legitimate crawlers and agent systems where appropriate. robots.txt

✓ Publishes a valid XML sitemap to help agents and crawlers discover indexable pages efficiently. XML Sitemap

✗ Exposes a /llms.txt file that gives LLM-based systems guidance on important content and site structure. llms.txt

✗ Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. OpenAPI Specification

✓ Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. Machine-Readable Documentation

✓ Ensures primary content is available as text, rather than being locked inside images, videos, or non-parsable PDFs. Text-Accessible Content

L3 Structured Interaction 4/6

✓ Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. Structured API

✓ Returns JSON payloads with stable and predictable schemas across endpoints. Consistent JSON Responses

✓ Supports query parameters for search, filtering, pagination, and retrieval refinement. Search and Filtering Support

✗ Provides an agent descriptor, such as an A2A agent card at /.well-known/agent.json, to advertise agent capabilities. A2A Agent Card

✓ Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. Documented Rate Limits

✗ Returns machine-readable error responses with clear codes, messages, and actionable context. Structured Error Handling

L4 Agent Integration 3/6

✓ Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. MCP Server

✗ Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. WebMCP Support

✓ Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. Write-Capable API

✓ Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. Agent-Friendly Authentication

✗ Supports webhooks so agents can receive event-driven updates instead of relying only on polling. Webhooks

✗ Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. Idempotent Writes

L5 Autonomous Operation 3/6

✓ Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. Event Streaming

✗ Supports agent-to-agent capability discovery or negotiation so systems can adapt to each other dynamically. Capability Negotiation

✓ Provides APIs for subscription, lifecycle management, or registration of agent integrations. Subscription and Management API

✓ Supports multi-step workflows, task coordination, and stateful execution across actions or services. Workflow Orchestration

✗ Can proactively notify agents when relevant content, state, or business events change. Proactive Notifications

✗ Supports handoff between agents or services so tasks can continue across system boundaries. Cross-Service Handoff

AI Readiness Report

download .md

Executive Summary

Minimax.io demonstrates excellent AI discoverability, making it highly likely to be found and recommended by AI systems. However, its readiness for direct, autonomous AI agent interaction is moderate, with significant gaps in agent integration and operational features.

AI Visibility — L5

The site is exceptionally well-optimized for AI discovery, with strong foundational SEO, clear content structure, and robust trust signals. It is highly likely to be surfaced and recommended by AI assistants like ChatGPT and Perplexity, though it lacks a dedicated /llms.txt file to guide AI attention.

AI Capability — L3

While the site provides a solid API foundation with documentation and authentication, it lacks key agent-oriented features like an OpenAPI spec, structured error handling, and webhooks. This limits the ability of AI agents to reliably discover, integrate with, and operate on the site's services.

The high visibility score means AI systems can easily find and understand the site. The moderate capability score means AI agents can perform basic tasks but cannot fully automate complex workflows or integrate seamlessly without developer intervention.

Top Issues

HIGH Missing LLMs.txt File for AI Guidance visibility · L3 · developer

Why: An llms.txt file acts as a sitemap for AI systems, directing them to your most important content and pages. Without it, AI crawlers may miss or deprioritize key information.

Impact: Reduces the likelihood of your content being accurately discovered, summarized, and recommended by AI assistants, potentially decreasing referral traffic and brand authority in AI-generated answers.

Fix: Create a plain text file at the root domain (https://minimax.io/llms.txt). Structure it with clear directives, such as 'Allow:' for important pages, 'Disallow:' for irrelevant ones, and 'Sitemap:' links. Include a priority list of key pages, product names, and core concepts.

HIGH Missing Basic Security Headers visibility · L4 · devops

Why: Security headers (like Content-Security-Policy, X-Frame-Options) are a signal of site maintenance and trustworthiness. AI systems may be less likely to trust or recommend content from sites that appear insecure.

Impact: Undermines perceived site quality and authority, which can negatively influence AI systems' willingness to cite your content, potentially affecting trust and user safety.

Fix: Audit current headers using a tool like securityheaders.com. Configure the web server (e.g., Nginx, Apache) or application framework to include headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

HIGH Missing Programmatic AI Guidance File capability · L2 · developer

Why: This is the capability counterpart to the visibility llms.txt. It provides structured, machine-readable guidance for LLM-based agents, helping them navigate and interact with your site more effectively.

Impact: Limits the ability of advanced AI agents and tools to understand your site's purpose and structure, reducing the quality of automated interactions and potential integration opportunities.

Fix: Implement the same /llms.txt file as for visibility, but ensure its content is structured for programmatic consumption. Consider using a simple key-value or YAML-like format to define site sections, primary purposes, and interaction hints.

HIGH No OpenAPI Specification Published capability · L2 · developer

Why: An OpenAPI (Swagger) spec is the standard way for AI agents to discover, understand, and interact with your API endpoints autonomously. Without it, agents cannot reliably use your API.

Impact: Blocks AI agents from automating tasks via your API, such as data retrieval or triggering actions. This limits your service's integration into AI-driven workflows and reduces its utility for power users and developers.

Fix: Generate an OpenAPI specification for your existing API endpoints. Use a library in your framework (e.g., Swagger for Node.js, drf-yasg for Django) to auto-generate the spec. Host the JSON/YAML file at a public, documented URL (e.g., /api/docs).

MEDIUM Lack of AI-Optimized Structured Content visibility · L5 · content

Why: AI systems excel at extracting information from clearly structured content like FAQs, tables, and lists. Dense paragraphs without semantic markup are harder to parse accurately.

Impact: Makes it difficult for AI to summarize your content correctly or pull out key facts, leading to less accurate citations, missed details in AI answers, and a poorer user experience for those relying on AI summaries.

Fix: Audit key product and documentation pages. Refactor long text walls into structured elements: use proper HTML tags for definition lists (<dl>), tables (<table>), and ordered/unordered lists. Introduce clear FAQ sections with <details>/<summary> tags or heading hierarchies.

Quick Wins

⚡

Missing LLMs.txt File for AI Guidance — Create a plain text file at the root domain (https://minimax.io/llms.txt). Structure it with clear directives, such as 'Allow:' for important pages, 'Disallow:' for irrelevant ones, and 'Sitemap:' links. Include a priority list of key pages, product names, and core concepts. (developer)

⚡

Missing Programmatic AI Guidance File — Implement the same /llms.txt file as for visibility, but ensure its content is structured for programmatic consumption. Consider using a simple key-value or YAML-like format to define site sections, primary purposes, and interaction hints. (developer)

⚡

No Agent Descriptor File — Create a JSON file at /.well-known/agent.json following the A2A specification or a simple custom schema. Describe the site's purpose, available actions (e.g., 'search products', 'submit form'), and any required authentication patterns. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Create and deploy the /llms.txt file at the root domain with clear 'Allow:', 'Disallow:', and 'Sitemap:' directives, plus a priority list of key pages and concepts.

— Enhance the /llms.txt file content with a simple key-value or YAML-like structure for programmatic consumption, defining site sections and interaction hints.

— Create and deploy the A2A Agent Descriptor file at /.well-known/agent.json describing the site's purpose and available actions.

Visibility L3 → L4, Capability L2 → L3

Week 2: Foundation

— Audit current security headers using a tool like securityheaders.com.

— Configure the web server or application framework to deploy missing security headers: Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.

Visibility L4 → L5

Weeks 3-4: Advanced

— Generate an OpenAPI specification for existing API endpoints using a framework library (e.g., Swagger, drf-yasg) and host it at a public URL like /api/docs.

— Audit key product and documentation pages, then refactor content into structured HTML elements (definition lists, tables, clear lists) and introduce FAQ sections with <details>/<summary> tags.

Capability L3 → L4

The site should reach AI Visibility Level 5/5 and AI Capability Level 4/5, solidifying its foundational AI-readiness and enabling more advanced programmatic interactions.

// embed badge

L5 AI Visibility L3 AI Capability

AI Visibility — markdown:

[![ReadyforAI](https://readyforai.dev/badge/minimax.io)](https://readyforai.dev/websites/minimax.io)

AI Capability — markdown:

[![ReadyforAI](https://readyforai.dev/badge/minimax.io?track=capability)](https://readyforai.dev/websites/minimax.io)

About badges