Connect MeowID to Zhongdamaopu

This guide starts with a Zhongdamaopu campus-cat application that already has the recognition-service settings page. It covers MeowID setup and mini program operations.

Prepare:

• A MeowID console account with permission to create a project and API key.
• A Level-99 administrator account in the mini program, for service configuration and data sync.
• Existing cat profiles and approved photos to register and use for verification.

People will be able to search for similar cats and open existing profiles from the same mini program. Begin with a small set of cats and clear, single-cat photos before processing a larger photo library.

1. Sign in to the MeowID console and create a project for your campus-cat application.
2. Copy the project ID from its details. You will enter it in the mini program.
3. Check the available balance and current billing rules; top up as needed. Image registration and recognition may consume paid usage.

Keep using the same project for this cat application. Sync creates a corresponding MeowID cat for each local profile; do not manually create every cat first.

Open API Keys, select the same project, and create an integration key. Choose full access, or a custom key with all four scopes below.

A recognition-only key cannot run the complete sync workflow. Save the full key when it is displayed. Enter it in the mini program service configuration below. Never share it publicly or include it in screenshots.

1. Sign in as a Level-99 administrator. Open 关于 → 小程序配置 → 识猫服务 (About → Mini program settings → Recognition service). Lower-level administrators will not see this entry.
2. Select MeowID as the recognition mode and save it.
3. Enter the project ID, API key, and API base URL under service configuration. The default is https://platform.meowid.net; the documentation URL https://meowid.net/developers is not an API endpoint.
4. Keep the candidate count at 5 initially. Save the configuration, then check the connection.

The project ID and API key must belong to the same MeowID project. Saved keys are not displayed again; leave a field blank to keep its current value. A blank key field does not mean the saved key is missing.

The screenshots show a real campus-cat application in Chinese; names and counts will differ in your project. Candidate count controls how many similar cats a search returns. It is separate from the per-cat photo cap in the next step.

Choose a sync mode in the data-sync panel. Both modes sync cat profiles, skip existing submission receipts, and use approved photos without requiring a featured-photo flag.

Start with capped sync if you want to limit historical registration usage. A cat with only three approved photos uploads three; no image is repeated to reach five. A cat with no approved photos can still have its profile synced. Lowering the cap does not delete existing remote images.

Keep the page open while batches continue. Leaving stops new batch requests; an already submitted batch may still run. Click the same sync mode to resume. Keep prior sync records and never force reuploads based only on a difference between platform and local totals.

Synced and remaining cats count local profiles with a remote binding. Uploaded and remaining images count approved photos with platform acceptance records. Each accepted/synced count plus its remaining count equals its total.

Uploaded does not mean registration has completed. The platform still needs to crop images and extract features. Open the project task queue to check:

• queued / running: accepted and waiting or processing.
• completed: the registration task finished; use available registered images to verify recognition.
• waiting_user: confirm the target cat in the MeowID console.
• failed: inspect the error. A failed task with a receipt is not blindly uploaded again.

Remaining images can include capped, failed, and uncertain submissions; not all of them are safe to retry. Local cat bindings can also differ from platform totals that include manually created or older records.

1. Choose a locally linked cat with available registered images and prepare a clear, single-cat photo, ideally a different photo for verification.
2. On the mini program cat directory, tap 识别 (Recognize) next to the search field. Take a photo or choose one from the album.
3. Inspect the similar-cat candidates and open a local profile. Confirm that the name, photos, and profile link are correct.

The mini program displays the local profiles linked to MeowID candidates. Compare names, photos, and distinctive features when reviewing a match.

Similarity ranks candidates; it is not an identity accuracy percentage. No cat detected, identity unknown, and a failed service request are different outcomes. Changing the selected cat in a multi-cat photo issues another recognition request and may incur usage. Begin with a single-cat photo.

With MeowID enabled, approving a new photo directly attempts registration. The manual batch cap does not limit new approval uploads. Reviews can still be saved when another sync batch is active or an upload is incomplete; resume sync later for unsent photos.

• Keep existing sync records and use the appropriate sync button to continue. Do not recreate cat profiles to restart a sync.
• Check uncertain uploads in the MeowID task queue before taking action. Do not immediately submit the image again.
• Avoid adding the same photo as multiple separate records; separate records may still be submitted independently.
• Check project ownership before changing a project or key. Keep using the same MeowID project for the same cat application.

Continue with the API reference or MeowID console walkthrough. When reporting an issue, include the visible message, task ID, and time, but never publish API keys.