Track a brand, product or topic across developer communities in one run: Stack Exchange questions, Lemmy posts and Mastodon hashtag activity, merged into one schema with text, direct link, author, community and engagement numbers. Official/open APIs, no key needed.
0.1.15 — 2026-10-08 — README: the Python example works with the current Apify client
The README's Python example read the results with run['defaultDatasetId']. With the current Apify client for Python (version 3) call() returns a run object, not a dict, and that line raised TypeError: 'Run' object is not subscriptable — after the run itself had finished. The example now reads run.default_dataset_id; with client version 1 or 2, keep run['defaultDatasetId']. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
No code, output field or pricing change.
0.1.14 — 2026-09-20 — README examples corrected against the real input schema
The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"query":"supabase","maxResults":500}
The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
No code, output field or pricing change.
0.1 — 2026-09-07
Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).
0.0
Initial release: data from public community and forum discussions by name or registry ID.
