SuperAPI AI Directory

linkfox-multimodal-recognize-image

Data & analytics

View repository

Updated 10-16 00:00

About this skill

Image Recognition

This skill guides you on how to use the multimodal image recognition API to analyze images from URLs and extract meaningful information based on user intent.

Core Concepts

The Image Recognition tool accepts an image URL and an optional natural-language requirement describing what the user wants to know about the image. The backend uses a multimodal AI model to interpret the visual content and return a textual description or analysis.

Supported formats: JPG, JPEG, PNG, GIF, WebP, BMP.

How it works: You provide a publicly accessible image URL and a requirement (what you want to learn from the image). The service downloads the image, runs multimodal analysis, and returns a text-based result.

Parameter Guide

Parameter Required Description
imageUrl Yes A publicly accessible URL pointing to the image. Must be JPG, JPEG, PNG, GIF, WebP, or BMP. Maximum 1000 characters.
requirement No A natural-language description of what to identify or analyze in the image. Defaults to "Describe the content of this image" when omitted. Maximum 1000 characters.

Tips for Writing the requirement Parameter

  1. Be specific: Instead of "analyze this image", say "List all products visible on the shelf and estimate their category."
  2. State the goal: If you need text extraction, say "Extract all visible text from the image." If you need object identification, say "Identify the main objects and their colors."
  3. Provide context when helpful: For product images, mention "This is an e-commerce product listing image" so the model can tailor its analysis.

Local Image Upload

This tool requires a publicly accessible image URL. If the user provides a local image file path (e.g., C:\Users\...\photo.png, /home/.../image.jpg), you must upload it first to obtain a public URL.

Run the upload script:

python scripts/upload_image.py /path/to/local/image.png

The script will return a public URL (valid for 24 hours) that can be used as the image URL parameter.

Usage Examples

1. General Image Description

  • User says: "What is in this picture?"
  • Set imageUrl to the provided URL, leave requirement as default.

2. Product Image Analysis

  • User says: "Analyze this Amazon product image and list the key selling points shown."
  • Set requirement to: "This is an Amazon product listing image. Identify the product, key features, and selling points visible in the image."

3. Text Extraction from an Image

  • User says: "Read the text in this screenshot."
  • Set requirement to: "Extract all visible text from this image, preserving layout where possible."

4. A+ Page Image Review

  • User says: "Describe what this A+ content image communicates."
  • Set requirement to: "This is an Amazon A+ product description image. Describe the visual content, key messaging, and branding elements."

5. Comparison / Detail Inspection

  • User says: "What differences can you spot between the product and its packaging?"
  • Set requirement to: "Identify and describe any differences between the product and its packaging shown in the image."

How to call

  • API endpoint:POST /multimodal/recognizeImage(for full parameters/responses/error codes, see references/api.md)
  • Python script:python scripts/multimodal_recognize_image.py '<JSON 参数>' [--inline]
  • Cost constraints: This tool consumes compute; by default, the same parameter combination in the same session is called only once, and the script has a 24h local cache. On failure/empty results, do not automatically switch keywords, paginate, or change the postal code to probe continuously; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (script default behavior):

  • Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-multimodal-recognize-image-<timestamp>.json(<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user's task;writing to /tmp is prohibited, and if the current directory is not writable, an error is reported)
  • Response body ≤ 8 KB: after writing to disk, print the full JSON to stdout
  • Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, the length of the largest list field + the first 3 samples)
  • Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: first look at the summary to determine whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding the entire JSON entering the context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

  • API Key not configured: the environment variable is not configured LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Display Rules

  1. Show the analysis result clearly: Present the returned text analysis in a readable format. Use bullet points or paragraphs as appropriate for the content.
  2. No fabrication: Only relay information that the API actually returned. Do not add visual details that were not in the response.
  3. Format support: If the image URL is invalid or the format is unsupported, explain the limitation and list the supported formats (JPG, JPEG, PNG, GIF, WebP, BMP).
  4. Error handling: When the API returns an error status, explain the issue based on the response and suggest corrective actions (e.g., check that the URL is publicly accessible, verify the image format).
  5. Token usage: If the user asks about cost, you may mention the costToken value from the response.

User Expression & Scenario Quick Reference

Applicable -- Image analysis tasks:

User Says Scenario
"What's in this image/picture/photo" General image description
"Analyze this product image" Product visual analysis
"Read the text in this image" OCR / text extraction
"Describe the A+ page images" E-commerce content review
"What does this screenshot show" Screenshot interpretation
"Identify objects in this photo" Object detection / listing

Not applicable -- Needs beyond image recognition: ``

  • Generating or editing images
  • Video analysis
  • Analyzing images from local file paths (only URLs are supported)
  • Image search or reverse image lookup

Compute consumption rules

Billed according to dynamic rules: compute consumed = compute consumed by input + compute consumed by output results.

Important: the service of this skill is dynamically calculated by a multiplier and may consume a large amount of compute at once. The user must be reminded, and the user decides whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.


For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.