In May 2026 provincial cyberspace administrations continued to publish filing and registration notices under the Interim Measures for the Administration of Generative Artificial Intelligence Services. According to public information, the Guangdong Cyberspace Administration announced on 11 May that six generative AI services had completed registration, and on 18 May that one had completed filing; Jiangsu, Zhejiang and other provinces also released new batches, including vertical video models and spatial-intelligence models.

Filing and registration: two routes, two judgements

Providing generative AI services to the domestic public triggers a filing duty. This is the baseline requirement set by the Interim Measures, and it applies to model developers that build and serve models themselves.

A parallel route is registration. Applications or features that directly call on the capability of an already-filed model through APIs or otherwise, and provide generative AI services externally, are registered with the local cyberspace administration. The distinction lies not in technical difficulty but in a substantive judgement: whether generative capability is being provided. A common error is to treat an application that connects to a third-party model as needing no formality at all, or to treat a fine-tuned service as still mere “calling”. The assessment criteria are set out in large model filing versus registration.

Two trends stand out from the May notices. First, vertical models are growing in number. Models in vertical fields such as video generation and spatial intelligence are entering the filing sequence, showing that filing has extended from general foundation models to industry models — an industry setting does not exempt a model from filing. Second, API-based applications are growing. Many applications that provide services through APIs on top of already-filed models have completed registration, and registration is becoming a routine compliance step at the application layer.

For companies, the implication is that whether you build or call, you should decide the filing-versus-registration route before launch rather than wait for a regulator’s prompt.

Materials and process

Filing and registration have different material checklists. Filing usually involves entity qualifications, algorithm and model descriptions, security assessment, corpus sources, content labelling and a safety-management system; registration is simpler but still requires describing the model called, the service form and safety measures. The completeness of materials directly affects how quickly an application is accepted; a working checklist is set out in generative AI filing materials.

Note that generative AI service filing and algorithm filing are two separate mechanisms. Algorithm filing rests on the rules on algorithm recommendation and has a broader scope; generative AI filing is a dedicated requirement for generative services, and the two cannot substitute for each other — see the complete guide to algorithm filing. Where a service also involves deep-synthesis content, the deep-synthesis filing rules apply as well.

Self-check actions for companies

First, go through the service list item by item and decide whether each is a filing, a registration, or neither. Second, confirm the filing status and authorisation chain of the models you call. Third, check that content labelling, user terms and complaint channels are in place. Fourth, build the cadence of local batch announcements into your launch schedule, avoiding “launch first, paperwork later”.

For support on filing-versus-registration assessment, material preparation and process liaison, see our Algorithm Filing service.

This article is based on publicly released generative AI service filing and registration notices from provincial cyberspace administrations in May 2026. It is for reference only and does not constitute legal advice.