Documentation / 7.5.1

Complete plugin endpoint reference

Generated inventory of Cybermaps publications, robots.txt, sitemap families, REST routes, and agent authorization.

Cybermaps 7.5.1 supports 64 routes and route families in this inventory. It includes aliases, /robots.txt, sitemap families, REST routes, IndexNow key verification, and the agent authorization page. Concrete URLs vary with enabled features, languages, content, pagination, and configured sitemap slugs. Routes may require authentication or return an unavailable response when disabled.

WordPress admin screens, AJAX/admin-post actions, static assets, and legacy redirects are outside this count. Filename and query-form Markdown alternates are variants of the permalink Markdown family.

Routes

Path / route familyFormatAvailabilityStatic mode
/.well-known/agent-skills/cybermaps-site-guide/SKILL.mdtext/markdownPublication Hub and publication configurationwell_known
/.well-known/agent-skills/index.jsonapplication/jsonPublication Hub and publication configurationwell_known
/.well-known/ai-catalog.jsonapplication/jsonenable_discovery_hubwell_known
/.well-known/api-catalogapplication/linkset+jsonPublication Hub and publication configurationwell_known
/.well-known/mcp/server-card.jsonapplication/mcp-server-card+jsonPublication Hub and publication configurationwell_known
/.well-known/oauth-authorization-serverapplication/jsonPublication Hub and publication configurationwell_known
/.well-known/oauth-protected-resourceapplication/jsonPublication Hub and publication configurationwell_known
/ai-actions.jsonapplication/ld+jsonPublication Hub and publication configurationwell_known
/ai-catalog.jsonapplication/jsonenable_discovery_hubdynamic
/ai-discoveryapplication/jsonPublication Hub and publication configurationwell_known
/ai-discovery.jsonapplication/jsonPublication Hub and publication configurationdynamic
/ai-sitemap.xmlapplication/xmlPublication Hub and publication configurationall
/ai-usage.jsonapplication/jsonPublication Hub and publication configurationwell_known
/ai.jsonapplication/jsonPublication Hub and publication configurationwell_known
/api-catalogapplication/linkset+jsonPublication Hub and publication configurationdynamic
/auth.mdtext/markdownPublication Hub and publication configurationdynamic
/cybermaps-agent-authtext/htmlMCP user-claimed registration and WordPress logindynamic
/cybermaps-openapi.jsonapplication/vnd.oai.openapi+jsonPublication Hub and publication configurationdynamic
/discovery/chunks/{post_id}.jsonapplication/jsonenable_rag_chunksall
/feed.jsonapplication/feed+jsonPublication Hub and publication configurationdynamic
/knowledge-graph.jsonapplication/ld+jsonPublication Hub and publication configurationall
/llms-full.txttext/markdownenable_llms_fullall
/llms-tldr.txttext/plainenable_llms_tldrall
/llms.txttext/markdownPublication Hub and publication configurationall
/news/archive.jsonlapplication/x-ndjsonPublication Hub and publication configurationall
/news/changelog.jsonapplication/jsonPublication Hub and publication configurationall
/news/llms.txttext/markdownPublication Hub and publication configurationall
/news/speakable.jsonapplication/ld+jsonPublication Hub and publication configurationall
/robots.txttext/plainWordPress virtual route; physical robots.txt takes precedencedynamic
/sitemap-archives-{page}.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-authors-{page}.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-misc.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-network.xmlapplication/xmlEnabled sitemap/provider; network index requires multisitedynamic
/sitemap-news.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-posts-{post_type}-{page}.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-rss.xmlapplication/rss+xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap-taxonomies-{taxonomy}-{page}.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/sitemap.xmlapplication/xmlEnabled sitemap/provider; network index requires multisiteall (single site only)
/skill.mdtext/markdownPublication Hub and publication configurationdynamic
/updates.jsonapplication/jsonPublication Hub and publication configurationall
/wp-json/cybermaps/v1/audit-latestapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/audit-runapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/discoveryapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/editor/translation/{post_id}application/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/healthapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/llms-tldrapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/mcpapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/mcp/server-cardapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/authorization-serverapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/authorizeapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/clientsapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/device-authorizationapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/protected-resourceapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/revokeapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/oauth/tokenapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/purgeapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/searchapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/statusapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/wp-json/cybermaps/v1/urlsapplication/jsonRoute-specific enablement and permissions; see MCP/REST documentationdynamic
/{key}.txttext/plainIndexNow enabled; the site key is generated when neededdynamic
/{language}/llms-full.txttext/markdownenable_llms_fullall
/{language}/llms-tldr.txttext/plainenable_llms_tldrall
/{language}/llms.txttext/markdownenable_multilingual_huball
/{permalink}/index.mdtext/markdownPublication Hub and publication configurationdynamic

dynamic means Cybermaps does not materialize that route as a static file. Other values identify eligible Static File Engine modes; actual publication also depends on feature settings, ownership, protocol requirements, and a single-site installation. /robots.txt uses WordPress’s virtual route, so a physical file served by the web server takes precedence.

This table is generated from the imported plugin release. See the public data and the tagged source.