# Fixed URL Product Price Change Recorder (`malachite_digit/my-actor`) Actor

Record explicit JSON-LD prices from up to 10 fixed public product URLs. Compare with a previous snapshot and preserve valid prices on failures. $0.01 per successful comparable check. No login, proxy or CAPTCHA bypass.

- **URL**: https://apify.com/malachite_digit/my-actor.md
- **Developed by:** [Kai Yin Ng](https://apify.com/malachite_digit) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 successful price checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Fixed Public Product Price Recorder

Pricing is shown in the Actor Pricing tab, including any scheduled change. When Pay per event pricing is effective, the successful-price-check event costs $0.01 per successful URL check, only after saved output is verified. An error or a non-comparable item makes the whole batch ineligible for this event. Unknown charging outcomes are not automatically resubmitted; this is not a guarantee of cross-process exactly-once charging.

Record explicit structured prices from 1–10 fixed public product URLs and compare them with a previous snapshot. This Actor reads schema.org JSON-LD only. It does not follow product links or guess prices from visible text.

### Input

```json
{"urls":["https://www.staples.com/avery-easy-peel-laser-address-labels-1-x-2-5-8-white-30-labels-sheet-100-sheets-box-5160/product_209882"]}
```

To compare prices, copy the `snapshot` object from the previous OUTPUT and pass it as `previous` alongside the same URL set. History is supplied explicitly; no other user's data or shared history is loaded. For Pay per event runs, set a finite maximum charge that covers the batch: at least $0.01 per URL ($0.10 for ten URLs). This event limit does not represent a hard cap on platform resource costs under every pricing model.

### Output

Open the **Results and snapshot (JSON)** output link. The OUTPUT record contains `results` for this attempt and `snapshot` with the last valid observations. Each successful result includes source URL, explicit product identifiers/name, price/currency, availability, UTC capture time, previous valid price and change type. Shipping, tax, contract price and absent package fields remain unknown.

Change types include first_observation, unchanged, increased, decreased, identity_changed, currency_changed and unavailable. Missing/ambiguous prices, mismatched offers, access failures and unsupported content do not overwrite the previous valid observation or become decreases.

### Supported pages and limits

The page must expose a single unambiguous Product and direct Offer in JSON-LD with explicit product identity, price and currency. Multiple products/offers, variants, aggregate/conditional pricing and inconsistent offer identities are rejected. No browser execution, login, proxies, CAPTCHA solving or access bypass is used. Private/reserved network addresses and unsafe redirects are blocked. Robots restrictions are honored conservatively.

Up to 10 fixed HTTP(S) URLs per run; 15 seconds maximum per URL, 4-second connection/read idle bounds, 1 MiB per response, 3 redirects and no retries. Results can be unavailable when a retailer blocks cloud addresses or omits supported structured data. A historical sample price is not a promise of a current retailer quote.

This Actor uses Limited permissions and stores results only in the current run's default key-value store. No product alerts or purchases are performed. The active pricing and any future effective date appear in the Actor Pricing tab. Under the configured Pay per event model, platform usage is included in the event price. A failed run can still have an OUTPUT record containing diagnostics and the last valid snapshot. Use Report issue on the run to request support; include the Run ID and public source URL, and do not include credentials.

# Actor input Schema

## `urls` (type: `array`):

One to ten fixed public HTTP(S) product URLs. Only explicit structured product prices are recorded; access restrictions are respected.

## `previous` (type: `object`):

仅接受本次同一 URL 集合的显式历史快照。

## Actor input object example

```json
{}
```

# Actor output Schema

## `output` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("malachite_digit/my-actor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("malachite_digit/my-actor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call malachite_digit/my-actor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,malachite_digit/my-actor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UzeKdMzHZL8YAHlgR/builds/abCRKmF4sK3d25Lz8/openapi.json