Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who want something more resilient than brittle CSS selectors when they need agents to read, query, or act on real websites.
Who should use it
Who should skip it
Skip tinyfish-io/agentql unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
tinyfish-io/agentql is tracked by RepoRadar as a developer tool in the Web Automation / Extraction section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, tinyfish-io/agentql is strongest on workflow potential (9.6) and open-source/build quality (8.4) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned tinyfish-io/agentql a composite score of 8.1 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It can automate authenticated pages and persist logged-in browser sessions, so first evaluation should use a low-privilege browser profile with no production accounts; Several examples focus on scraping, login automation, and anti-bot durability, so verify target-site terms and data rights before using it on third-party properties.