You can view resource plan usage, bills, and spending details for Visual Intelligence API to understand your spending.
Resource plan usage
Method 1: In the Visual Intelligence API console
The following steps use the General-purpose Image Resource Plan as an example.
-
Log on to the Visual Intelligence API console. In the navigation pane on the left, choose Features > Face and Body.
-
On the General-purpose Image Resource Plan tab, view the usage and remaining quota of your resource plans.
Method 2: In the Billing Management console
Log on to the Billing Management console to view the usage of specific resource plan instances.
For detailed steps, see View Resource Plan Usage.
Viewing the validity period and expiration date
Besides the Visual Intelligence API console, you can also view resource plan validity periods and expiration dates in the following ways:
-
Log on to the Billing Management console and go to Resource Instance Management to view per-instance expiration details.
-
View expiration information in the order details page of the Billing Management console.
Multiple expiration dates
If you purchase a new general-purpose resource plan that overlaps with an existing dedicated resource plan, the console list may display the end date of the longest-running order. This is expected behavior.
SMS quota alerts
When the remaining quota of a resource plan drops to 20%, the system automatically sends you an SMS notification. If the SMS notification does not match the remaining balance shown in the Visual Intelligence API console (for example, when you have multiple resource plans), use the per-instance data in Resource Instance Management of the Billing Management console as the authoritative reference.
API calls
The following steps use 1:1 Face Comparison as an example.
-
Log on to the Visual Intelligence API console. In the navigation pane on the left, choose Features > Face and Body.
-
To the right of 1:1 Face Comparison, click View Details to view the number of API calls, QPS alert information, and QPS threshold.
Troubleshooting: Monitoring data is empty or delayed
If the API call monitoring data appears empty or delayed, follow these troubleshooting steps:
-
Verify that you have selected the correct API category or capability name.
-
Monitoring statistics and resource plan deductions have an hourly processing delay. Wait some time after making API calls before rechecking the data.
-
For specific capabilities such as image super-resolution and product segmentation, you can view usage details directly at the Usage Details page.
Bill details
Log on to the Billing Management console and view the spending details for the Visual Intelligence API on the Billing Overview and Bill Details pages.
For detailed steps, see Billing Overview and Bill Details.
FAQ
Why are there no billing records or deductions in the console after calling the API?
Some Visual Intelligence API (VIAPI) services, such as PDF recognition, use a pay-as-you-go billing model where bills are generated and charges are applied in the month following usage. If you do not see any billing records immediately after calling the API, this is expected behavior. To query historical billing details, go to Bill Management in the Billing Management console.
How do I configure resource plan quota alerts?
Quota alert configuration is managed through the Alibaba Cloud unified Billing Resource Center, not within the Visual Intelligence API console. To configure quota alerts:
-
Go to the Quota Alert Settings page to enable quota alerts for your resource plans.
-
Go to the Message Subscription Center to configure your preferred notification channels, such as SMS or email.
What should I do if there are unexpected API calls and charges?
-
Check asynchronous query calls: Call statistics may include counts for asynchronous query interfaces, such as the general HD segmentation capability. These additional internal calls can cause the total call count to be higher than expected.
-
Identify the source using ActionTrail: Use ActionTrail in the Alibaba Cloud console to query the specific calling IP addresses, accounts, and timestamps to identify the source of unexpected calls.
-
Prevent unintended calls: Disable the corresponding AccessKey in the RAM console, or create a dedicated AccessKey for the service and disable it when not in use. This ensures no API calls are made and no charges are incurred when the service is not actively being used.